Skip to content
/ deploy-code-server Public template

Deploy code-server to the cloud with a few clicks ☁️ πŸ‘¨πŸΌβ€πŸ’»

License

Notifications You must be signed in to change notification settings

coder/deploy-code-server

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

71 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

deploy-code-server πŸš€

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! ☁️

Platform Type Cheapest Plan Deploy
DigitalOcean VM $5/mo, 1 CPU, 1 GB RAM Test
Vultr VM $5/mo, 1 CPU, 1 GB RAM Test
Linode VM $3.50/mo, 1 CPU, 512 MB RAM Test
Railway Deploy Container Free, specs unknown, but very fast πŸš€ Deploy on Railway
Heroku Deploy Container Free, 1 CPU, 512 MB RAM Deploy
Azure App Service Deploy Container Free, 1 CPU, 1 GB RAM see guide

Using a VM vs. Deploying a Container

  • VMs are deployed once, and then can be modified to install new software
    • You need to save "snapshots" to use your latest images
    • Storage is always persistent, and you can usually add extra volumes
    • VMs can support many workloads, such as running Docker or Kubernetes clusters
    • πŸ‘€ Docs for the VM install script
  • App Platforms deploy code-server containers, and are often rebuilt
    • App platforms can shut down when you are not using it, saving you money
    • All software and dependencies need to be defined in the Dockerfile or install script so they aren't destroyed on a rebuild
    • Storage may not be redundant. You may have to use rclone to store your filesystem on a cloud service
    • πŸ“„ Docs for code-server-deploy-container