OSE Development Server - Revision history

Maltfield: /* Useful Commands */

2022-10-28T20:57:47Z

Useful Commands

← Older revision		Revision as of 20:57, 28 October 2022
Line 51:		Line 51:
	# determine running lxc containers		# determine running lxc containers
	lxc-top		lxc-top

			# start the staging server container
			lxc-start --name osestaging1

	# attach to currently-running staging server container		# attach to currently-running staging server container

Maltfield: added info on how to get info about and connect to staging server's lxc container on dev server

2021-08-06T10:03:00Z

added info on how to get info about and connect to staging server's lxc container on dev server

← Older revision		Revision as of 10:03, 6 August 2021
Line 35:		Line 35:

	# <code>/mnt/ose_dev_volume_1/</code>		# <code>/mnt/ose_dev_volume_1/</code>
			# <code>/mnt/ose_dev_volume_1/var/lib/lxc/</code>
	# <code>/var/</code>		# <code>/var/</code>
	# <code>/etc/crypttab</code>		# <code>/etc/crypttab</code>
	# <code>/etc/fstab</code>		# <code>/etc/fstab</code>
	# <code>/root/keys/</code>		# <code>/root/keys/</code>

			=Useful Commands=

			This section will describe useful commands when working with the OSE Dev Server

			<pre>
			# get list of lxc containers
			ls /mnt/ose_dev_volume_1/var/lib/lxc/

			# determine running lxc containers
			lxc-top

			# attach to currently-running staging server container
			lxc-attach --name osestaging1

			</pre>

	=Initial Creation (Aug 2019)=		=Initial Creation (Aug 2019)=

Maltfield at 05:45, 17 December 2019

2019-12-17T05:45:11Z

← Older revision		Revision as of 05:45, 17 December 2019
Line 1:		Line 1:
			As of 2019, Open Source Ecology has exactly one development server, and this article is specifically about this development server.

			For information about OSE's production server, see [[OSE Server]].

			For information about OSE's staging server, see [[OSE Staging Server]].

	=Purpose=		=Purpose=

Maltfield at 11:37, 23 October 2019

2019-10-23T11:37:08Z

← Older revision		Revision as of 11:37, 23 October 2019
Line 23:		Line 23:

	Note that the rootfs for containers (which accounts for most of the bytes of osedev1's data) lives in /var/lib/lxc.		Note that the rootfs for containers (which accounts for most of the bytes of osedev1's data) lives in /var/lib/lxc.

			===Important Files & Directories===

			For more information about our network-attached block volume configuration, please see the following files & directories on the <code>osedev1</code> server:

			# <code>/mnt/ose_dev_volume_1/</code>
			# <code>/var/</code>
			# <code>/etc/crypttab</code>
			# <code>/etc/fstab</code>
			# <code>/root/keys/</code>

	=Initial Creation (Aug 2019)=		=Initial Creation (Aug 2019)=

Maltfield: /* See Also */

2019-10-23T11:24:22Z

Maltfield at 11:23, 23 October 2019

2019-10-23T11:23:03Z

