Unify deploy secret keys for the main server

We were using `server` on staging but `server1` and `server2` on
preproduction and production.

The reason behind it is we've always used one server on staging but
sometimes we've used several servers on preproduction and production.

However, this is a bit of a mess on installations which have only one
server on preproduction or production and need to use the `server` key
for the staging environments but `server1` for other environments.

So, in order to keep compatibility with existing Consul installations,
we're now allowing either `server` or `server1` on any environment.
This commit is contained in:
Javi Martín
2023-03-21 19:01:26 +01:00
parent b115b0cc8d
commit 8aa113a47c
5 changed files with 14 additions and 6 deletions

View File

@@ -1,6 +1,6 @@
set :branch, ENV["branch"] || :master
server deploysecret(:server1), user: deploysecret(:user), roles: %w[web app db importer cron background]
server main_deploy_server, user: deploysecret(:user), roles: %w[web app db importer cron background]
#server deploysecret(:server2), user: deploysecret(:user), roles: %w(web app db importer cron background)
#server deploysecret(:server3), user: deploysecret(:user), roles: %w(web app db importer)
#server deploysecret(:server4), user: deploysecret(:user), roles: %w(web app db importer)