Give every developer and tester their own environment

Use case · Updated on 12 October 2026

The problem

One shared staging server, several developers and testers. Whoever deployed last wins, QA waits for someone with SSH to put the right build up, and a second test environment means copying compose files, hunting for free ports and remembering to add every new variable to each copy.

How it works in Enver

With Enver, each developer or tester gets an environment of their own on your servers, configured from one shared definition, and switches the image tags in it themselves from the browser – without SSH and without access to production.

Set it up

  1. Describe your services under Services (image, default tag, ports, variables) and put shared values into Variable groups.
  2. Create the first environment, e.g. qa-anna, on your edge server and add the services.
  3. For the next one, choose Duplicate existing and shift the ports by 1000.
  4. Invite the team and give testers Env Tag Switching; in production, block it under the environment’s Permissions.
  5. Optionally connect a Docker Hub webhook, so environments following a branch tag redeploy on every push.

The guide covers each step in detail. Enver is free for up to 2 environments and 10 services, so you can try it with a dev and a QA environment right away.

Questions

Do testers need SSH or Docker access to the server?

No. They work in the browser and see only the environments and permissions you grant them. The agent on the server does the deploying.

Can several environments share one server?

Yes. Duplicating with a port shift keeps their host ports apart, and the Infrastructure view lists every port with its environment and marks any collision.

Does a change to a shared variable reach every environment?

Yes, every environment that doesn’t override it picks the change up the next time its service starts or restarts.