← Older revision		Revision as of 11:23, 23 October 2019
Line 1:		Line 1:
	=Purpose=		=Purpose=

	The OSE Development Server (osedev1) is a cheap cloud server with a huge network-attahed ~~disk~~. It is a minimal lxc host that also runs our [[VPN]] server. Development (which could be destructive by definition) should not take place on this osedev1 instance, but rather on lxc containers hosted on osedev1.		The OSE Development Server (osedev1) is a cheap cloud server with a huge network-attahed [[#Disk]]. It is a minimal lxc host that also runs our [[VPN]] server. Development (which could be destructive by definition) should not take place on this osedev1 instance, but rather on lxc containers hosted on osedev1.

	=Security=		=Security=

Maltfield at 11:22, 23 October 2019

2019-10-23T11:22:14Z

← Older revision		Revision as of 11:22, 23 October 2019
Line 32:		Line 32:

	==See Also==		==See Also==
			* [[OSE Server]]
			* [[OSE Development Server]]
	* [[Web server configuration]]		* [[Web server configuration]]
	* [[Wordpress]]		* [[Wordpress]]

Maltfield at 11:16, 23 October 2019

2019-10-23T11:16:37Z

← Older revision		Revision as of 11:16, 23 October 2019
Line 1:		Line 1:
	=Purpose=		=Purpose=

	The OSE Development Server (osedev1) is a cheap cloud server with a huge disk. It is a minimal lxc host that also runs our [[VPN]] server. Development (which could be destructive by definition) should not take place on this osedev1 instance, but rather on lxc containers hosted on osedev1.		The OSE Development Server (osedev1) is a cheap cloud server with a huge network-attahed disk. It is a minimal lxc host that also runs our [[VPN]] server. Development (which could be destructive by definition) should not take place on this osedev1 instance, but rather on lxc containers hosted on osedev1.

	=Security=		=Security=

Maltfield at 11:16, 23 October 2019

2019-10-23T11:16:18Z

← Older revision		Revision as of 11:16, 23 October 2019
Line 2:		Line 2:

	The OSE Development Server (osedev1) is a cheap cloud server with a huge disk. It is a minimal lxc host that also runs our [[VPN]] server. Development (which could be destructive by definition) should not take place on this osedev1 instance, but rather on lxc containers hosted on osedev1.		The OSE Development Server (osedev1) is a cheap cloud server with a huge disk. It is a minimal lxc host that also runs our [[VPN]] server. Development (which could be destructive by definition) should not take place on this osedev1 instance, but rather on lxc containers hosted on osedev1.

	~~==Disk==~~

	Unless otherwise required, the cheapest cloud instance is used for this server. The biggest bottleneck is the disk. The solution to this is to mount a block storage volume. Specifically, a very large (resizeable) disk (max 10T?) is mounted on /var/ <ref>[[Maltfield_Log/2019_Q4#Tue_Oct_08.2C_2019]]</ref>

	~~Note that the rootfs for containers (which accounts for most of the bytes of osedev1's data) lives in /var/lib/lxc.~~

	=Security=		=Security=
Line 23:		Line 17:

	Both of these services must be hardened. All developers working on the OSE Dev server should first authenticate to OpenVPN. Once given a "local" IP address by OpenVPN, they can freely & securely interact with the dev server.		Both of these services must be hardened. All developers working on the OSE Dev server should first authenticate to OpenVPN. Once given a "local" IP address by OpenVPN, they can freely & securely interact with the dev server.

			==Disk==

			Unless otherwise required, the cheapest cloud instance is used for this server. The biggest bottleneck is the disk. The solution to this is to mount a block storage volume. Specifically, a very large (resizeable) disk (max 10T?) is mounted on /var/ <ref>[[Maltfield_Log/2019_Q4#Mon_Oct_07.2C_2019]]</ref>

			Note that the rootfs for containers (which accounts for most of the bytes of osedev1's data) lives in /var/lib/lxc.

	=Initial Creation (Aug 2019)=		=Initial Creation (Aug 2019)=

Maltfield at 11:12, 23 October 2019

2019-10-23T11:12:06Z

← Older revision		Revision as of 11:12, 23 October 2019
Line 5:		Line 5:
	==Disk==		==Disk==

	Unless otherwise required, the cheapest cloud instance is used for this server. The biggest bottleneck is the disk. The solution to this is to mount a block storage volume. Specifically, a very large (resizeable) disk (max 10T?) is mounted on /var/. Note that the rootfs for containers (which accounts for most of the bytes of osedev1's data) lives in /var/lib/lxc.		Unless otherwise required, the cheapest cloud instance is used for this server. The biggest bottleneck is the disk. The solution to this is to mount a block storage volume. Specifically, a very large (resizeable) disk (max 10T?) is mounted on /var/ <ref>[[Maltfield_Log/2019_Q4#Tue_Oct_08.2C_2019]]</ref>

			Note that the rootfs for containers (which accounts for most of the bytes of osedev1's data) lives in /var/lib/lxc.

	=Security=		=Security=

← Older revision		Revision as of 11:24, 23 October 2019
Line 33:		Line 33:
	==See Also==		==See Also==
	* [[OSE Server]]		* [[OSE Server]]
	* [[OSE ~~Development~~ Server]]		* [[OSE Staging Server]]
	* [[Web server configuration]]		* [[Web server configuration]]
	* [[Wordpress]]		* [[Wordpress]]