You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.


The application.schema.automigration flag enables Structr to automatically remove or modify parts of the buit-in schema that have changed due to a version upgrade.

Please note that the automatic migration can only fix specific modifications like added or removed schema methods. It might be necessary to manually amend the schema, especially when upgrading older instances or schemas that define lots of new properties or methods on built-in types.


application.schema.automigration = true

When upgrading to Structr 3.0, the automigration flag is necessary to allow the schema upgrade.

Search results for "application.schema.automigration"


application.schema.automigration Allows Structr to attempt an automatic migration of the schema between different Structr versions.
application.schema.allowunknownkeys Allows access to properties that are not specified in the schema via get/set-Operations.

Kubernetes / Helm

# configure the desired number of replicas
replicaCount: 1

# Structr configuration

# configure your desired memory limits
min: 1g
max: 4g

# configure the storage class and size for your cloud provider of choice
storageClassName: "standard"
size: 2Gi

# configure the connection to Neo4j
url: "bolt://neo4j:7687"
username: "neo4j"
password: "password"

# Add custom config entries here
custom: [
"application.schema.automigration = true",

# put the contents of your license.key file here
# please note that clustering only works with a Structr Enterprise license key
license: ""

# configure resource limits according to you cluster node configuration
cpu: 1000m
memory: 4Gi
cpu: 100m
memory: 1Gi