Feature Ideas

Support Github Actions CI integration within Qovery

Support Azure to deploy applications

If someone wants to scan all environment variables to confirm they have the correct values, I have to currently click to view each and every one. Show them by default (actually why have hide at all for non-secrets?) I suggest each non-secret key value also be editable inline by default for quick changes. The context menu to edit each one is tedious. The closer you can get this UI to being a simple text file the better in my opinion, though of course the specific fields for name and value make editing safer than a simple file.

It seems like any time an environment variable is updated, a re-deploy with full image re-build is required. This takes a long time. Re-deploys should be optimized as much as possible in case of urgent updates. The rebuild is probably required in case the new variables are needed during image building, but in most cases that is probably not needed. Suggest a way to identify variables that when changed, a new image build is required, vs variables that when changed, simply need the container's environment updated. Or, maybe this can be controlled via docker file layers by the customer, in which case this feature idea is unnecessary. But the goal would be to be able to update a "runtime" variable and redeploy quickly.

Sometimes I may need to store files on S3. Eg: I have a service that received images from users, I need to save the images and expose them publicly.

Support GCP to deploy applications

As a user, I need to be able to import all my environment variables and secrets at once.

Case example: As a user I would like to use a CDN for static sites to serve static assets for my non-static apps built with frameworks like Rails or Django. This would let me turn off the option for Rails to serve static files. In a typical setup, this would be off and static assets would be served directly from the CDN and these requests would never hit the (comparatively slow) Rails app.

Extend Qovery with slack integration add on

Are you interested to control Qovery via Terraform? Vote for and explain why...

Support Docker Compose file to configure a Qovery environment and deploy complete apps.

See and create backups for your databases

Monitor history metrics consumption for CPU, RAM, Storage and Healthcheck for each of your applications and databases.

Create a deploy cronjob with Qovery - a cronjob is a one-time or recurrent process. It can be used to do the batch processing and background compute.

Support Hetzner to deploy applications.