separated stage & prod servers?
Hi! Nico (Acolono) asked me if I could create this ticket
Would it be possible to have the stage/feature websites' server separated from the one with production websites?
From my point of view, I think we need then two Gitlab runners per project. The first could be tagged as deployprod
, and the second as deploystage
for example. And then, GitLab-ci scripts (.deployartefact-ng, CollectConfig, CollectDatabase, CollectFiles, CopyDataToStage, etc) would need some additional logic, so if the branch is 'master' - use deployprod
GitLab runner, but otherwise - use deploystage
runner.
Any other ideas, or concerns?
I can help with some adoptions/testing if needed