Docker - Revision history

Tomjones: /* References */

2021-04-29T20:21:00Z

References

← Older revision		Revision as of 20:21, 29 April 2021
Line 106:		Line 106:

	[[Category: Glossary]]		[[Category: Glossary]]
	[[Category: ~~Best~~ Profile]]		[[Category: Profile]]
	[[Category: Best Practice]]		[[Category: Best Practice]]

Tomjones: /* References */

2021-04-29T20:20:46Z

References

← Older revision		Revision as of 20:20, 29 April 2021
Line 106:		Line 106:

	[[Category: Glossary]]		[[Category: Glossary]]
			[[Category: Best Profile]]
	[[Category: Best Practice]]		[[Category: Best Practice]]

Tomjones: /* Step by Step Instructions */

2021-03-06T05:51:06Z

Step by Step Instructions

← Older revision		Revision as of 05:51, 6 March 2021
Line 57:		Line 57:
	## git pull		## git pull
	## git stash pop (should be just product.yml		## git stash pop (should be just product.yml
	## s Production.sh		## sh Production.sh
	# Copy up the user secrets if required (either using echo 'stuff' > filename.json, or rsh)		# Copy up the user secrets if required (either using echo 'stuff' > filename.json, or rsh)
	# Copy of the https cert if required (rsync -avz ./RegistryTest.pfx root@204.48.19.105:/root/.aspnet/https)		# Copy of the https cert if required (rsync -avz ./RegistryTest.pfx root@204.48.19.105:/root/.aspnet/https)

Tomjones: /* Step by Step Instructions */

2021-03-06T05:50:41Z

Step by Step Instructions

← Older revision		Revision as of 05:50, 6 March 2021
Line 57:		Line 57:
	## git pull		## git pull
	## git stash pop (should be just product.yml		## git stash pop (should be just product.yml
	## Production.sh		## s Production.sh
	# Copy up the user secrets if required (either using echo 'stuff' > filename.json, or rsh)		# Copy up the user secrets if required (either using echo 'stuff' > filename.json, or rsh)
	# Copy of the https cert if required (rsync -avz ./RegistryTest.pfx root@204.48.19.105:/root/.aspnet/https)		# Copy of the https cert if required (rsync -avz ./RegistryTest.pfx root@204.48.19.105:/root/.aspnet/https)

Tomjones: /* Step by Step Instructions */

2021-03-06T02:20:53Z

Step by Step Instructions

← Older revision		Revision as of 02:20, 6 March 2021
Line 52:		Line 52:
	# Make sure that the source file in GitHub is current as the container will be built from the GitHub repository.		# Make sure that the source file in GitHub is current as the container will be built from the GitHub repository.
	# SSH login looks like this: ssh root@0.0.0.0: where you enter the IP address of the droplet and will be prompted for the ssh password.		# SSH login looks like this: ssh root@0.0.0.0: where you enter the IP address of the droplet and will be prompted for the ssh password.
	#Then cd into the newly created directory. (/home/app/..)		#Then cd into the newly created directory. (/home/app/..). (eg cd \homeapp\RegistryDemo)
	#If everything is configured correctly, you should be able to enter docker-compose build and see the output of the process.		#If everything is configured correctly, you should be able to enter docker-compose build and see the output of the process. -- OR
			## git stash
			## git pull
			## git stash pop (should be just product.yml
			## Production.sh
	# Copy up the user secrets if required (either using echo 'stuff' > filename.json, or rsh)		# Copy up the user secrets if required (either using echo 'stuff' > filename.json, or rsh)
	# Copy of the https cert if required (rsync -avz ./RegistryTest.pfx root@204.48.19.105:/root/.aspnet/https)		# Copy of the https cert if required (rsync -avz ./RegistryTest.pfx root@204.48.19.105:/root/.aspnet/https)

Tomjones: /* Step by Step Instructions */

2021-03-06T00:51:19Z

Step by Step Instructions

← Older revision		Revision as of 00:51, 6 March 2021
Line 49:		Line 49:

	The following builds the container directly in the droplet. <<<. preferred mode		The following builds the container directly in the droplet. <<<. preferred mode
	# SSH configuration. Images must have sshd installed and configured to run on boot. If your image does not have sshd set up, you will not have SSH access to Droplets created from that image unless you recover access using the Droplet console.		# SSH configuration. Images must have sshd installed and configured to run on boot. If your image does not have sshd set up, you will not have SSH access to Droplets created from that image unless you recover access using the Droplet console. (DO SERVER.TXT)
	# Make sure that the source file in GitHub is current as the container will be built from the GitHub repository.		# Make sure that the source file in GitHub is current as the container will be built from the GitHub repository.
	# SSH login looks like this: ssh root@0.0.0.0: where you enter the IP address of the droplet and will be prompted for the ssh password.		# SSH login looks like this: ssh root@0.0.0.0: where you enter the IP address of the droplet and will be prompted for the ssh password.

