Search results for "structr.conf"

• The CronService must be included in the structr.conf setting configured.services to be activated
• When a cronExpression is added, deleted or edited, the CronService has to be restarted for the changes to take effect. This can be done at runtime via the configuration tool or by restarting structr
• By default, structr prevents the same cron task to run run while the previous execution is still running. This can be changed via the setting CronService.allowparallelexecution in structr.conf.

This command will ask for a keystore password and some information and then create a file named “domain.key.keystore”. Place this file inside the structr main directory alongside the structr.conf configuration file. Configure the keystore password in structr.conf in the key application.keystore.password and enable HTTPS by setting application.https.enabled = true. Restarting structr will result in a HTTPS-enabled instance.

NOTE: Some browsers will refuse to connect to servers using self-signed certificates citing security risk as the cause. In some browsers the user can accept the risk and still connect.

There is a legacy mode available via the setting application.legacy.requestparameters.enabled = true in structr.conf. This allows using the old syntax without the prefix but is discouraged for new projects.

The reason for this is that, since version 4.1-SNAPSHOT, structr supports connecting to different neo4j databases. The database name has to be configured though. By default the database name is set to “neo4j” (because that is the default database name since neo4j 4.x). If your application started with an older version of neo4j, then the database name might be “graph.db”. If you have configured a different name, then that name has to be used.

The configuration for this is done in structr.conf. A new configuration line has to be added to the existing configuration.

Let us assume the configuration looks like this:

XXXXXXXXXX.database.connection.name = <a name for your connection>
XXXXXXXXXX.database.connection.password = <your database user password>
XXXXXXXXXX.database.connection.url = <your connection string>
XXXXXXXXXX.database.connection.username = <your database username>

XXXXXXXXXX is the custom prefix in your settings.

The new line would need to match the XXXXXXXXXX and look like this:

XXXXXXXXXX.database.connection.databasename =

If the version upgrade is from below Neo4j v4, then it is possible that the default database is called “graph.db” instead of the newer “neo4j” in version 4 and up. Since v4.1 Structr supports selecting a database (if supported by the Neo4j installation it is connecting to). The default database it connects to is the “neo4j” database - if the migration happened from an older version, the correct database name needs to be configured via structr.conf file using the “xxxx.database.connection.databasename” setting as shown in the following example in line 4.

The KeyStore file has to be stored beside the structr.conf file in the installation directory of your Structr instance.

The configuration settings are grouped by topic. You can access the individual groups by clicking on one of the tabs in the tab row of the main area. The individual settings are listed by their key in the config file, e.g. the “application.title” setting can be found in structr.conf under application.title. If there is a little next to the title of a setting, you can get additional information about the setting by hovering over the icon.

To apply the changes, click on the “Save to structr.conf” button on the bottom right.

The Configuration Tool is a web application that allows you to manage configuration settings in structr.conf. It is the preferred way to edit the configuration, because the config file only stores the difference to the default, and you can apply the changes immediately. In a default setup, the tool is available at http://localhost:8082/structr/config.

Structr provides a service for periodic task scheduling: the CronService. It is a background service that can be configured in the structr.conf configuration file to schedule the execution of periodic tasks.

structr.conf is the main configuration file. It consists of key-value mappings which are managed automatically by the Configuration Tool. Since the Configuration Interface is the preferred way of editing configuration settings, the config file only stores the values that differ from the default value.

In order to log into the Configuration Tool, you need the superuser password stored in your structr.conf. Up until version 3.4, Structr was configured to create a secure random password on first start. In versions 3.5 and later, you must enter the superuser password when configuring Structr initially.

To backup a Structr installation, do the following:

• stop the Structr instance
• copy db/ and files/ directories to a safe place
• copy structr.conf to a safe place
• start instance

You can find the password for the Configuration Tool in your structr.conf file.

Please note that by default the number of visible results in the Cypher console is limited to 10. If you run a query that returns more than 10 objects, Structr will show an error message. This number is configurable via application.console.cypher.maxresults in structr.conf

The SSHService allows admin users to connect to the structr instance via the SSH protocol. The SSH port can be configured via the application.ssh.port key in structr.conf.

Authentication can be done via public key or via password (unless explicitly forbidden via application.ssh.forcepublickey).

After successful authentication the SSH connection allows exactly the same functionality as the Admin Console but via SSH.

Using the parameter challenge, you can overwrite the default challenge method as set in structr.conf. This is convenient to test an alternative challenge type without the need to restart the Structr instance.