The Future of Qovery - Week #2
During the next nine weeks, our team will work to improve the overall experience of Qovery. We gathered all your feedback (thank you to our wonderful community 🙏), and we decided to make significant changes to make Qovery a better place to deploy and manage your apps.
This series will reveal all the changes and features you will get in the next major release of Qovery. Let's go!
Read the previous article: The Future of Qovery - Week #1.
Qovery has been built to manage complex Production, Staging, and Dev environments seamlessly. Complex means that your production environment has probably up to hundreds of applications, and you may want to keep synchronized your staging and dev environments from your production environment. Qovery promises to keep you safe from any bug while promoting your changes in production.
Each Git branch that the developer creates is an Environment. It is very convenient to validate your pull requests/bug fixes/improvements with the same configuration as if it was in production.
Thanks to our community for their hundreds of feedback using Qovery. We decided to enhance the Environment interface by giving you more granular control over your applications, databases, and other resources.
For instance, with the new Environment interface you'll be able to:
Restart, pause, stop a single application or database
Rollback a single application
Know exactly who made an action
See the full deployment history
Get alerted if something goes wrong
And this is only the beginning. Besides simplifying application deployment in the Cloud, Qovery's goal is to make you and your team focusing on what you do best — developing great products.
See you next week — same hour, same place. 👋
Join the community on Discord to give your feedback.