Upgrade - История изменений

N.Skrypnik в 07:08, 30 июля 2025

2025-07-30T07:08:13Z

← Предыдущая версия		Версия от 07:08, 30 июля 2025
Строка 12:		Строка 12:
	Specifics of the version 3.18 upgrade: [[Upgrade 3.18\|view]]		Specifics of the version 3.18 upgrade: [[Upgrade 3.18\|view]]
	Specifics of the version 3.19 upgrade: [[Upgrade 3.19\|view]]		Specifics of the version 3.19 upgrade: [[Upgrade 3.19\|view]]
			Specifics of the version 3.20 upgrade: [[Upgrade 3.20\|view]]

	'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.		'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.

N.Skrypnik в 09:25, 11 июля 2024

2024-07-11T09:25:19Z

← Предыдущая версия		Версия от 09:25, 11 июля 2024
Строка 1:		Строка 1:
	[[~~Upgrade_(installer)~~\|en]] \| [[~~Обновление_(инсталлятор)~~\|ru]]		[[Upgrade\|en]] \| [[Обновление\|ru]]

	'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].		'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].

N.Skrypnik: N.Skrypnik переименовал страницу Upgrade (installer) в Upgrade: Renaming

2024-07-11T09:23:28Z

N.Skrypnik переименовал страницу Upgrade (installer) в Upgrade: Renaming

← Предыдущая версия	Версия от 09:23, 11 июля 2024
(нет различий)

Admin в 14:23, 3 июня 2024

2024-06-03T14:23:10Z

← Предыдущая версия		Версия от 14:23, 3 июня 2024
Строка 10:		Строка 10:
	Specifics of the version 3.16 upgrade: [[Upgrade 3.16\|view]]		Specifics of the version 3.16 upgrade: [[Upgrade 3.16\|view]]
	Specifics of the version 3.17 upgrade: [[Upgrade 3.17\|view]]		Specifics of the version 3.17 upgrade: [[Upgrade 3.17\|view]]
			Specifics of the version 3.18 upgrade: [[Upgrade 3.18\|view]]
			Specifics of the version 3.19 upgrade: [[Upgrade 3.19\|view]]

	'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.		'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.

N.Skrypnik в 17:23, 28 февраля 2024

2024-02-28T17:23:16Z

← Предыдущая версия		Версия от 17:23, 28 февраля 2024
Строка 23:		Строка 23:
	== Upgrade ==		== Upgrade ==

	See also: [[Installer\|Installer ~~Help~~]]		See also: [[Installer\|Installer help]]

	1) Navigate to the system directory ''(/var/www/userside)''		1) Navigate to the system directory ''(/var/www/userside)''
Строка 41:		Строка 41:
	sudo -u www-data php userside_install.phar repair		sudo -u www-data php userside_install.phar repair

	If the problem cannot be solved by yourself, submit a ticket to [[Technical_support_regulations\|Technical ~~Support~~]].		If the problem cannot be solved by yourself, submit a ticket to [[Technical_support_regulations\|Technical support]].

	4) if necessary, upgrade the UserSide family modules with new files on all machines where they are running		4) if necessary, upgrade the UserSide family modules with new files on all machines where they are running

	5) restore the previously disabled ERP "UserSide" modules in the system cron, and start the permanently running Userside services, if any		5) restore the previously disabled ERP "UserSide" modules in the system cron, and start the permanently running Userside services, if any

N.Skrypnik в 17:22, 28 февраля 2024

2024-02-28T17:22:05Z

← Предыдущая версия		Версия от 17:22, 28 февраля 2024
Строка 13:		Строка 13:
	'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.		'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.

	Instructions on how to create a copy of a working system for testing a new version or other research can be found in [[HOWTO: ~~Cloning~~ USERSIDE]].		Instructions on how to create a copy of a working system for testing a new version or other research can be found in [[HOWTO: USERSIDE cloning]].

	== Preparation work ==		== Preparation work ==

N.Skrypnik в 18:17, 20 февраля 2023

2023-02-20T18:17:55Z

← Предыдущая версия		Версия от 18:17, 20 февраля 2023
Строка 35:		Строка 35:
	During runtime, the installer will suggest you select the version to which you want to upgrade. It can be a version from a provided list (you can enter a serial number from the list) or any other version (you can enter a version number, e.g. 3.15.4).		During runtime, the installer will suggest you select the version to which you want to upgrade. It can be a version from a provided list (you can enter a serial number from the list) or any other version (you can enter a version number, e.g. 3.15.4).

	A message will be displayed when the ~~update~~ is completed.		A message will be displayed when the upgrade is completed.

	If the installer is interrupted for any reason (data migration error or other), run the installer with the repair command		If the installer is interrupted for any reason (data migration error or other), run the installer with the repair command

N.Skrypnik в 18:14, 20 февраля 2023

2023-02-20T18:14:43Z

