Page MenuHomeDevCentral

Provide Alkane, Nasqueron PaaS to serve PHP and static sites
Open, HighPublic

Description

Alkane is a modern and state-of-art PaaS to automate hosting of PHP and static sites.

It provides the following features:

  • nginx, php-fpm
  • pools separated by application or group of applications
  • Up-to-date PHP versions
  • Automate the deployment, for example:
    • You commit, it's pulled from Git
    • You commit, Jenkins build it, it's pulled from Jenkins artifacts
    • Human-controlled releases for when automated deployment isn't the best fit
  • Secrets live in Vault
  • Databases live on their own cluster (db-A for PostgreSQL, db-B for MySQL)
  • SaaS services can live here too, e.g. saas-mediawiki

It supersedes webserver-legacy role, with a commitment to continue to provide a simple hosting solution, not requiring to create Docker images.


ASCII logo can be C2H6 or CH3-CH3:

    H     H
    |     |
H - C --- C - H
    |     |
    H     H

Event Timeline

Les travaux préparatoires

  • MySQL at db-B-001 is ready, with tooling to migrate databases from Ysul
  • Consolidate the nginx configuration across all the roles, to have a common basis in webserver-core
  • Easter week-end was the opportunity to write T1826, a Rust tool to help sites deployment

Alkane web stack

  • Write units on the top of webserver-core in webserver-alkane, with care to offer the same workflow for PHP and static sites
  • Prepare Vault policy
  • Look if it's currently easy enough for a PHP application to read from Vault ; if not, provide keruald/secrets or keruald/vault or something like that
  • Deploy on web-01

[ Alkane tasks are prioritized to be handled in the next operations sprint. ]

So at this stage, we've PHP and Alkane deployed.

Are missing:

  • nginx configuration (web-001 uses the Ysul folder currently, based on webserver-legacy/nginx)
  • deployment script examples ready to use on Jenkins