Tomjones: /* Step by Step Instructions */

2021-03-06T00:29:25Z

Step by Step Instructions

← Older revision		Revision as of 00:29, 6 March 2021
Line 48:		Line 48:
	# Optionally check the account: .\doctl.exe account get		# Optionally check the account: .\doctl.exe account get

	The following builds the container directly in the droplet		The following builds the container directly in the droplet. <<<. preferred mode
	# SSH configuration. Images must have sshd installed and configured to run on boot. If your image does not have sshd set up, you will not have SSH access to Droplets created from that image unless you recover access using the Droplet console.		# SSH configuration. Images must have sshd installed and configured to run on boot. If your image does not have sshd set up, you will not have SSH access to Droplets created from that image unless you recover access using the Droplet console.
	# Make sure that the source file in GitHub is current as the ~~contain~~ will be ~~build~~ from the GitHub repository.		# Make sure that the source file in GitHub is current as the container will be built from the GitHub repository.
	# SSH login looks like this: ssh root@0.0.0.0: where you enter the IP address of the droplet and will be prompted for the ssh password.		# SSH login looks like this: ssh root@0.0.0.0: where you enter the IP address of the droplet and will be prompted for the ssh password.
	#Then cd into the newly created directory. (/home/app/..)		#Then cd into the newly created directory. (/home/app/..)

Tomjones: /* Deploy image from GitHub */

2021-01-05T19:18:45Z

Deploy image from GitHub

← Older revision		Revision as of 19:18, 5 January 2021
Line 74:		Line 74:
	# Push contain from workstation to cloud: docker push registry.digitalocean.com/tomjones/tomjones		# Push contain from workstation to cloud: docker push registry.digitalocean.com/tomjones/tomjones

	==Deploy image from GitHub==		===Deploy image from GitHub===
	* [https://www.digitalocean.com/community/tutorials/how-to-install-git-on-ubuntu-18-04 How To Install Git on Ubuntu 18.04]		* [https://www.digitalocean.com/community/tutorials/how-to-install-git-on-ubuntu-18-04 How To Install Git on Ubuntu 18.04]
	* [https://www.digitalocean.com/community/tutorials/how-to-install-git-on-ubuntu-20-04 How To Install Git on Ubuntu 20.04]		* [https://www.digitalocean.com/community/tutorials/how-to-install-git-on-ubuntu-20-04 How To Install Git on Ubuntu 20.04]
Line 89:		Line 89:
	branch.master.remote=origin		branch.master.remote=origin
	branch.master.merge=refs/heads/master		branch.master.merge=refs/heads/master

	==The Environment==		==The Environment==
	Environmental variable are chital to the successful operation of a net core project running in a Linux Docker environment.		Environmental variable are chital to the successful operation of a net core project running in a Linux Docker environment.

Tomjones: /* =The Environment */

2021-01-05T19:17:46Z

=The Environment

← Older revision		Revision as of 19:17, 5 January 2021
Line 89:		Line 89:
	branch.master.remote=origin		branch.master.remote=origin
	branch.master.merge=refs/heads/master		branch.master.merge=refs/heads/master
	===The Environment==		==The Environment==
	Environmental variable are chital to the successful operation of a net core project running in a Linux Docker environment.		Environmental variable are chital to the successful operation of a net core project running in a Linux Docker environment.
	For example:		For example:
	APPDATA in a windows development environment is typically:		*APPDATA in a windows development environment is typically:
	$home ina Linux environment is typically:		*$home ina Linux environment is typically:

	==References==		==References==

Tomjones: /* Deploy image from GitHub */

2021-01-05T19:16:08Z

Deploy image from GitHub

← Older revision		Revision as of 19:16, 5 January 2021
Line 89:		Line 89:
	branch.master.remote=origin		branch.master.remote=origin
	branch.master.merge=refs/heads/master		branch.master.merge=refs/heads/master
			===The Environment==
			Environmental variable are chital to the successful operation of a net core project running in a Linux Docker environment.
			For example:
			APPDATA in a windows development environment is typically:
			$home ina Linux environment is typically:

	==References==		==References==