← Предыдущая версия		Версия от 18:14, 20 февраля 2023
Строка 3:		Строка 3:
	'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].		'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].

	~~Features~~ of the version 3.11 upgrade: [[Upgrade 3.11\|view]]		Specifics of the version 3.11 upgrade: [[Upgrade 3.11\|view]]
	~~Features~~ of the version 3.12 upgrade: [[Upgrade 3.12\|view]]		Specifics of the version 3.12 upgrade: [[Upgrade 3.12\|view]]
	~~Features~~ of the version 3.13 upgrade: [[Upgrade 3.13\|view]]		Specifics of the version 3.13 upgrade: [[Upgrade 3.13\|view]]
	~~Features~~ of the version 3.14 upgrade: [[Upgrade 3.14\|view]]		Specifics of the version 3.14 upgrade: [[Upgrade 3.14\|view]]
	~~Features~~ of the version 3.15 upgrade: [[Upgrade 3.15\|view]]		Specifics of the version 3.15 upgrade: [[Upgrade 3.15\|view]]
	~~Features~~ of the version 3.16 upgrade: [[Upgrade 3.16\|view]]		Specifics of the version 3.16 upgrade: [[Upgrade 3.16\|view]]
	~~Features~~ of the version 3.17 upgrade: [[Upgrade 3.17\|view]]		Specifics of the version 3.17 upgrade: [[Upgrade 3.17\|view]]

	'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.		'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.

N.Skrypnik в 18:07, 20 февраля 2023

2023-02-20T18:07:16Z

← Предыдущая версия		Версия от 18:07, 20 февраля 2023
Строка 11:		Строка 11:
	Features of the version 3.17 upgrade: [[Upgrade 3.17\|view]]		Features of the version 3.17 upgrade: [[Upgrade 3.17\|view]]

	'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.		'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.

	Instructions on how to create a copy of a working system for testing a new version or other research can be found in [[HOWTO: Cloning USERSIDE]].		Instructions on how to create a copy of a working system for testing a new version or other research can be found in [[HOWTO: Cloning USERSIDE]].

N.Skrypnik в 18:06, 20 февраля 2023

2023-02-20T18:06:32Z

← Предыдущая версия		Версия от 18:06, 20 февраля 2023
Строка 1:		Строка 1:
	[[Upgrade_(installer)\|en]] \| [[Обновление_(инсталлятор)\|ru]]		[[Upgrade_(installer)\|en]] \| [[Обновление_(инсталлятор)\|ru]]

			'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].

			Features of the version 3.11 upgrade: [[Upgrade 3.11\|view]]
			Features of the version 3.12 upgrade: [[Upgrade 3.12\|view]]
			Features of the version 3.13 upgrade: [[Upgrade 3.13\|view]]
			Features of the version 3.14 upgrade: [[Upgrade 3.14\|view]]
			Features of the version 3.15 upgrade: [[Upgrade 3.15\|view]]
			Features of the version 3.16 upgrade: [[Upgrade 3.16\|view]]
			Features of the version 3.17 upgrade: [[Upgrade 3.17\|view]]

			'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.

			Instructions on how to create a copy of a working system for testing a new version or other research can be found in [[HOWTO: Cloning USERSIDE]].

			== Preparation work ==

			1) Be sure to back up the database, the programme directory and all modules before upgrading the working copy! You are responsible for the safety of your data!

			2) Disable all ERP "UserSide" modules in the system cron and stop all ongoing modules working with the Userside database during the upgrade

			== Upgrade ==

			See also: [[Installer\|Installer Help]]

			1) Navigate to the system directory ''(/var/www/userside)''

			2) Run the installer with the ''install'' command

			sudo -u www-data php userside_install.phar install

			In the work process, the installer checks for compliance with technical requirements and asks questions related to the upgrade.

			During runtime, the installer will suggest you select the version to which you want to upgrade. It can be a version from a provided list (you can enter a serial number from the list) or any other version (you can enter a version number, e.g. 3.15.4).

			A message will be displayed when the update is completed.

			If the installer is interrupted for any reason (data migration error or other), run the installer with the repair command

			sudo -u www-data php userside_install.phar repair

			If the problem cannot be solved by yourself, submit a ticket to [[Technical_support_regulations\|Technical Support]].

			4) if necessary, upgrade the UserSide family modules with new files on all machines where they are running

			5) restore the previously disabled ERP "UserSide" modules in the system cron, and start the permanently running Userside services, if any

← Предыдущая версия		Версия от 18:14, 20 февраля 2023
Строка 3:		Строка 3:
	'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].		'''ATTENTION: These instructions are valid for ERP "UserSide" version 3.10 and higher. For versions below 3.10 - use separate instructions for [[Upgrade\|upgrade]].

	~~Features~~ of the version 3.11 upgrade: [[Upgrade 3.11\|view]]		Specifics of the version 3.11 upgrade: [[Upgrade 3.11\|view]]
	~~Features~~ of the version 3.12 upgrade: [[Upgrade 3.12\|view]]		Specifics of the version 3.12 upgrade: [[Upgrade 3.12\|view]]
	~~Features~~ of the version 3.13 upgrade: [[Upgrade 3.13\|view]]		Specifics of the version 3.13 upgrade: [[Upgrade 3.13\|view]]
	~~Features~~ of the version 3.14 upgrade: [[Upgrade 3.14\|view]]		Specifics of the version 3.14 upgrade: [[Upgrade 3.14\|view]]
	~~Features~~ of the version 3.15 upgrade: [[Upgrade 3.15\|view]]		Specifics of the version 3.15 upgrade: [[Upgrade 3.15\|view]]
	~~Features~~ of the version 3.16 upgrade: [[Upgrade 3.16\|view]]		Specifics of the version 3.16 upgrade: [[Upgrade 3.16\|view]]
	~~Features~~ of the version 3.17 upgrade: [[Upgrade 3.17\|view]]		Specifics of the version 3.17 upgrade: [[Upgrade 3.17\|view]]

	'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.		'''We recommend''' having two instances of the system. A separate production instance and a test instance. On the test instance, you can periodically update the database from the production system and perform upgrades to make sure everything is working, check new features, or identify things that are not working for you.