|
2 | 2 |
|
3 | 3 | A collection of one-click buttons and scripts for deploying code-server to various cloud hosting platforms. The fastest way to get a code-server environment! ☁️ |
4 | 4 |
|
5 | | -| Platform | Type | Cheapest Plan | Deploy | |
6 | | -| ----------------- | ---------------- | ------------------------------------- | -------------------------------------------------------- | |
7 | | -| DigitalOcean | VM | $5/mo, 1 CPU, 1 GB RAM | [see guide](guides/digitalocean.md) | |
8 | | -| Vultr | VM | $5/mo, 1 CPU, 1 GB RAM | coming soon | |
9 | | -| Linode | VM | $3.50/mo, 1 CPU, 512 MB RAM | [see guide](guides/linode.md) | |
10 | | -| Railway | Deploy Container | Free, specs unknown, but very fast 🚀 | [see guide](guides/railway.md) | |
11 | | -| Heroku | Deploy Container | Free, 1 CPU, 512 MB RAM | [see guide](guides/heroku.md) | |
12 | | -| Azure App Service | Deploy Container | Free, 1 CPU, 1 GB RAM | [see guide](https://github.com/bencdr/code-server-azure) | |
| 5 | +| Platform | Type | Cheapest Plan | Deploy | |
| 6 | +| ---------------------------------------------------------------------- | ---------------- | ------------------------------------- | -------------------------------------------------------- | |
| 7 | +| [](https://digitalocean.com) | VM | $5/mo, 1 CPU, 1 GB RAM | [see guide](guides/digitalocean.md) | |
| 8 | +| Vultr | VM | $5/mo, 1 CPU, 1 GB RAM | coming soon | |
| 9 | +| Linode | VM | $3.50/mo, 1 CPU, 512 MB RAM | [see guide](guides/linode.md) | |
| 10 | +| Railway | Deploy Container | Free, specs unknown, but very fast 🚀 | [see guide](guides/railway.md) | |
| 11 | +| Heroku | Deploy Container | Free, 1 CPU, 512 MB RAM | [see guide](guides/heroku.md) | |
| 12 | +| Azure App Service | Deploy Container | Free, 1 CPU, 1 GB RAM | [see guide](https://github.com/bencdr/code-server-azure) | |
13 | 13 |
|
14 | 14 | --- |
15 | 15 |
|
16 | | -## Using a VM vs. Deploying a Container |
| 16 | +## Coding on a VM vs. a Container |
17 | 17 |
|
18 | 18 | - VMs are deployed once, and then can be modified to install new software |
19 | 19 | - You need to save "snapshots" to use your latest images |
20 | 20 | - Storage is always persistent, and you can usually add extra volumes |
21 | 21 | - VMs can support many workloads, such as running Docker or Kubernetes clusters |
22 | | - - [👀 Docs for the VM install script](vm-script/) |
23 | | -- App Platforms deploy code-server containers, and are often rebuilt |
24 | | - - App platforms can shut down when you are not using it, saving you money |
25 | | - - All software and dependencies need to be defined in the `Dockerfile` or install script so they aren't destroyed on a rebuild |
| 22 | + - [👀 Docs for the VM install script](deploy-vm/) |
| 23 | +- Deployed containers do not persist, and are often rebuilt |
| 24 | + - Containers can shut down when you are not using it, saving you money |
| 25 | + - All software and dependencies need to be defined in the `Dockerfile` or install script so they aren't destroyed on a rebuild. THis is great if you want to have a consistant environment every time. |
26 | 26 | - Storage may not be redundant. You may have to use [rclone](https://rclone.org/) to store your filesystem on a cloud service, for info: |
27 | | - - [📄 Docs for code-server-deploy-container](deploy-container/) |
| 27 | +- [📄 Docs for code-server-deploy-container](deploy-container/) |
0 commit comments