InContext Server Installation - Revision history

Lji: /* Backup the database */

2024-06-24T21:13:01Z

Backup the database

← Older revision		Revision as of 21:13, 24 June 2024
Line 153:		Line 153:

	== Backup the database ==		== Backup the database ==
	You don't have to backup the current version of the database before proceeding to the update to the new version of the system, because the Update script will backup your current database automatically before updating. If you want to do the backup manually, you can use the ~~BackupCommandCenterDatabase~~.sh script		You don't have to backup the current version of the database before proceeding to the update to the new version of the system, because the Update script will backup your current database automatically before updating. If you want to do the backup manually, you can use the BackupIncontextDatabase.sh script

	chmod +x *.sh		chmod +x *.sh
	sudo ./~~BackupCommandCenterDatabase~~.sh		sudo ./BackupIncontextDatabase.sh

	The database backup sql file will be under $home_directory/~~commandcenter~~/backup folder, named ~~commandcenter_backup_~~$current_date.sql		The database backup sql file will be under $home_directory/incontext/backup folder, named incontext_backup_$current_date.sql

	To backup the database periodically, schedule to run <code>~~BackupCommandCenterDatabase~~.sh</code>, for instance with cron services.		To backup the database periodically, schedule to run <code>BackupIncontextDatabase.sh</code>, for instance with cron services.

	=== Note: Restoring the database ===		=== Note: Restoring the database ===
Line 167:		Line 167:

	chmod +x *.sh		chmod +x *.sh
	sudo ./~~RestoreCommandCenterDatabase~~.sh YYYY-MM-DD		sudo ./RestoreIncontextDatabase.sh YYYY-MM-DD

	Check your database backup sql file under '''$home_directory/~~commandcenter~~/backup''' folder, they are named '''~~commandcenter_backup_~~$current_date.s'''ql, for example, if you backup the database on 2023 September 20th, you will see a ~~commandcenter_backup_2023~~-09-20.sql file, and you can use below command to restore it		Check your database backup sql file under '''$home_directory/incontext/backup''' folder, they are named '''incontext_backup_$current_date.s'''ql, for example, if you backup the database on 2023 September 20th, you will see a incontext_backup_2023-09-20.sql file, and you can use below command to restore it

			sudo ./RestoreIncontextDatabase.sh 2023-09-20

	~~sudo ./RestoreCommandCenterDatabase.sh 2023-09-20~~
	= Next Steps =		= Next Steps =
	The next steps involve configuring and using the InContext Server for your localization needs. For more details on post-installation setup and usage, refer to the InContext Server Users Guide.		The next steps involve configuring and using the InContext Server for your localization needs. For more details on post-installation setup and usage, refer to the InContext Server Users Guide.

Lji: /* Next Steps */

2024-06-24T21:11:09Z

Next Steps

@@ Line 152: / Line 152: @@
 Go to [[ InContext_Server_Users_Guide|User Guide ]] to log in for the first time and perform the base configuration.
 = Next Steps =
 The next steps involve configuring and using the InContext Server for your localization needs. For more details on post-installation setup and usage, refer to the InContext Server Users Guide.

Rwilliams: /* InContext Server */

2024-04-18T17:32:24Z

InContext Server

← Older revision		Revision as of 17:32, 18 April 2024
Line 1:		Line 1:
	= InContext Server =		= InContext Server =
	The typical G11n system will be installed using a Docker-based method.		The typical G11n system will be installed using a Docker-based method.
	~~<BR>~~
	~~<B>Please note this section is currently a WORK IN PROGRESS so it may not be fully accurate</B>~~

	==Hardware & Software Requirements==		==Hardware & Software Requirements==

Olibouban: /* Installation Files */

2024-04-16T20:42:03Z

Installation Files

