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.
- One definition, many environments. Each service is described once. Values every environment needs live in the service defaults and in variable groups; an environment sets only what differs, such as its database URL.
- A new environment in a minute. Duplicate existing copies every service with its tag, settings, variables and groups, and Shift exposed ports moves its ports (8080 becomes 9080) so nothing collides on the server. Enver refuses a shift that hits a taken port and suggests a free one.
- Deploy without editing. The Env Tag Switching permission lets someone switch tags, restart services and read logs, but not change the configuration. Tags are suggested from the registry, and Service groups switch a whole backend at once.
- Production stays off limits. Per-environment permissions grant or block access in one environment only, e.g. tag switching everywhere except production.
- Everyone sees the state. Live status, uptime and logs per service, a note on the environment card for the app’s addresses, and a push notification when a service starts running a new image.
Set it up
- Describe your services under Services (image, default tag, ports, variables) and put shared values into Variable groups.
- Create the first environment, e.g.
qa-anna, on your edge server and add the services. - For the next one, choose Duplicate existing and shift the ports by 1000.
- Invite the team and give testers Env Tag Switching; in production, block it under the environment’s Permissions.
- 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.