Operations grimoire/Alkane - Revision history

Duranzed: /* Guides */

2026-02-19T14:22:02Z

Guides

← Older revision		Revision as of 14:22, 19 February 2026
Line 17:		Line 17:

	'''Devserver.''' subdomain.domain.tld CNAME www-dev.nasqueron.org		'''Devserver.''' subdomain.domain.tld CNAME www-dev.nasqueron.org

			[[File:alkane.png\|thumb\|Alkane workflow]]

	==== nginx ====		==== nginx ====
Line 32:		Line 34:
	;Through Salt:		;Through Salt:
	{{Ops file\|roles/webserver-content}} can provision configuration for your site, especially if you need content elsewhere than in /var/wwwroot/<domain.tld>/<sub> (that content is for Jenkins to provision)		{{Ops file\|roles/webserver-content}} can provision configuration for your site, especially if you need content elsewhere than in /var/wwwroot/<domain.tld>/<sub> (that content is for Jenkins to provision)

	~~[[File:alkane.png\|thumb\|Alkane workflow]]~~

	==== Database ====		==== Database ====

Duranzed at 14:21, 19 February 2026

2026-02-19T14:21:24Z

← Older revision		Revision as of 14:21, 19 February 2026
Line 10:		Line 10:

	Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].		Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].

	~~[[File:alkane.png\|thumb\|Scheme]]~~

	== Guides ==		== Guides ==
Line 34:		Line 32:
	;Through Salt:		;Through Salt:
	{{Ops file\|roles/webserver-content}} can provision configuration for your site, especially if you need content elsewhere than in /var/wwwroot/<domain.tld>/<sub> (that content is for Jenkins to provision)		{{Ops file\|roles/webserver-content}} can provision configuration for your site, especially if you need content elsewhere than in /var/wwwroot/<domain.tld>/<sub> (that content is for Jenkins to provision)

			[[File:alkane.png\|thumb\|Alkane workflow]]

	==== Database ====		==== Database ====

Duranzed at 14:20, 19 February 2026

2026-02-19T14:20:16Z

← Older revision		Revision as of 14:20, 19 February 2026
Line 11:		Line 11:
	Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].		Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].

	[[File:alkane.png\|Scheme]]		[[File:alkane.png\|thumb\|Scheme]]

	== Guides ==		== Guides ==

Duranzed at 14:19, 19 February 2026

2026-02-19T14:19:38Z

← Older revision		Revision as of 14:19, 19 February 2026
Line 10:		Line 10:

	Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].		Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].
	[[File:alkane.png\|~~Caption text~~]]
			[[File:alkane.png\|Scheme]]

	== Guides ==		== Guides ==
	=== Host a new site ===		=== Host a new site ===

Duranzed at 14:18, 19 February 2026

2026-02-19T14:18:51Z