← Older revision		Revision as of 20:42, 16 April 2024
Line 102:		Line 102:

	Clone the public repo in the home directory of your user with sudo rights.		Clone the public repo in the home directory of your user with sudo rights.
	* The public repo can be found at the [[ https://github.com/Lingoport/CommandCenterConfig ~~\| Public Repo ]]~~		* The public repo can be found at the https://github.com/Lingoport/CommandCenterConfig

	Once cloned create a new directory in the home directory called IncontextInstall (It can be named anything you wish)		Once cloned create a new directory in the home directory called IncontextInstall (It can be named anything you wish)

Olibouban: /* Installation Files */

2024-04-16T20:41:24Z

Installation Files

← Older revision		Revision as of 20:41, 16 April 2024
Line 102:		Line 102:

	Clone the public repo in the home directory of your user with sudo rights.		Clone the public repo in the home directory of your user with sudo rights.
	* The public repo can be found at the [[https://github.com/Lingoport/CommandCenterConfig\|Public Repo]]		* The public repo can be found at the [[ https://github.com/Lingoport/CommandCenterConfig \| Public Repo ]]

	Once cloned create a new directory in the home directory called IncontextInstall (It can be named anything you wish)		Once cloned create a new directory in the home directory called IncontextInstall (It can be named anything you wish)

Rwilliams: /* External access */

2024-04-16T19:57:52Z

External access

← Older revision		Revision as of 19:57, 16 April 2024
Line 59:		Line 59:
	\|Lingoport SSH access \|\| 22 \|\| Y \|\| N \|\| Optional. Recommended for ease of upgrades and maintenance.		\|Lingoport SSH access \|\| 22 \|\| Y \|\| N \|\| Optional. Recommended for ease of upgrades and maintenance.
	\|-		\|-
	\|~~Incontext~~ Server \|\| 8085 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| Default 8085 (configurable at install time) HTTPS requires reverse proxy Ex: Apache and Installation of SSL certificate.		\|InContext Server \|\| 8085 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| Default 8085 (configurable at install time) HTTPS requires reverse proxy Ex: Apache and Installation of SSL certificate.
	\|-		\|-
	\|RHEL/CentOS/Ubuntu Packages \|\| 80 (Debian) 443 (RHEL) \|\| N \|\| Y \|\| Operating system packages access (Most likely external, but could be managed internally as well)		\|RHEL/CentOS/Ubuntu Packages \|\| 80 (Debian) 443 (RHEL) \|\| N \|\| Y \|\| Operating system packages access (Most likely external, but could be managed internally as well)

Rwilliams: /* Internal to company network */

2024-04-16T19:57:43Z

Internal to company network

← Older revision		Revision as of 19:57, 16 April 2024
Line 49:		Line 49:
	\|SSH (for system config/maintenance)\|\| 22 \|\| Y \|\| N \|\| System configuration and maintenance		\|SSH (for system config/maintenance)\|\| 22 \|\| Y \|\| N \|\| System configuration and maintenance
	\|-		\|-
	\|~~Incontext~~ Server \|\| 8085 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| Default 8085 (configurable at install time) HTTPS requires reverse proxy Ex: Apache and Installation of SSL certificate.		\|InContext Server \|\| 8085 (HTTP) and/or 443 (HTTPS) \|\| Y \|\| N \|\| Default 8085 (configurable at install time) HTTPS requires reverse proxy Ex: Apache and Installation of SSL certificate.
	\|}		\|}

Rwilliams at 19:57, 16 April 2024

2024-04-16T19:57:14Z

Show changes

Rwilliams: /* Installation Files */

2024-04-12T21:08:03Z

Installation Files

← Older revision		Revision as of 21:08, 12 April 2024
Line 36:		Line 36:
	The installation files for InContext are located in the same place as the ones for Command Center.		The installation files for InContext are located in the same place as the ones for Command Center.

	Clone the public repo in the home directory of your sudo ~~user~~. The public repo can be found at the [[https://github.com/Lingoport/CommandCenterConfig\|Public Repo]]		Clone the public repo in the home directory of your user with sudo rights.
			* The public repo can be found at the [[https://github.com/Lingoport/CommandCenterConfig\|Public Repo]]

	Once cloned create a new directory in the home directory called IncontextInstall (It can be named anything you wish)		Once cloned create a new directory in the home directory called IncontextInstall (It can be named anything you wish)

Rwilliams: /* Docker-based Installation of InContext Server */

2024-04-12T21:06:38Z

Docker-based Installation of InContext Server

← Older revision		Revision as of 21:06, 12 April 2024
Line 17:		Line 17:
	Users in the 'docker' group may optionally omit use of sudo.		Users in the 'docker' group may optionally omit use of sudo.

	== Docker-based Installation of InContext Server ==		= Docker-based Installation of InContext Server =
	For a new, simplified deployment process, the InContext Server can be installed using Docker. This section outlines the Docker-based installation process.		For a new, simplified deployment process, the InContext Server can be installed using Docker. This section outlines the Docker-based installation process.

	<B>Please note this section is currently a WORK IN PROGRESS so it may not be fully accurate</B>		<B>Please note this section is currently a WORK IN PROGRESS so it may not be fully accurate</B>

	=== Pre-Requisites ===		== Pre-Requisites ==
	~~==== Create sudo user if needed on the VM ====~~
	~~A user, such as centos or ec2-user, with sudo privileges is required as the user under which to install InContext Server~~

	===~~= This is a Docker installation =~~===		=== OS Requirements ===
	This requires Linux and a Docker installation.		This requires Linux and a Docker installation.
	The details on the installation of Docker itself on the Linux vm can be found [[ Command_Center_Installation#Docker_Install\|here ]]		The details on the installation of Docker itself on the Linux vm can be found [[ Command_Center_Installation#Docker_Install\|here ]]
	Most of the containers will be managed by Docker. However, volumes will be mounted on the Linux virtual machine and a database configuration file will reside on the VM		Most of the containers will be managed by Docker. However, volumes will be mounted on the Linux virtual machine and a database configuration file will reside on the VM

	==== Installation Files ====		=== User Account Requirements ===
			Create sudo user if needed on the VM
			* A user, such as centos or ec2-user, with sudo privileges is required as the user under which to install InContext Server

			=== Installation Files ===
	The installation files for InContext are located in the same place as the ones for Command Center.		The installation files for InContext are located in the same place as the ones for Command Center.

	Clone the public repo in the home directory of your sudo user. The public repo can be found at the [[https://github.com/Lingoport/CommandCenterConfig\|Public Repo]]		Clone the public repo in the home directory of your sudo user. The public repo can be found at the [[https://github.com/Lingoport/CommandCenterConfig\|Public Repo]]

Line 46:		Line 49:
	Open the install.conf with your editor as there are a couple of items in the file that will need to be modified		Open the install.conf with your editor as there are a couple of items in the file that will need to be modified

	Set the home_directory to the home directory of the current user		* Set the home_directory to the home directory of the current user
			* Set the incontext_image_version to the current version of InContext-Server. If unsure what the version is, it can be found [https://hub.docker.com/repository/docker/lingoport/incontext_pro/general Here ]
	Set the incontext_image_version to the current version of InContext-Server. If unsure what the version is, it can be found [https://hub.docker.com/repository/docker/lingoport/incontext_pro/general Here ]		* Optionally change the serverPort if desired or leave it at the default
			* Set the database_root_password to a password that you want to use for the root user on the database. Note this should be a good password so something from a random generator is a good idea of significant length.
	Optionally change the serverPort if desired or leave it at the default		* The other items in the file should not be required to be modified.

	Set the database_root_password to a password that you want to use for the root user on the database. Note this should be a good password so something from a random generator is a good idea of significant length.

	The other items in the file should not be required to be modified.

	=== Installation Process ===		== Installation Process ==
	Modify the `install.conf` file with your specific configurations, including Docker Hub credentials (account with read access to the InContext Image will be shared by Lingoport), MySQL root password (to be created with an associated MySQL 8 container), and desired server port.		Modify the `install.conf` file with your specific configurations, including Docker Hub credentials (account with read access to the InContext Image will be shared by Lingoport), MySQL root password (to be created with an associated MySQL 8 container), and desired server port.