Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Speed-up and/or reduce re-deployment playbook #5

Open
Apreche opened this issue Jul 18, 2021 · 0 comments
Open

Speed-up and/or reduce re-deployment playbook #5

Apreche opened this issue Jul 18, 2021 · 0 comments

Comments

@Apreche
Copy link
Owner

Apreche commented Jul 18, 2021

The deployment playbook currently contains the entire process for setting up the new instance from almost scratch. This makes sense for the initial release of the new project. However, for further releases, much of this process becomes unnecessary to repeat. There is no need to re-install PostgreSQL every single release.

Even though Ansible will check that it is installed and skip those steps, it may still be beneficial to skip some steps completely. Maybe we can figure out a way to run a different, smaller, playbook for the first release vs. every subsequent release.

There may also be ways to use Ansible caching and other features to dramatically speed up the release process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant