Skip to content

ZaneOps v1.7

Release notes: https://github.com/zane-ops/zane-ops/releases/tag/v1.7.0

22 Mar 2025 by Fred KISSIE

Since the release of v1.0, we added a lot more changes.

To install :

Terminal window
# assuming you are at /var/www/zaneops
curl https://cdn.zaneops.dev/makefile > Makefile
make setup
make deploy

Environments let you separate your services logically accross isolated instances. Within environments you can share environment variables available accross all the services within the environment. You can learn more here.

project environments page project environments page

You can clone environments and copy all the services, variables and configurations to the new environment :

clone environment modal clone environment modal

Accross environments you can also have multiple services with the same name :

searching a service accross multiple environments searching a service accross multiple environments

Now, when you install ZaneOps on a blank instance, you will be greated by an onboarding page allowing you to create a first user directly from the UI rather than only from the terminal :

onboarding page with a form for creating the first user onboarding page with a form for creating the first user

Starting with v1.7.0, future upgrades will trigger a toast notification informing you of new ZaneOps versions, enabling you to upgrade directly from the UI instead of relying solely on the terminal.

clone environment modal clone environment modal project environments page project environments page
  • Changed the logs configuration to only logs the result of monitoring health checks if they fail, significantly reducing clutter on the logs page
  • Added confirmation modals for destructive actions, for when you want to delete a project, environment or service : delete environment confirmation modal delete project confirmation modal delete service confirmation modal toggle sleep service confirmation modal
  • We fixed some occasional 502 Bad Gateway error you would encounter when you deploy services in #406
  • We fixed some bugs with the metrics not being collected correctly and resulting in you not seeing the metrics of certain services in #383