Flynn - Revision history

Leaky: /* Generating a trusted TLS cert for a single app */

2018-01-22T21:33:27Z

‎Generating a trusted TLS cert for a single app

2017-07-13T15:31:27Z

‎Generating a trusted TLS cert for a single app

2017-05-18T15:19:16Z

‎Generating a trusted TLS cert for a single app

2017-05-18T15:18:51Z

‎Updating to a new release: adding a trusted TLS cert

2017-04-07T07:50:46Z

‎Accessing files from a job's filesystem: persistent data volume for docker

2017-04-05T08:16:02Z

‎Using a custom TLS wildcard cert during setup

2017-04-05T07:57:59Z

‎Accessing files from a job's filesystem: using a custom tls cert

2017-04-04T15:06:53Z

‎Github repo deployed via webhook: info about files

2017-03-31T08:00:54Z

‎App runs out of space on the overlay partition

2017-03-29T09:35:36Z

‎Updating to a new release

@@ Line 176: / Line 176: @@
 To get the route id, just call flynn route
-  flynn route add http
+  $ flynn -a appname route
 Then using the route id:

@@ Line 167: / Line 167: @@
 === Generating a trusted TLS cert for a single app ===
-Use the client at https://github.com/google/acme to generate the key/certificate pair and then
+Use the client at https://github.com/google/acme
   flynn route add http
 to add the certificate to an application.

@@ Line 165: / Line 165: @@
   CLUSTER_DOMAIN=flynn.bocks.com flynn-host bootstrap --min-hosts 1 --from-backup=/root/backup-$DATE.tar
-== Generating a trusted TLS cert for a single app ==
+=== Generating a trusted TLS cert for a single app ===
 Use the client at https://github.com/google/acme to generate the key/certificate pair and then

@@ Line 164: / Line 164: @@
   service flynn-host start
   CLUSTER_DOMAIN=flynn.bocks.com flynn-host bootstrap --min-hosts 1 --from-backup=/root/backup-$DATE.tar
 == Git requirements ==

← Older revision		Revision as of 07:50, 7 April 2017
Line 89:		Line 89:

	/var/lib/flynn/volumes/zfs/mnt/ext2/$JOBID/overlay-upperdir		/var/lib/flynn/volumes/zfs/mnt/ext2/$JOBID/overlay-upperdir
		+
		+	=== Persistent volume for docker apps ===
		+
		+	Edit the release to indicate the jobs should get a persistent volume
		+
		+	flynn release update /dev/stdin <<< '{"processes": {"app": {"volumes": [{"path": "/data"}]}}}'

	=== Using a custom TLS wildcard cert during setup ===		=== Using a custom TLS wildcard cert during setup ===

@@ Line 91: / Line 91: @@
 === Using a custom TLS wildcard cert during setup ===
   export TLS_CA="
@@ Line 97: / Line 99: @@
   -----END CERTIFICATE-----
+  "
-−
   export TLS_CERT="
   -----BEGIN CERTIFICATE-----
@@ Line 103: / Line 105: @@
   -----END CERTIFICATE-----
+  "
-−
   export TLS_KEY="
   -----BEGIN RSA PRIVATE KEY-----
@@ Line 112: / Line 114: @@
   export CONTROLLER_KEY="..."
   flynn-host bootstrap
 === Updating to a new release ===

← Older revision		Revision as of 07:57, 5 April 2017
Line 89:		Line 89:

	/var/lib/flynn/volumes/zfs/mnt/ext2/$JOBID/overlay-upperdir		/var/lib/flynn/volumes/zfs/mnt/ext2/$JOBID/overlay-upperdir
		+
		+	=== Using a custom TLS wildcard cert during setup ===
		+
		+	export TLS_CA="
		+	-----BEGIN CERTIFICATE-----
		+	...
		+	-----END CERTIFICATE-----
		+	"
		+
		+	export TLS_CERT="
		+	-----BEGIN CERTIFICATE-----
		+	...
		+	-----END CERTIFICATE-----
		+	"
		+
		+	export TLS_KEY="
		+	-----BEGIN RSA PRIVATE KEY-----
		+	...
		+	-----END RSA PRIVATE KEY-----
		+	"
		+
		+	export CONTROLLER_KEY="..."
		+	flynn-host bootstrap

	=== Updating to a new release ===		=== Updating to a new release ===

← Older revision		Revision as of 15:06, 4 April 2017
Line 82:		Line 82:

	See https://github.com/lmars/flynn-webhook-deploy		See https://github.com/lmars/flynn-webhook-deploy
		+
		+	=== Accessing files from a job's filesystem ===
		+
		+	Primarily for use where there is a job running and you need a file it has generated.
		+	ssh to the flynn host and look for the files in
		+
		+	/var/lib/flynn/volumes/zfs/mnt/ext2/$JOBID/overlay-upperdir

	=== Updating to a new release ===		=== Updating to a new release ===

← Older revision		Revision as of 08:00, 31 March 2017
Line 30:		Line 30:

	flynn limit set web temp_disk=200MB		flynn limit set web temp_disk=200MB
		+
		+	This also applies to the mariadb app - if /tmp fills up, this will cause problems so you can expand it in a similar way to above. If you have a lot of data, you may need to increase the deployment timeout first. The following commands set the timeout to 1 hour and then increases the disk space for mariadb to 1GB.
		+
		+	flynn -a mariadb deployment timeout 3600
		+	flynn -a mariadb limit set temp_disk=1G

	=== Restart any app ===		=== Restart any app ===

@@ Line 98: / Line 98: @@
   DATE=`date +%Y%m%d`
   flynn cluster backup --file=/root/backup-$DATE.tar
-−
   service flynn-host stop
   umount /var/lib/flynn/volumes/zfs/mnt/squashfs/*
@@ Line 105: / Line 105: @@
   umount /flynn-default
   umount /tmp/tmp.*/mnt
-−
   curl -fsSL -o /tmp/install-flynn https://dl.flynn.io/install-flynn
   chmod 755 /tmp/install-flynn