Installing Telstar - Revision history

John: /* Pull the Images and Run the Containers */

2022-05-07T17:04:20Z

Pull the Images and Run the Containers

← Older revision		Revision as of 17:04, 7 May 2022
Line 21:		Line 21:
	== Pull the Images and Run the Containers ==		== Pull the Images and Run the Containers ==

	It is highly recommended that the Stacks feature of Portainer, inconjunction with a compose file is used to install and manage Telstar. But to get started quickly the following docker commands can be used. See [[Managing Telstar with Portainer]] and		It is highly recommended that the Stacks feature of Portainer, inconjunction with a compose file is used to install and manage Telstar. But to get started quickly the following docker commands can be used. See [[Managing Telstar with Portainer]] and [[Orchestrating Telstar with Docker Compose]].

	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.

John: /* Pull the Images and Run the Containers */

2022-05-07T17:03:44Z

Pull the Images and Run the Containers

← Older revision		Revision as of 17:03, 7 May 2022
Line 21:		Line 21:
	== Pull the Images and Run the Containers ==		== Pull the Images and Run the Containers ==

	It is highly recommended that the Stacks feature of Portainer, inconjunction with a compose file is used to install and manage Telstar. But to get started quickly the following docker commands can be used.		It is highly recommended that the Stacks feature of Portainer, inconjunction with a compose file is used to install and manage Telstar. But to get started quickly the following docker commands can be used. See [[Managing Telstar with Portainer]] and

	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.

John: /* Pull the Images and Run the Containers */

2022-05-07T17:03:05Z

Pull the Images and Run the Containers

← Older revision		Revision as of 17:03, 7 May 2022
Line 20:		Line 20:

	== Pull the Images and Run the Containers ==		== Pull the Images and Run the Containers ==

			It is highly recommended that the Stacks feature of Portainer, inconjunction with a compose file is used to install and manage Telstar. But to get started quickly the following docker commands can be used.

	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.

John: /* Pull the Images and Run the Containers */

2022-05-07T08:52:38Z

Pull the Images and Run the Containers

← Older revision		Revision as of 08:52, 7 May 2022
Line 21:		Line 21:
	== Pull the Images and Run the Containers ==		== Pull the Images and Run the Containers ==

	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version.		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version for your architecture.

	$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.23 .		$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.23 .

John: /* Pull the Images and Run the Containers */

2022-05-07T08:51:59Z

Pull the Images and Run the Containers

← Older revision		Revision as of 08:51, 7 May 2022
Line 21:		Line 21:
	== Pull the Images and Run the Containers ==		== Pull the Images and Run the Containers ==

	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated).		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated) for the latest version.

	$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.23 .		$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.23 .

John: /* Pull the Images and Run the Containers */

2022-05-07T08:49:07Z

Pull the Images and Run the Containers

John: /* Pull the Images and Run the Containers */

2022-04-15T05:25:38Z

Pull the Images and Run the Containers

John: /* Pull the Images and Run the Containers */

2022-04-14T21:03:21Z

Pull the Images and Run the Containers

← Older revision		Revision as of 21:03, 14 April 2022
Line 44:		Line 44:
	If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.		If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.

	In order to add additional content to the system, [[the Telstar API]] ~~canb be started e.g~~.		In order to add additional content to the system the Telstar API can be used, this can be started as follows (see [[the Telstar API]] for mor details).

	docker run --rm -d --name telstar-api~~-test~~ --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.3 api --port ~~8011~~ --init		docker run --rm -d --name telstar-api --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.3 api --port 8001 --init

	The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.		The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.

John: /* Pull the Images and Run the Containers */

2022-04-14T21:00:05Z

Pull the Images and Run the Containers

← Older revision		Revision as of 21:00, 14 April 2022
Line 44:		Line 44:
	If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.		If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.

	In order to add additional content to the system, ~~the~~ [[Telstar API]] canb be started e.g.		In order to add additional content to the system, [[the Telstar API]] canb be started e.g.

	docker run --rm -d --name telstar-api-test --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.3 api --port 8011 --init		docker run --rm -d --name telstar-api-test --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.3 api --port 8011 --init

John: /* Pull the Images and Run the Containers */

2022-04-14T20:59:25Z

Pull the Images and Run the Containers

