From b115b0cc8d7d1bece2ccd5b17c4bd40d771de937 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Javi=20Mart=C3=ADn?= Date: Mon, 27 Feb 2023 17:03:20 +0100 Subject: [PATCH] Use only one server when deploying to preproduction It doesn't make much sense that by default we use one server on production on two servers on preproduction. Note we're keeping `server1` instead of using just `server` in order to keep compatibility with existing installation. --- config/deploy-secrets.yml.example | 1 - config/deploy/preproduction.rb | 1 - 2 files changed, 2 deletions(-) diff --git a/config/deploy-secrets.yml.example b/config/deploy-secrets.yml.example index 26c5a38f6..62caca99f 100644 --- a/config/deploy-secrets.yml.example +++ b/config/deploy-secrets.yml.example @@ -8,7 +8,6 @@ preproduction: deploy_to: "/home/deploy/consul" ssh_port: "2222" server1: xxx.xxx.xxx.xxx - server2: xxx.xxx.xxx.xxx user: "deploy" production: diff --git a/config/deploy/preproduction.rb b/config/deploy/preproduction.rb index 7bbc3755a..ca225008f 100644 --- a/config/deploy/preproduction.rb +++ b/config/deploy/preproduction.rb @@ -1,4 +1,3 @@ set :branch, ENV["branch"] || :master server deploysecret(:server1), user: deploysecret(:user), roles: %w[web app db importer cron background] -server deploysecret(:server2), user: deploysecret(:user), roles: %w[web app db importer]