Change Details

As a *developer*, *I want* to use a consistent deployment toolset for all Fundraising projects, *so that* bugs are reduced and synergies come into effect. Acceptance Criteria: * FundraisingFrontend uses the atomic-deploy role for app deployment to all hosted stages * Feature is documented in in infrastructure and frontend README * remove cachetool "installed" in FundraisingFrontend directory Background: * There is a prototypical WIP PR https://github.com/wmde/FundraisingFrontend/pull/880

As a *developer*, *I want* to use a consistent deployment toolset for all Fundraising projects, *so that* bugs are reduced and synergies come into effect. Acceptance Criteria: * FundraisingFrontend uses the atomic-deploy role for app deployment to all hosted stages * Feature is documented in in infrastructure and frontend README * remove cachetool "installed" in FundraisingFrontend directory * Should also work in the Docker image from https://phabricator.wikimedia.org/T167289 Background: * There is a prototypical WIP PR https://github.com/wmde/FundraisingFrontend/pull/880

As a *developer*, *I want* to use a consistent deployment toolset for all Fundraising projects, *so that* bugs are reduced and synergies come into effect. Acceptance Criteria: * FundraisingFrontend uses the atomic-deploy role for app deployment to all hosted stages * Feature is documented in in infrastructure and frontend README * remove cachetool "installed" in FundraisingFrontend directory * Should also work in the Docker image from https://phabricator.wikimedia.org/T167289 Background: * There is a prototypical WIP PR https://github.com/wmde/FundraisingFrontend/pull/880