← Older revision		Revision as of 20:59, 14 April 2022
Line 43:		Line 43:

	If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.		If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.

			In order to add additional content to the system, the [[Telstar API]] canb be started e.g.

			docker run --rm -d --name telstar-api-test --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.3 api --port 8011 --init

	The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.		The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.

← Older revision		Revision as of 08:49, 7 May 2022
Line 23:		Line 23:
	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated).		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated).

	$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.4 .		$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.23 .
	$ docker pull mongo		$ docker pull mongo

Line 36:		Line 36:
	The Docker ''run'' command can be used to start the Telstar container and connect it to the previously created network. Note that in the example below the internal port is specified as 6512 and that this is mapped to the same port on the host system. This is also specified at the end of the command to inform TELSTAR that this is the port to listen on.		The Docker ''run'' command can be used to start the Telstar container and connect it to the previously created network. Note that in the example below the internal port is specified as 6512 and that this is mapped to the same port on the host system. This is also specified at the end of the command to inform TELSTAR that this is the port to listen on.

	$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.4 server --port=6512		$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.23 server --port=6512

	In order to add some example content to the system, the ''init'' parameter can be used as in the example below.		In order to add some example content to the system, the ''init'' parameter can be used as in the example below.

	$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.4 server --port=6512 --init		$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.23 server --port=6512 --init

	If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.		If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.
Line 46:		Line 46:
	In order to add additional content to the system the Telstar API can be used, this can be started as follows (see [[the Telstar API]] for mor details).		In order to add additional content to the system the Telstar API can be used, this can be started as follows (see [[the Telstar API]] for mor details).

	docker run --rm -d --name telstar-api --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.4 api --port 8001 --init		docker run --rm -d --name telstar-api --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.23 api --port 8001 --init

	The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.		The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.

← Older revision		Revision as of 05:25, 15 April 2022
Line 23:		Line 23:
	Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated).		Pull the required images as follows (example shows amd64 image, see https://hub.docker.com/repository/docker/johnnewcombe/telstar/tags?page=1&ordering=last_updated).

	$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.3 .		$ docker pull johnnewcombe/telstar:amd64-2.0-RC3.4 .
	$ docker pull mongo		$ docker pull mongo

Line 36:		Line 36:
	The Docker ''run'' command can be used to start the Telstar container and connect it to the previously created network. Note that in the example below the internal port is specified as 6512 and that this is mapped to the same port on the host system. This is also specified at the end of the command to inform TELSTAR that this is the port to listen on.		The Docker ''run'' command can be used to start the Telstar container and connect it to the previously created network. Note that in the example below the internal port is specified as 6512 and that this is mapped to the same port on the host system. This is also specified at the end of the command to inform TELSTAR that this is the port to listen on.

	$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.3 server --port=6512		$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.4 server --port=6512

	In order to add some example content to the system, the ''init'' parameter can be used as in the example below.		In order to add some example content to the system, the ''init'' parameter can be used as in the example below.

	$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.3 server --port=6512 --init		$ docker run --rm -d --name telstar-server --network telstar-network -p 6512:6512 -v telstar-volume:/opt/telstar/volume johnnewcombe/telstar:amd64-2.0-RC3.4 server --port=6512 --init

	If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.		If the ''--init'' switch is used as in the example above, the service will be running with some example content (see [[Example Content]]) and can be accessed using a suitable client.
Line 46:		Line 46:
	In order to add additional content to the system the Telstar API can be used, this can be started as follows (see [[the Telstar API]] for mor details).		In order to add additional content to the system the Telstar API can be used, this can be started as follows (see [[the Telstar API]] for mor details).

	docker run --rm -d --name telstar-api --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.3 api --port 8001 --init		docker run --rm -d --name telstar-api --network telstar-network -p 8011:8011 -e TELSTAR_API_USERID=2222222222 -e TELSTAR_API_PASSWORD=1234 -e TELSTAR_COOKIE_SECRET=b6c7a826-96d6-4f45-88c4-3cf27cc2c647 johnnewcombe/telstar:amd64-2.0-RC3.4 api --port 8001 --init

	The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.		The simplest way to test the system from a desktop machine is to use the [[Telstar Viewdata Client]] alternatively Telnet can be used. TELSTAR is not a Telnet application but telnet can be used to provide a ''sanity check'' e.g.