MX on Linux: Difference between revisions

MX on Linux (view source)

Revision as of 09:07, 25 July 2021

214 bytes added , 09:07, 25 July 2021

→‎Configuration Files to copy across from any previous Cumulus installation

Sfws

5,838

edits

@@ Line 352: / Line 352: @@
 *[[Cumulus.ini]] (note initial capital, then lower case) – main configuration file
-If your old installation was for a relatively recent release, then just copy these files to new installation and optionally skip the next 2 sub-sections.
+Just copy the existing files from old to new installation, if
+# Your locale is still the same
+# All files on your new install are in same paths as on your old install (some settings involve specifying paths)
+# Your old installation has a relatively recent MX release (compare the "y" in 3.y.z,between old and new installation,  a difference of more than 1 means you do not have a recent release)
+# Your old installation was on a Linux computer (not a computer running Microsoft Windows Operating System)
-If you are upgrading from an older release, please read the next 2 sub-sections for advice.
-===strings.ini===
+If you are upgrading from an older release, please read the table for advice.
-'''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.
+{| class="wikitable"
+|-
+! scope="col" style="width:450px; color:blue" | Cumulus.ini !! scope="col" style="width:450px; color:navy" | strings.ini
+|-
+| When you work through the Settings pages, MX will create this file if it does not exist.
+* In general, if your old installation was any release before 3.8.0, the advice is rename the old file and use the settings pages to create a new file
+* 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]]
+* As MX evolves, the former "read-only" settings in this file are becoming "advanced" settings in the interface.
+| '''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.
 You create a “strings.ini” file by selecting some of the parameters from the [[Samplestring.ini]] file that is included in each MX release, and modifying the value for the listed attributes as you type them (under the same group titles - these are enclosed in [ ] as before).
-The sections that appear in '''samplestring.ini''', and the parameters that appear within a section, changed drastically between Cumulus 1.9.4 and MX.  So be cautious if you try to use a "strings.ini" file originally created by the legacy software, check whether the parameters you used before are still available in the latest "samplestrings.ini".
+The sections that appear in '''samplestring.ini''', and the parameters that appear within a section, changed drastically between Cumulus 1.9.4 and MX.  So be cautious if you try to use a "strings.ini" file originally created by the legacy software, check whether the parameters you used before are still available 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]]
-The content of "samplestring.ini" is changing as MX is developed:
+If your old file contains any [[Cumulus.ini (Cumulus 1)|legacy read-only]] or [[Cumulus.ini (MX 3.0.0 to 3.7.0)|early MX read-only]] parameters, you may need to manually add them back into new file by stopping MX (after finishing all the settings you can configure in the interface), do an external file edit, and then restart MX
+| The content of "samplestring.ini" is changing as MX is developed:
 * Therefore, your existing “strings.ini” might need to be modified.
 * There is no automatic way to check your “strings.ini” file, if MX does not understand any parameter in this file, it ignores it.
 * Instead, you need to manually check each parameter you have in your “strings.ini” file to see if that parameter is still in the “samplestring.ini” included in the release you have installed.
 * You may also find new parameters in “samplestring.ini” that you wish to add to your “strings.ini” file to tailor new functionality to your preferences.
+|}
-===Cumulus.ini===
-If your old release was 3.8.0 or later, then copy the [[Cumulus.ini]] file used in that old installation into your new one. The file is growing with lots of new parameters, and the tables on the page I have just linked indicated when parameters were introduced, and where those settings may be changed to make it simple for you to ensure all settings are right for your new release.
-If your old release was older that 3.8.0, then you will see [[:Category:Configuration Files|the Configuration Files page]] shows different links for documentation on older "cumulus.ini" files.  Because of those differences, many people prefer to rename their existing “Cumulus.ini” file when upgrading from such an old release, or making an install on a new device. To create a new file, they work through all the settings manually, so that MX can create a fresh file, with them having confidence every setting reflects their preference.  However, you do need to be aware that such older releases included a lot of "read-only" parameters that had to be set manually in the file, you may find some of those parameters are still needed by you, so you will want to edit the new file, with MX stopped, and copy any of those old "read-only" parameters that might not yet be settings you configure within the MX interface (although the number of these is diminishing with each new release).
 If you previously used an older release of Cumulus, but in this new installation will be using the latest release (latest is what is normally best, unless it has bugs), you may want to read up on all the changes between your old release and the current release, not just changes that affect the configuration file.