Updating MX to new version - Revision history

HansR: /* Installer Option */

2024-07-03T17:54:06Z

Installer Option

← Older revision		Revision as of 17:54, 3 July 2024
Line 93:		Line 93:
	#*The install procedure gives you the possibility to select, or define, the Archive to install, and the location where to install.		#*The install procedure gives you the possibility to select, or define, the Archive to install, and the location where to install.
	#Stop CumulusMX		#Stop CumulusMX
	#Run '''InstallCMX''' and confirm / fill in (on the console) where you wish to install (or update) CMX. The default for Windows is C:\CumulusMX\ and for Linux it is : /home/CumulusMX or ~~/opt/CumulusMX~~ in ~~case~~ of an ''image install''. ~~The~~ ~~Installation~~ ~~directory~~ ~~can~~ ~~be modified~~.		#Run '''InstallCMX''' and confirm / fill in (on the console) where you wish to install (or update) CMX. The default for Windows is C:\CumulusMX\ and for Linux it is : /home/CumulusMX. The Installation directory can be modified. Note that for an ''image install'' you have to use /opt/CumulusMX.
	#* You can give the '''build number''', for the release distribution zip, to install as command line '''argument'''.		#* You can give the '''build number''', for the release distribution zip, to install as command line '''argument'''.
	#Start CumulusMX		#Start CumulusMX

HansR: /* Installer Option */

2024-07-03T17:09:56Z

Installer Option

Relleray: /* Upgrading if you run MX as a service */

2023-03-16T09:32:11Z

Upgrading if you run MX as a service

← Older revision		Revision as of 09:32, 16 March 2023
Line 58:		Line 58:
	For a Linux Operating system: <code>sudo systemctl stop cumulusmx</code>.		For a Linux Operating system: <code>sudo systemctl stop cumulusmx</code>.

	For Microsoft Windows Operating System: ~~(a contributor who uses Microsoft Windows needs to modify this page)~~		For Microsoft Windows Operating System: <br>

			Open Windows Administration Tools from Windows Task Bar, select Component Services, click on Services (local)
			In middle window select CumulusMX service from the list; click on Stop the service option. (click on Start the service after upgrade)

	==Upgrading if you run MX interactively==		==Upgrading if you run MX interactively==

Sfws: /* if using any 3.7.y release, any 3.8.x release, or 3.9.y release */

2021-12-11T18:07:11Z

if using any 3.7.y release, any 3.8.x release, or 3.9.y release

← Older revision		Revision as of 18:07, 11 December 2021
Line 314:		Line 314:


	====if using ~~any~~ 3.7.y release, any 3.8.x release, or 3.9.y release====		====if using 3.7.0 release, any 3.8.x release, or 3.9.y release====

	See sub-section directly above, that describes similar process, '''upgrade directly to 3.9.6, or any later build, within 3.9.x''', without any major change or to 3.12.0 with major change (find either release from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).		See sub-section directly above, that describes similar process,
			* EITHER '''upgrade directly to 3.9.6, or any later build, within 3.9.x, without any major change,'''
			* or to 3.12.0 with major change
			* (find either release from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).

	If you are using 3.7.0 note ~~there were~~ no ~~other~~ ~~builds~~ in 3.7.y series, but because 3.7.0 introduced a lot of changes these staged upgrades recommend that ~~this version~~ is implemented, and run for a while, before continuing to upgrade.		If you are using a release earlier that 3.7.0, you can note 3.7.0 was only build in 3.7.y series, but because 3.7.0 introduced a lot of changes these staged upgrades recommend that 3.7.0 is implemented, and run for a while, before continuing to upgrade.

	~~Version~~ 3.8.0 was a major release, as it introduced the ability to run Cumulus MX as a service. ~~However,~~ there ~~were bugs in the builds in all 3.8.z versions, and in some 3.9.x versions, so that~~ is ~~why~~ ~~you need~~ to ~~skip~~ ~~through~~ ~~intermediate~~ ~~builds~~ to ~~release~~ ~~3.9.6~~ ~~build 3101~~ as a ~~minimum~~, ~~doing~~ ~~the~~ ~~one-off~~ ~~changes~~ ~~noted~~ as ~~IMPORTANT~~ ~~here:~~		Be aware that 3.8.0 was a major release, as it introduced the ability to run Cumulus MX as a service, but there is no reason to install it as the ability to run either interactively, or as a service, continues to be available in all subsequent releases.

			It is optional to install release 3.9.6 build 3101, because that is a safe release to use while there were bugs in the builds in all 3.8.z versions, and in other 3.9.x releases, however please action the one-off changes noted as IMPORTANT here:

	'''IMPORTANT''' one-off actions needed:		'''IMPORTANT''' one-off actions needed:
Line 326:		Line 331:
	* There is a further on-off change described in [https://cumulus.hosiene.co.uk/viewtopic.php?p=147329#p147329 release announcement for Patch release 3.9.1 - b3096] for those who use '''Mono''' to enable the executables to run.		* There is a further on-off change described in [https://cumulus.hosiene.co.uk/viewtopic.php?p=147329#p147329 release announcement for Patch release 3.9.1 - b3096] for those who use '''Mono''' to enable the executables to run.

	If ~~you~~ do ~~implement~~ release 3.9.6 ~~build 3101,~~ you ~~can~~ ~~continue~~ to ~~upgrade,~~ as soon as you are happy to change your web server contents (if you are using web pages that MX provides). You should continue in stages because it is mandatory to install 3.12.0 as only that release can rewrite your [[Cumulus.ini]] file ready for subsequent release, so ensure that 3.12.0 is working before installing current release as instructed in sub-sections for those using subsequent releases.		Be aware that 3.10.0 was withdrawn, but it was a major release that totally changed the files in [[Web folder]] and [[Webfiles folder]] within the release download. However, you can skip directly from 3.9.6 (if you have implemented that) to 3.12.0 as soon as you are happy to change your web server contents (if you are using web pages that MX provides), see sub-section above for further advice re web pages. You should continue in stages because it is mandatory to install 3.12.0 as only that release can rewrite your [[Cumulus.ini]] file ready for subsequent release, so ensure that 3.12.0 is working before installing current release as instructed in sub-sections for those using subsequent releases.

	====If using a 3.5.x release ====		====If using a 3.5.x release ====

Sfws: /* Recommendations for staged updating */

2021-12-11T17:53:14Z

Recommendations for staged updating

← Older revision		Revision as of 17:53, 11 December 2021
Line 289:		Line 289:

	The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].		The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].






	====Currently using one of the 3.9.y releases ====		====Currently using one of the 3.9.y releases ====
Line 305:		Line 310:
	Note: The folder <code>CumulusMX/webfiles-legacy</code> mentioned in the new default web site information page, with some alternative web pages that have no ongoing support, is only available from a 3.10.0 or 3.10.1 download (find from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).		Note: The folder <code>CumulusMX/webfiles-legacy</code> mentioned in the new default web site information page, with some alternative web pages that have no ongoing support, is only available from a 3.10.0 or 3.10.1 download (find from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).

	====if using either 3.8.x or 3.9.y release====

⚫	See ~~next~~ sub-section, that describes similar process, '''upgrade directly to 3.9.6, or any later build, within 3.9.x''', without any major change.



	====if using any 3.7.y release, ~~upgrade to~~ 3.9.6 ~~before~~ ~~going~~ ~~further~~ ====		====if using any 3.7.y release, any 3.8.x release, or 3.9.y release====

		⚫	See sub-section directly above, that describes similar process, '''upgrade directly to 3.9.6, or any later build, within 3.9.x''', without any major change or to 3.12.0 with major change (find either release from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).

		⚫	If you are using 3.7.0 note there were no other builds in 3.7.y series, but because 3.7.0 introduced a lot of changes these staged upgrades recommend that this version is implemented, and run for a while, before continuing to upgrade.

		⚫	Version 3.8.0 was a major release, as it introduced the ability to run Cumulus MX as a service. However, there were bugs in the builds in all 3.8.z versions, and in some 3.9.x versions, so that is why you need to skip through intermediate builds to release 3.9.6 build 3101 as a minimum, doing the one-off changes noted as IMPORTANT here:

	'''IMPORTANT''' one-off actions needed:		'''IMPORTANT''' one-off actions needed:
