4.1. Installation and directory settings

Configure the directories that appNET OS uses.

The directory settings are stored in the config.inc.php in the root directory and can be changed later.

The directory settings are set by the installer. Changing the directories can cause problems.

• Url (without /index.php at the end)
  The URL APPNET OS is accessible after installation.
  The setting is determined by the installer and should only be changed if APPNET OS is to be installed in a different directory. Changing the setting does not ensure a successful installation.
• Installation directory (without /index.php at the end)
  directory in which APPNET OS is installed.
  The setting is determined by the installer and should not be changed. If the directory is changed, adjustments must be made to the file system.
• Cache directory (based on installation directory)
  Directory in which APPNET OS and the template engines used store cache files. This directory must be within the directory of the installation.
  
• Temporary directory (starting from the installation directory)
  Directory in which temorary data is stored at run time. This directory must be within the directory of the installation.
  
• Log file directory (starting from the installation directory)
  Directory where the APPNET OS log files are stored. This directory must be within the directory of the installation.
  
• Compile directory (starting from the installation directory)
  Directory where the template engines used store their compiled files. This directory must be within the directory of the installation.
  
• Config directory (starting from the installation directory)
  Directory where the template engines used store their configuration files. This directory must be within the directory of the installation.
  

4.2. Security Settings

Important settings for the security of the APPNET OS system. These settings configure the authentication behavior, session behavior, and security of the administration section. User groups for the application section and the administration section can be deactivated here.

The security settings are stored in the config.inc.php in the root directory and can be changed later.

Be careful when changing the security system. Changes can compromise the security of APPNET OS. If you set the wrong setting, you will no longer be able to log on as an administrator..

• Number of false logins until users are blocked
  If users enter your password incorrectly too often, the user account will be locked and must be unlocked in the administration section. Configure the number of false sign-ins until an account is locked.
  
• Time until the link to reset the password expires in seconds
  APPNET OS creates a link with a token when resetting the password. The link allows the user to set a new password with his or her e-mail address. Configure the time for how long the token can be used.
• Application section Session time in seconds
  Time until the session of the application section expires.
• Time until the user logs off in seconds when they save the credentials
  Saved credentials are managed by the APPNET OS Authenticator. This time defines how long stored credentials can be used until the user has to log on again.
• Deactivate application section groups
  For Web applications that do not have restricted pages for specific users, the user groups of the application area can be deactivated here.
• Administration section session time in seconds
  Time until the session of the administration section expires.
  The time must not be configured too short, otherwise you will no longer be able to log on to the administration section.
• Disable administration section groups
  If all administrators are allowed to access all areas of the administration section, the user groups of the administration section can be disabled here.

4.3. Cache Settings

APPNET OS has many cache functions that greatly speed up the system and minimize server load. The JavaScript and CSS cache generates a compressed file from all App JavaScript and App CSS files and integrates them into the HTML head.

The cache settings are stored in the config.inc.php in the root directory and can be changed later. The cache behavior can also be configured in the administration section. The settings in the administration section overwrite the settings from the config.inc.php file.

Apps that always output the same content after their configuration can use the APPNET OS app cache. The app cache speeds up the output of the apps enormously. The finished output of the apps that use the app cache is stored in the database. When the apps are called again, they are not rerun, but the content is loaded and output from the database. This does not load and run classes of the app. The app cache saves up to 50% time when you visit a page.

• App Cache Expiration Time in Seconds
  How long an app that uses the app cache loads from the database until it is recreated.
  
• App Cache
  Defines whether the app cache is used globally.
• File Cache
  The cache file stores all paths of app files in one file. The PHP SPL autoloader no longer needs to search all directories for the classes used when the apps are called again.
• String Cache
  The String Cache stores all already loaded language files in one file. This does not reload language files when the app is called again.
• Directory Cache
  The Cache directory stores all directories that contain app files in one file. When you revisit an app, you don't need to re-search the directories that contain the app's files.
• JavaScript Cache
  The JavaScript cache loads all JavaScript files, from all active apps, and stores them in a file that is mounted via the head area.
  Please note. Not all apps are compatible with the JavaScript cache. The JavaScript cache can be disabled separately in the app settings for each app. If the JavaScript you create causes problems, locate the app that is causing it and disable the JavaScript cache. Don't forget to clear the JavaScript cache when you change the settings.
• CSS Cache
  The CSS cache loads all CSS files, from all active apps, and stores them in a file that is mounted through the head area.

4.4. Compression

APPNET OS can compress the source code, the embedded JavaScript files and the embedded CSS files. Compression makes the output source code up to 50% smaller. This speeds up your web application enormously.

The compression settings are stored in the config.inc.php in the root directory and can be changed later. The compression behavior can also be configured in the administration area. The settings in the administration area overwrite the settings from the config.inc.php file.

• Minimize CSS and JavaScript
  Configure whether JavaScript and CSS files are compressed when they are included.
• Compress HTML source code
  Configure whether the output source code is compressed. This removes all blank rows and indents.

4.5. Developer Settings

In the developer settings, special options for developers can be configured.

The developer settings are stored in the config.inc.php in the root directory and can be changed later. The settings can also be configured in the administration section. The settings in the administration section overwrite the settings from the config.inc.php file.

• Debug Mode
  Debug mode provides tools for developers. When debug mode is enabled, errors and warnings that occur at run time are appended to the end of the output. Requests that use the APPNET OS JavaScript can be read in detail in the JavaScript console.
  Debug mode should never be used in your Live instance. Attackers could get detailed information about your APPNET OS installation here.
• Admin section expert mode
  The Expert mode allows the direct modification of app JavaScript and app CSS files in the administration area.
  Be careful when modifying the app JavaScript and the app CSS files. Incorrect changes can permanently destroy the app.