← Older revision		Revision as of 14:18, 19 February 2026
Line 10:		Line 10:

	Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].		Alkane is a work in progress to track at [https://devcentral.nasqueron.org/T1803 T1803].
			[[File:alkane.png\|Caption text]]
	== Guides ==		== Guides ==
	=== Host a new site ===		=== Host a new site ===

Dereckson: .env documentation

2023-06-27T20:51:36Z

.env documentation

← Older revision		Revision as of 20:51, 27 June 2023
Line 44:		Line 44:

	We're here to help, create a task on DevCentral with your ideas and we can offer architecture guidance and tips to host it in the best conditions.		We're here to help, create a task on DevCentral with your ideas and we can offer architecture guidance and tips to host it in the best conditions.

			=== Provision credentials with .env ===

			You can use the <code>webserver_content_dotenv</code> pillar to generate .env files.

			Those files allow sites using libraries like DotEnv to read secrets.

			To ensure secrets can only be read by application user, use:

			user: <php-fpm pool user>

			If your configuration can be read and stored in memory,
			it's probably best to directly call Vault from the app
			and only provision Vault AppRole credentials:

			vault: <path to AppRole credential>

			For PHP sites where the configuration file is read every
			request, it's probably best to cache secrets in file
			through this mechanism.

			If you need a database, you can use:

			db:
			service: entry in nasqueron_services table
			credentials: path to Vault secret

			To provision a secret key or other credentials, use:

			extra_credentials:
			key: path to vault secret

			If you need to pass extra plain values use:

			extra_values:
			key: value

	=== Migrate from Ysul ===		=== Migrate from Ysul ===

Dereckson at 22:12, 30 May 2023

2023-05-30T22:12:30Z

← Older revision		Revision as of 22:12, 30 May 2023
Line 18:		Line 18:
	'''Devserver.''' subdomain.domain.tld CNAME www-dev.nasqueron.org		'''Devserver.''' subdomain.domain.tld CNAME www-dev.nasqueron.org

	==== nginx ===		==== nginx ====
	* In {{Ops file\|pillar/paas/alkane/web-001/}} add the subdomain in nginx_vhosts		* In {{Ops file\|pillar/paas/alkane/web-001/}} add the subdomain in nginx_vhosts
	* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file		* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file

Dereckson: /* = Auto-provisioning */

2023-05-30T22:12:11Z

= Auto-provisioning

← Older revision		Revision as of 22:12, 30 May 2023
Line 22:		Line 22:
	* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file		* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file

	==== Auto-provisioning ===		==== Auto-provisioning ====

	;Through Jenkins:		;Through Jenkins:

Dereckson: /* Host a new site */

2023-05-30T22:11:56Z

Host a new site

← Older revision		Revision as of 22:11, 30 May 2023
Line 13:		Line 13:
	== Guides ==		== Guides ==
	=== Host a new site ===		=== Host a new site ===
	'''~~DNS~~.''' subdomain.domain.tld CNAME www-alkane.nasqueron.org		==== DNS ====
			'''Production.''' subdomain.domain.tld CNAME www-alkane.nasqueron.org

	; nginx		'''Devserver.''' subdomain.domain.tld CNAME www-dev.nasqueron.org

			==== nginx ===
	* In {{Ops file\|pillar/paas/alkane/web-001/}} add the subdomain in nginx_vhosts		* In {{Ops file\|pillar/paas/alkane/web-001/}} add the subdomain in nginx_vhosts
	* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file		* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file

	~~'''~~Auto-~~provisionning.'''~~ Through Jenkins:		==== Auto-provisioning ===

			;Through Jenkins:
	* A CD job to deploy specific releases or your last commit		* A CD job to deploy specific releases or your last commit
	* Nothing fancy? You can adopt a standard job template "git fetch --all && git switch <new tag>" or the job "ensure you're on main then git pull"		* Nothing fancy? You can adopt a standard job template "git fetch --all && git switch <new tag>" or the job "ensure you're on main then git pull"
Line 25:		Line 30:
	* Jenkins build scripts can be ported to Dockerfile if you prefer to host the PHP site on our Docker PaaS		* Jenkins build scripts can be ported to Dockerfile if you prefer to host the PHP site on our Docker PaaS

	~~'''~~Salt~~.'''~~ {{Ops file\|roles/webserver-content}} can provision configuration for your site, especially if you need content elsewhere than in /var/wwwroot/<domain.tld>/<sub> (that content is for Jenkins to provision)		;Through Salt:
			{{Ops file\|roles/webserver-content}} can provision configuration for your site, especially if you need content elsewhere than in /var/wwwroot/<domain.tld>/<sub> (that content is for Jenkins to provision)

			==== Database ====

			'''PostgreSQL.''' Hosted on db-A cluster, see [[Operations grimoire/PostgreSQL]]

	'''~~Database~~.''' Hosted ~~separately,~~ on cluster ~~A for PostgreSQL~~, ~~B for~~ MySQL		'''MySQL.''' Hosted on db-B cluster, see [[Operations grimoire/MySQL]]

	'''Redis/memcached/etc.''' There are fully supported. For more complex applications, there are two roads: (i) the Docker PaaS, look for example how are deployed Airflow, Sentry and Penpot stacks (ii) we create role/saas-<app> and we look if it's suitable for Alkane or if we create a specific server for that app.		'''Redis/memcached/etc.''' There are fully supported. For more complex applications, there are two roads:
			* (i) the Docker PaaS, look for example how are deployed Airflow, Sentry and Penpot stacks;
			* (ii) we create role/saas-<app> and we look if it's suitable for Alkane or if we create a specific server for that app.

	We're here to help, create a task on DevCentral with your ideas and we can offer architecture guidance and tips to host it in the best conditions.		We're here to help, create a task on DevCentral with your ideas and we can offer architecture guidance and tips to host it in the best conditions.

Dereckson: /* Host a new site */

2023-05-30T22:07:33Z

Host a new site

← Older revision		Revision as of 22:07, 30 May 2023
Line 13:		Line 13:
	== Guides ==		== Guides ==
	=== Host a new site ===		=== Host a new site ===
	'''DNS.''' subdomain.domain.tld CNAME ~~www1~~.nasqueron.org		'''DNS.''' subdomain.domain.tld CNAME www-alkane.nasqueron.org

			; nginx
			* In {{Ops file\|pillar/paas/alkane/web-001/}} add the subdomain in nginx_vhosts
			* In {{Ops file\|roles/webserver-alkane/nginx/files/vhosts/}} add the nginx configuration file

	'''Auto-provisionning.''' Through Jenkins:		'''Auto-provisionning.''' Through Jenkins: