This way, you can even update the credentials in a single place if they expire and not have your next deployments fail.

I'm also trying to not rely on AI to rewrite what I want to say, I've been so dependant on it that I may have lost some vocabulary and spelling skills.

Instead of being scared to sound bad or rude, I should trust myself more... I think you should too 🫵

I've noticed that I'm losing some fundamental skills, mainly how to find information and fix issues.

So I'm trying to change that by actually trying to not rely on the AI tools that much and actually looking on the web and honing my finding solutions and fixing bugs skills

This is the first step towards supporting multi server on ZaneOps.

The images can be stored either directly on your server or in AWS/S3 compatible service to optimize the storage on your server.

This is the first step towards supporting multi server on ZaneOps.

😉

More details in the release notes: zaneops.dev/changelog/v1...

You also get a new design for the dashboard of ZaneOps:

Alongside that you get Account settings brought to you by @ahmedbaset.dev

To do that, you use "preview templates" with pre-configured options for your preview environments.

You can add as much templates as you want per project and choose which preview to use via API

However compared to other preview deployments on other PaaS, you have the choice to modify this default behavior and either tests your features in total isolation or share a service (like the DB) across previews:

more details: zaneops.dev/knowledge-ba...

The main feature in this release is preview environments - not just deployments, but full isolated environments.

They create an ephemeral copy of your base environment to test features safely.

You can either trigger a preview via API or from a Pull Request.