Multiple targets

[YuukanOO]

For now, seelf only support deploying application on a local Docker engine.

The goal is to support multiple providers inside a seelf instance. The simplest one will be a remote Docker engine and we can investigate some initial support for Podman, Docker Swarm or Kube

Initial version roadmap

• Add a Target resource representing where seelf applications could be deployed with:
  • A unique id
  • A name (could be anything since it will only be used for tooltips and such)
  • A unique domain url (for the first version, only allow one domain per target, this will be extended to support multiple domains per target in the future but keep it simple for now)
  • A provider specific configuration with everything needed to connect to local/remote host. This one should be bound to a specific provider just like SourceData. So for example, a docker provider configuration will include an host and a private ssh key
• Remove configuration related to the balancer (since it will now be configured on a per target basis)
• Add a target property to app environments so an environment will now include a target and service variables
• Add target to deployment config
• Providers will receive a Target when deploying or cleaning stuff and they should appropriately setup it the first time they have to deal with it. This way, if a user deletes a proxy configuration, just restart seelf and the first deployment on that target will redeploy the proxy needed to make the application available
• Changing an app environment target should clear that specific environment on the old target (it should happen on the first successful deployment on a different target)
• App's name unicity will now be based on name, production_target and staging_target so multiple apps with the same name will be allowed only if they are not deployed on the target (because for now, one target equals one domain)

Configuring a target for Docker will use an ssh config file to configure Host / Identity file to use by using the target specific private key.

Not part of the first version

• Multiple domains per target
• Generates private key if no one is provided
• Multiple targets per host and configurable proxy ports (See Multiple targets #1 (comment))

[YuukanOO]

Allow multiple targets to run on the same server. For this one to work, they should use different ports and use traefik constraints to handle only applications they should handle.

[YuukanOO]

Allow multiple targets to run on the same server. For this one to work, they should use different ports and use traefik constraints to handle only applications they should handle.

This one will be delayed because HTTP or TLS challenge are only allowed on the default ports (80 and 443).

[YuukanOO]

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

• v2.0.0
• GitHub release

Your semantic-release bot 📦🚀