5,838
edits
MX on Linux: Difference between revisions
m
→Configuration Files to copy across from any previous Cumulus installation
| Line 363: | Line 363: | ||
|- | |- | ||
! scope="col" style="width:450px; color:blue" | Cumulus.ini !! scope="col" style="width:450px; color:navy" | strings.ini | ! scope="col" style="width:450px; color:blue" | Cumulus.ini !! scope="col" style="width:450px; color:navy" | strings.ini | ||
|- | |||
| Your old installation will have this file. In general, ''if your old installation was any release before 3.8.0'', the advice is give the old file a different name when you copy it across to the new installation, and let MX create the file as you work through all the settings. | |||
| '''This is an optional file'''. Its [[strings.ini|purpose]] is to allow customisation of some of the outputs from Cumulus. You might want to use customisation to abbreviate (or extend) some outputs, or to change those outputs into another language. | |||
|- | |- | ||
| When you work through the Settings pages, MX will create this file if it does not exist. | | When you work through the Settings pages, MX will create this file if it does not exist. | ||
* See [[#Moving from Microsoft Windows to Linux]] if your old installation is on a Microsoft operating system, as several changes will be needed for extra web file settings on your Linux computer | * See [[#Moving from Microsoft Windows to Linux]] if your old installation is on a Microsoft operating system, as several changes will be needed for extra web file settings on your Linux computer | ||
* If your old installation was of the legacy software then also see [[Migrating from Cumulus 1 to MX]] | * If your old installation was of the legacy software then also see [[Migrating from Cumulus 1 to MX]] | ||
* As MX evolves, the former "read-only" settings in this file are becoming "advanced" settings in the interface. | * As MX evolves, the former "read-only" settings in this file are becoming "advanced" settings in the interface. | ||
| | | You create a “strings.ini” file by '''selecting some of the parameter'''s from the [[Samplestring.ini]] file that is included in each MX release, and ''modifying the value for the listed attributes'' as you type just those you selected (under the same group titles - these are enclosed in [ ] as before). | ||
You create a “strings.ini” file by selecting some of the | |||
The sections that appear in '''samplestring.ini''', and the parameters that appear within a section, | The sections that appear in '''samplestring.ini''', and the parameters that appear within a section, depend upon which release you are using. So be cautious if you try to reuse a "strings.ini" file originally created by the legacy software, you may find you need to specify your customisation using different parameters in the latest "samplestring.ini". | ||
|- | |- | ||
| | | To remove any parameters no longer used in this file, see [[Cumulus.ini#How_to_Remove_Redundant_parameters_from_file|remove redundant parameters]] | ||
To remove any parameters no longer used in this file, see [[Cumulus.ini#How_to_Remove_Redundant_parameters_from_file|remove redundant parameters]] | |||
If your old file contains any [[Cumulus.ini (Cumulus 1)|legacy read-only]] or [[Cumulus.ini (MX 3.0.0 to 3.7.0)| | If your old file contains any [[Cumulus.ini (Cumulus 1)|legacy read-only]] parameters not yet converted into advanced settings, or any [[Cumulus.ini (MX 3.0.0 to 3.7.0)|MX read-only parameters not yet converted into advanced settings]], you may need to manually add such missing parameters back into new file by stopping MX (after finishing all the settings you can configure in the interface), doing an external file edit, and then restarting MX | ||
| The content of "samplestring.ini" is changing as MX is developed: | | The content of "samplestring.ini" is changing as MX is developed: | ||
* Therefore, your existing “strings.ini” might need to be modified. | * Therefore, your existing “strings.ini” might need to be modified. | ||