Servers: sharing one between projects, who can do what, removing one
The Servers page lists every machine your projects run on: the servers you connected yourself, and the servers The Deployer made for your projects in your AWS, Google Cloud, Azure and DigitalOcean accounts. Each card shows what the machine carries, how much of it is promised and used, and what it costs.
Putting a second project on a server you already have
When you choose where a project runs, the architecture page shows On a server you already have. Pick a server, and the project joins it:
- It gets its own folder, its own containers and its own address: the server's plain address, a port, or a hostname you choose.
- Nothing that already runs there is restarted.
- On a server in your cloud account, the project also gets its own login on the machine, and its own port on the cloud firewall. The machine's price is split between the projects on it.
A server that runs one project has to be shared first. Open it on the Servers page and choose Share this server: its web server becomes one shared front door, with a pause of a few seconds, and your certificates are kept.
Projects on one server share one machine and one root account, so they trust each other. Use separate servers for people who must not see each other's work.
Who can do what
The workspace owner and admins decide, person by person, which servers each member may use and how far. Open Team, click the person on the Members tab, and go to the Servers section of the drawer:
- Choose No servers, Chosen servers (pick servers and give each a level) or All servers (one level for every server, including ones added later). Access to a project doesn't include its servers.
- Pick a level. Each one includes the ones before it:
| Level | Lets them |
|---|---|
| See | Open the server and read its status, what runs on it and what it costs. They see only the projects they can open. |
| Operate | Also start, stop, restart, resize and check it. Each affects every project on it. |
| Manage | Also share it between projects, move its default site and set its project limit. |
- Tick Can delete to let them remove a server, and the machine itself in a cloud account. It asks for their own password every time. Only the workspace owner can give this, and an admin doesn't have it unless the owner gives it.
- Click Save changes.
You can set the same in an invite, under Give access now.
Removing a server
Removing a server first lists every project on it and says what happens to each one: it goes back to choosing a server, and its history, settings and environment are kept. You then type the server's name and your own password (and your authenticator code, if your account has one). If the list of projects changes while you are looking, the removal stops and shows you the new list.
- A server you connected yourself is only disconnected. The machine is not wiped. You can also choose to remove what each project put on it.
- A server in your cloud account is only forgotten by default, and keeps running and costing money in your account. Tick Also delete the machine to delete the machine and its disk, and the DNS records The Deployer made for the projects on it. That cannot be undone.
- A server that The Deployer's own site runs on, and a server that carries projects you cannot open, cannot be removed by you.
Deleting a project together with the cloud server it made asks for your password in the same way. Deleting a project that only shares a server never deletes the server.