Line 318:		Line 326:
	* There is a further on-off change described in [https://cumulus.hosiene.co.uk/viewtopic.php?p=147329#p147329 release announcement for Patch release 3.9.1 - b3096] for those who use '''Mono''' to enable the executables to run.		* There is a further on-off change described in [https://cumulus.hosiene.co.uk/viewtopic.php?p=147329#p147329 release announcement for Patch release 3.9.1 - b3096] for those who use '''Mono''' to enable the executables to run.

		⚫	If you do implement release 3.9.6 build 3101, you can continue to upgrade, as soon as you are happy to change your web server contents (if you are using web pages that MX provides). You should continue in stages because it is mandatory to install 3.12.0 as only that release can rewrite your [[Cumulus.ini]] file ready for subsequent release, so ensure that 3.12.0 is working before installing current release as instructed in sub-sections for those using subsequent releases.


	If you are using 3.7.0 (there were no other builds in 3.7.y series), then you should upgrade directly to version 3.9.6 - build 3101.

⚫	~~Only~~ 3.7.0 ~~was~~ ~~ever~~ ~~released~~, it introduced a lot of changes~~, so that is~~ ~~why~~ staged upgrades recommend that this version is implemented, and run for a while, before continuing to upgrade.

⚫	Version 3.8.0 was a major release, as it introduced the ability to run Cumulus MX as a service. However, there were bugs in the builds in all 3.8.z versions, and in some 3.9.x versions, so that is why you need to skip through intermediate builds ~~below~~ ~~3101~~.


⚫	~~When~~ you ~~are~~ ~~happy~~ ~~with running version~~ 3.9.6 build 3101, you can continue to upgrade. You should continue in stages by ~~going~~ to 3.12.0, ~~and~~ ensure that is working before installing current release as instructed for those using subsequent releases.

	====If using a 3.5.x release ====		====If using a 3.5.x release ====
Line 346:		Line 345:
	*'''If you use commas to separate integer and decimal parts of real numbers''', then various releases from 3.6.0 to 3.7.0 add "rc=y" to various web tags, that option will replace the decimal commas you use by decimal points that are required for some script languages (like the JavaScript used by HighCharts), and that makes it easier if you want to customise your web site.		*'''If you use commas to separate integer and decimal parts of real numbers''', then various releases from 3.6.0 to 3.7.0 add "rc=y" to various web tags, that option will replace the decimal commas you use by decimal points that are required for some script languages (like the JavaScript used by HighCharts), and that makes it easier if you want to customise your web site.

	When you are happy with running 3.7.0, then you should continue to upgrade, but in steps (~~3.7.0~~ to 3.9.6, ~~then~~ ~~3.9.6~~ to ~~3.10.y~~, then exactly 3.12.0, then latest) as described in earlier sub-sections for later releases.		When you are happy with running 3.7.0, then you should continue to upgrade, but in steps (optionally try 3.9.6 because that will test some new features, then mandatory upgrade to exactly 3.12.0 which will rewrite your Cumulus.ini file, then you can continue your upgrade to latest) as described in earlier sub-sections for later releases.


Line 353:		Line 352:
	====If using either 3.1.x, 3.2.y, 3.3.z, or 3.4.w releases====		====If using either 3.1.x, 3.2.y, 3.3.z, or 3.4.w releases====

	First, upgrade to 3.5.1 by downloading it at [[https://github.com/cumulusmx/CumulusMX/releases/tag/b3072 Mark's Github respository]]. The actual installation is done using the instructions early in this Wiki page for simple next build upgrades. You can safely skip reading the intermediate release announcements, as there are no special one-off actions.		First, upgrade to 3.5.1 by downloading it at [[https://github.com/cumulusmx/CumulusMX/releases/tag/b3072 Mark's Github respository]]. The actual installation is done using the instructions early in this Wiki page for simple next build upgrades. You can safely skip reading the intermediate release announcements, as there are no special one-off actions. There are one-off actions at 3.5.1, see release announcement. It does not involve any updates to the fields in the log files nor to the columns in any database tables you use.


	When you are happy running 3.5.1, then you should continue to upgrade, initially follow instructions given ~~forlater~~ releases		When you are happy running 3.5.1, then you should continue to upgrade, initially follow instructions given for later releases


Line 365:		Line 364:
	====If using 3.0.0 (the MX original beta)====		====If using 3.0.0 (the MX original beta)====


	Upgrade from the beta directly to 3.5.1 by downloading it at https://github.com/cumulusmx/CumulusMX/releases/tag/b3072.
			Upgrade from the beta directly to 3.5.1 by downloading it at https://github.com/cumulusmx/CumulusMX/releases/tag/b3072. There are one-off actions at 3.5.1, see release announcement. This skips you past the problems in 3.5.0. It gives you benefits introduced in 3.1.x, 3.2.y, 3.3.z, and 3.4.w releases.

	This gives you essential new functionality in the admin interface like editors for the log files and extreme records. But it also fixes multiple bugs in the beta you were using and adds some useful validation missing in the beta.		This gives you essential new functionality in the admin interface like editors for the log files and extreme records. But it also fixes multiple bugs in the beta you were using and adds some useful validation missing in the beta.
Line 371:		Line 371:
	It does not involve any updates to the fields in the log files nor to the columns in any database tables you use.		It does not involve any updates to the fields in the log files nor to the columns in any database tables you use.

	It skips you past the problems in 3.5.0. It gives you benefits introduced in 3.1.x, 3.2.y, 3.3.z, and 3.4.w releases.

	Now follow instructions in other sub-sections, to upgrade in stages until you reach latest release and get support from developer.		Now follow instructions in other sub-sections, to upgrade in stages to where there are significant actions to do, until you reach latest release and get support from developer.

	= Knowing when a new release is available =		= Knowing when a new release is available =

Sfws: /* if using any 3.7.y release, upgrade to 3.9.6 before going further */

2021-12-11T17:32:19Z

if using any 3.7.y release, upgrade to 3.9.6 before going further

← Older revision		Revision as of 17:32, 11 December 2021
Line 327:		Line 327:


	When you are happy with running version 3.9.6 build 3101, you can continue to upgrade. You should continue in stages by going to 3.10.x, and ensure that is working before installing ~~a later~~ release as instructed for those using ~~3.10.x~~ releases.		When you are happy with running version 3.9.6 build 3101, you can continue to upgrade. You should continue in stages by going to 3.12.0, and ensure that is working before installing current release as instructed for those using subsequent releases.


	====If using a 3.5.x release ====		====If using a 3.5.x release ====

Sfws: /* From 3.9.y releases */ renamed sub-section

2021-12-11T17:30:16Z

From 3.9.y releases: renamed sub-section

← Older revision		Revision as of 17:30, 11 December 2021
Line 290:		Line 290:
	The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].		The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].

	====~~From~~ 3.9.y releases ====		====Currently using one of the 3.9.y releases ====

	If you are using any release in the 3.9.y series (note release announcement 3.9.1 warning about Mono if you use that), and you are using web pages that were provided by MX...		If you are using any release in the 3.9.y series (note release announcement 3.9.1 warning about Mono if you use that), and you are using web pages that were provided by MX...
Line 299:		Line 299:
	* Changes to settings		* Changes to settings
	** You need to open the [[MX Administrative Interface]] and work through all pages in the '''Settings''' menu.		** You need to open the [[MX Administrative Interface]] and work through all pages in the '''Settings''' menu.
	*Changes to web files included in two folders in distribution: <code>CumulusMX/web</code>, <code>~~CumulusMX/webfiles</code>~~ ~~and introduction of <code>~~CumulusMX/webfiles~~-legacy~~</code>		*Changes to web files included in two folders in distribution: <code>[[Web folder\|CumulusMX/web]]</code>, <code>[[Webfiles folder\|CumulusMX/webfiles]]</code>
	**If you used the provided templates to produce web pages in earlier releases, or you had directly customised provided [[Customised templates\|web templates]], these will no longer work		**If you used the provided templates to produce web pages in earlier releases, or you had directly customised provided [[Customised templates\|web templates]], these will no longer work
	**Please see [[New Default Web Site Information\|New Default Web Site Information page]] for further advice		**Please see [[New Default Web Site Information\|New Default Web Site Information page]] for further advice

			Note: The folder <code>CumulusMX/webfiles-legacy</code> mentioned in the new default web site information page, with some alternative web pages that have no ongoing support, is only available from a 3.10.0 or 3.10.1 download (find from [https://github.com/cumulusmx/CumulusMX/releases this Github page]).

	====if using either 3.8.x or 3.9.y release====		====if using either 3.8.x or 3.9.y release====

Sfws: /* From 3.9.y releases */ add warning re Mono

2021-12-11T17:23:27Z

From 3.9.y releases: add warning re Mono

← Older revision		Revision as of 17:23, 11 December 2021
Line 292:		Line 292:
	====From 3.9.y releases ====		====From 3.9.y releases ====

	If you are using any release in the 3.9.y series, and you are using web pages that were provided by MX...		If you are using any release in the 3.9.y series (note release announcement 3.9.1 warning about Mono if you use that), and you are using web pages that were provided by MX...

	Then you need to be aware that 3.10.1 (3.10.0 was withdrawn) got rid of the HTML templates that you have been using, and introduced a lot of new settings.		Then you need to be aware that 3.10.1 (3.10.0 was withdrawn) got rid of the HTML templates that you have been using, and introduced a lot of new settings.

Sfws: /* Currently running 3.10.x or 3.11.y */ updated section heading

2021-12-11T17:21:49Z

Currently running 3.10.x or 3.11.y: updated section heading

← Older revision		Revision as of 17:21, 11 December 2021
Line 284:		Line 284:


	====~~From~~ 3.10.x to 3.11.y====		====Currently running 3.10.x or 3.11.y====

	Treat like any other major version upgrade as described above.		Treat like any other major version upgrade as described above.

	The changes between 3.10.~~xand~~ 3.11.y were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].		The changes between any 3.10.x release and any 3.11.y release were minor, but ''you can't go from 3.10.x to the latest release'', because you must use 3.12.0 to convert [[Cumulus.ini]].




	====From 3.9.y releases ====		====From 3.9.y releases ====

Sfws: /* From 3.9.y releases */ update for post 3.11.y

2021-12-11T17:20:18Z

From 3.9.y releases: update for post 3.11.y

← Older revision		Revision as of 17:20, 11 December 2021
Line 293:		Line 293:


	====From 3.9.y to ~~3.10.x~~====		====From 3.9.y releases ====

	If you are using any release in the 3.9.y series, and using web pages that were provided by MX~~, you need to jump only to 3~~.~~10.1 and set up totally different pages on your web server, and change a lot of settings (in [[Cumulus~~.~~ini]])~~.		If you are using any release in the 3.9.y series, and you are using web pages that were provided by MX...

			Then you need to be aware that 3.10.1 (3.10.0 was withdrawn) got rid of the HTML templates that you have been using, and introduced a lot of new settings.

			The good news is that you can now jump straight to 3.12.0 as that release will rename your existing [[Cumulus.ini]] and create a new file with all the new settings:
	The major aspects that changes at 3.10.1 (3.10.0 was withdrawn) are:
	* Changes to settings		* Changes to settings
	** You need to open the [[MX Administrative Interface]] and work through all pages in the '''Settings''' menu.		** You need to open the [[MX Administrative Interface]] and work through all pages in the '''Settings''' menu.
	*Changes to web files included in two folders in distribution: <code>CumulusMX/web</code>, <code>CumulusMX/webfiles</code> and introduction of <code>CumulusMX/webfiles-legacy</code>		*Changes to web files included in two folders in distribution: <code>CumulusMX/web</code>, <code>CumulusMX/webfiles</code> and introduction of <code>CumulusMX/webfiles-legacy</code>
	**If you used the provided templates to produce web pages in earlier releases, or you had directly customised provided [[Customised templates\|web templates]], these will no longer work		**If you used the provided templates to produce web pages in earlier releases, or you had directly customised provided [[Customised templates\|web templates]], these will no longer work
	**Please see [[New Default Web Site Information\|New Default Web Site Information page]] for further advice		**Please see [[New Default Web Site Information\|New Default Web Site Information page]] for further advice






	====if using either 3.8.x or 3.9.y release====		====if using either 3.8.x or 3.9.y release====

← Older revision		Revision as of 17:09, 3 July 2024
Line 89:		Line 89:
	[https://cumulus.hosiene.co.uk/memberlist.php?mode=viewprofile&u=9016 HansR] on support forum has developed an multi-platform installer, see [https://cumulus.hosiene.co.uk/viewtopic.php?f=44&t=18916 Multiplatform Installer for CumulusMX] which makes life a lot easier if you do not wish to dive into the (file level contents) internals of CumulusMX.		[https://cumulus.hosiene.co.uk/memberlist.php?mode=viewprofile&u=9016 HansR] on support forum has developed an multi-platform installer, see [https://cumulus.hosiene.co.uk/viewtopic.php?f=44&t=18916 Multiplatform Installer for CumulusMX] which makes life a lot easier if you do not wish to dive into the (file level contents) internals of CumulusMX.

	#Copy the '''InstallCMX.~~exe~~''' to any directory you want, on the drive where you wish to install (or have previously installed) MX.		#Copy the contents of the '''[https://cumulus.hosiene.co.uk/viewtopic.php?p=150084#p150084 InstallCMX.zip]''' to any directory you want, on the drive where you wish to install (or have previously installed) MX.
	#Copy the CumulusMX release distribution zip(s) to that same directory, if you have not already done so. You may have more than one distribution in the same directory.		#Copy the CumulusMX release distribution zip(s) to that same directory, if you have not already done so. You may have more than one distribution in the same directory.
	#*The install procedure gives you the possibility to select, or define, the Archive to install, and the location where to install.		#*The install procedure gives you the possibility to select, or define, the Archive to install, and the location where to install.
	#Stop CumulusMX		#Stop CumulusMX
	#Run '''InstallCMX''' and confirm / fill in (on the console) where you wish to install (or update) CMX. The default for Windows is C:\CumulusMX\ and for Linux it is : /home/CumulusMX. The Installation directory can be modified.		#Run '''InstallCMX''' and confirm / fill in (on the console) where you wish to install (or update) CMX. The default for Windows is C:\CumulusMX\ and for Linux it is : /home/CumulusMX or /opt/CumulusMX in case of an ''image install''. The Installation directory can be modified.
	#* You can give the '''build number''', for the release distribution zip, to install as command line '''argument'''.		#* You can give the '''build number''', for the release distribution zip, to install as command line '''argument'''.
	#Start CumulusMX		#Start CumulusMX

	'''NOTE:''' On Windows you run ~~the installer~~ as any other ~~command line~~ executable and it is best to open a command window in which you start the installer. On Linux you run it on the ~~command line~~ as "mono ./InstallCMX.exe", ~~the~~ ~~mono~~ ~~command~~ ~~can~~ be ~~omitted~~ if ~~mono~~ is ~~already active (e.g. if you~~ run ~~CumulusMX~~ as ~~a service, and stop it, mono remains active)~~.		'''NOTE:''' On Windows you run it as any other commandline executable and it is best to open a command window in which you start the installer. On Linux you run it on the commandline as "mono ./InstallCMX.exe" or "dotnet ./InstallCMX.dll". Note that on windows you can also run as ./InstallCMX.exe
	'''NOTE:''' In an existing installation with modified files, make sure those are in a different, either filename or folder (a safe place). If they have the same name as files in the distribution, they will be overwritten.		'''NOTE:''' In an existing installation with modified files, make sure those are in a different, either filename or folder (a safe place). If they have the same name as files in the distribution, they will be overwritten.
	'''NOTE:''' Check in the <code>webfiles</code> directory to see if any files there have been modified, since your last upload to your web server. If so, move those new files to the website.		'''NOTE:''' Check in the <code>webfiles</code> directory to see if any files there have been modified, since your last upload to your web server. If so, move those new files to the website.

	After the installation, there is a '''log file'''. Check the log file to see everything has gone well.		After the installation, there is a '''log file'''. Check the log file to see everything has gone well.
	There is an '''ini file''' where you can control:		There is also an '''ini file''' where you can control:
	* NormalMessageToConsole=true or (default) NormalMessageToConsole=false		* NormalMessageToConsole=true or (default) NormalMessageToConsole=false
	* TraceInfoLevel=Warning (out of: Error, Warning, Info, Verbose, None)		* TraceInfoLevel=Warning (out of: Error, Warning, Info, Verbose, None)
Line 108:		Line 108:
	Any reactions (thank you, issues and questions) please post in the [https://cumulus.hosiene.co.uk/viewtopic.php?f=44&t=18916 download thread of the installer].		Any reactions (thank you, issues and questions) please post in the [https://cumulus.hosiene.co.uk/viewtopic.php?f=44&t=18916 download thread of the installer].

	Modifications and additions on user request can be discussed (e.g. think about automated start/stop, upload of webfiles to the directory etc....), use the talk for this page.		Modifications and additions on user request can be discussed (e.g. think about automated start/stop, upload of webfiles to the directory etc....), use the talk for this page and create a post in the above thread.

	==Upgrading if you are running MX on a Linux computer==		==Upgrading if you are running MX on a Linux computer==