Welcome to the Console V3 alpha testing
It is a closed alpha testing phase, so only authorized users can access the new console. If you want to take part in it, please let me know directly within this thread.
To get access to the Qovery v3 Alpha, click here
(let me know if you have issues accessing the console)
You can always use the V2 via the regular link https://console.qovery.com
This forum section and the discord channel will be our main communication channels.
The objective of this alpha program is to collect valuable feedback from our users during the development phase instead of having a big bang release at some point in Q3. So we would like to keep it as much interactive as possible to gather some precious feedback.
We will proceed in the following way:
- We have prepared a baseline version of the V3 containing only a subset of the features available today on the V2 (see the section below for more details). This will be the version that you can start to test from day 0
- We will enrich this version with new features regularly. We will introduce you to those new features via this forum & the discord channel
- You will be able to test the baseline & new features based on your availability and provide your feedback (see the section below for more details)
Once all the V2 features will be available on the V3 console, we will close this alpha and move into an open beta phase.
The baseline has been built with the following functionalities:
- Environments list: list the available environments, manage the deployment actions (not fully finished), display running / deployment statuses, and manage the deployment rules.
- Service list (Environment page): list the services of an environment, manage the deployment actions, display running / deployment statuses, and list the environment deployments.
- Application page: overview page with instant metrics, manage the deployment actions, display running / deployment statuses, display the deployments.
- Database page: overview page with instant metrics, manage the deployment actions, display running / deployment statuses, and list the service deployments.
For most of the missing features, you will find on the V3 console a link redirecting you to the V2 to complete the action.
We work on a 2-weeks sprint where we develop, test and release the new features.
Once a new feature will be ready to be shipped in production, we will create a post on this forum (+ discord) announcing the new features, similar to a changelog.
(Of course, we will be flexible in terms of release if a blocking bug needs to be corrected ASAP)
When the new features are announced, we would like you to test them as soon as possible. It will be up to you to try them directly on one of your existing environments or create a dedicated one.
If you have any feedback to provide, you can write it directly within the changelog post in this forum. Within your feedback, try to provide as much information as possible, including the URLs, videos, photos etc…
In some special cases, we might also go further and schedule 1:1 sessions to share directly your feedback with me (depending on your availability).
Around September 2021, we launched our V2 console, it was an excellent start to deliver essential features, but we felt like a few things were missing, that’s why almost a year later, we are back with the V3 console, let me walk you through the main changes:
- Smoother user journey: “All the features developers need to scale, available on your AWS account in minutes instead of months” that’s one of the first things you see when you land on our home page. While it was already true with the V2, we wanted to make it even easier with the V3, which meant modifying the onboarding and adding more guidance to every step.
- More transparency: We know those insights are important and for our V3, we decided to provide you with much more insights on your infrastructure, this includes usage and cost.
- Open-source: Our new console is open source, you can find the repository here and feel free to contribute.
- Bonus: Built on React: Back to the end of 2021, when we first started to talk about a V3, this was a very hot topic.
Our V2 was built in Angular, and the question started to pop: should we build the V3 in Angular still or in React? After a few debates, the choice was made, and our V3 is in React; now, there is nothing wrong with Angular, but we felt React would be a better choice for future recruitments.
It’s a closed alpha and only you can have access. If you want to give access to any of your colleagues, please let me know.
The code is completely open-source, you can find it here
The console V3 is pointing to the production environment so that you can test it directly on real use cases (like your test environments). It will be up to you if you prefer to have a dedicated test environment or test it directly on one of your non-critical environments (we discourage testing it on your production environments )
I would recommend using: