The core/app.config.php file contains many options, to customize your system. To make these changes, copy the line from your app.config.php file, to the core/local.config.php file. The local file is not touched during any updates, except to add new options.
How to apply settings
The appropriate line is in the app.config.php file - it will look like:
Just copy the line into your local.config file. The app.config if first loaded, and then the local.config is loaded after it, so any changes made in the local.config file are used since it's loaded last.
All of the settings available are not listed here - look through the app.config.php file - they are there, along with the descriptions.
This is the page encoding to use for the site. Internationalized sites may use UTF-8.
This is the extension of pages. Leave as .htm, unless you know what you're doing.
The system starts with an ID of 1. You can start it from 1001, or 5001. This won't change the ID in the database, just the appearance.
This is the length of the ID. Default is 4, so a number will show as 0001. The length includes the ID number.
This setting determines the % of MAXLOAD which are on a flight. The system will generate a passenger/cargo load based off of this number. The industry load factor at this time is 72% (according to ATA). Can be adjusted, not more than 90%. phpVMS will decide between +/- 10% of LOAD_FACTOR
Enter nm (nautical miles), mi (miles), or km (kilometers). This will affect distance calculations
This is your units for cargo flights - lbs/kg/newtons. This is just the text which is displayed
Config::Set('MONEY_UNIT', ' );
This is the unit of money. For non-dollars, use : Euro (â‚¬), enter â€â‚¬â€ Yen (Â¥), enter â€¥â€ Pounds (Â£), enter â€£â€ For example:
Config::Set('MONEY_UNIT', 'â‚¬'); // For Euro
This is if your aircraft do not have a default set. There is a penalty if these values end up being used
This is if your aircraft don't have a passenger load set. There is a penalty if this is used.
Whether to automatically retire a pilot. True/false value. The next setting is for how many days. Inactivity = no PIREP filings.
After how much time, in days, to mark a pilot retired.
Whether to automatically confirm pilots, or require admin approval. Default is fault
After submitting a PIREP, a pilot can edit their PIREP, but only the custom fields. This is the time, in hours, they're allowed to do that.
What to order schedules by. Use s.[column_name] [ASC/DESC], with the column name being from the schedules table