GitHub Codespaces, Azure, and DigitalOcean: what is common, what differs, and how to choose
Prof. Fred Agbo
2026-11-04
🚀 Pick a path and ship it
AI 380: Human-AI Interaction
Your assistant works in rasa inspect. Now make it reachable by other people.
Free: GitHub Codespaces, Azure for Students
Paid: DigitalOcean
Shared: the same preparation for all three
🎯 Goals for this session
By the end you can:
Explain what every deployment needs before you pick a host.
Compare the three options by cost, uptime, and effort.
Choose one and justify it.
Start deploying your own assistant by following its basic steps.
Detailed walkthroughs exist for Azure and Codespaces. This deck is the map.
🗺️ Three options at a glance
GitHub Codespaces
Azure VM
DigitalOcean Droplet
Cost
Free allowance
Student credit
Paid (monthly)
Always on
No (idle stop)
Yes
Yes
Public URL for others
Not for long
Yes
Yes
Free HTTPS name
Yes (forwarded port)
Yes (cloudapp.azure.com)
No (bring a domain)
Setup effort
Lowest
Highest
Medium
Best for
Labs, demos, testing
Graded, free, online
Simple, reliable, paid
🔁 The shared pipeline
flowchart LR
A["✅ Works in<br/>rasa inspect"] --> B["📋 Pre-deployment<br/>(same for all)"]
B --> C{"Choose a host"}
C --> D["🧑💻 Codespaces"]
C --> E["☁️ Azure VM"]
C --> F["🌊 DigitalOcean"]
D --> G["▶️ Run + verify"]
E --> G
F --> G
G --> H["🛑 Update, stop,<br/>clean up"]
① Common pre-deployment
Part 1 · Do this before choosing a host
Docker → GitHub → front end → secrets → protection
📋 Pre-deployment checklist
Step
What
Why
1
Finish and test with rasa train + rasa inspect
Never debug on a server what you can debug locally
2
Note rasa --version
Server must run the same version
3
Put keys in environment variables
No secrets in files or git
4
Containerize: official Rasa image + Compose
Same run command everywhere
5
Push to GitHub (without secrets or models/)
Every host pulls from here
6
Decide the front end: Inspector or webchat.html
Decides what users open
7
Plan protection: HTTPS + password
Your LLM key and user logs are at stake
🐳 Step 4 · Docker, the minimal way
You do not need your own Dockerfile. Use Rasa’s official image and mount your project:
Password: a login before any request reaches Rasa.
Ports: only 80/443 public. Never publish Rasa’s 5005.
Logs:lesson_log.jsonl has user IDs. Know who can read it and delete it when done.
An open Rasa URL lets strangers spend your LLM key.
✅ Pre-deployment checkpoint
Before you pick a host, you can say yes to all of these:
Works in rasa inspect, and I know my Rasa version
Keys are in environment variables
Project is on GitHub without .env, models/, or the log
I chose Inspector or webchat.html
I know how I will add HTTPS and a password
② The three options
Part 2 · Basic steps for each
Free · Free · Paid
🧑💻 Option A · GitHub Codespaces
What it is: a cloud dev machine in your browser, tied to your repo.
Strength
Limit
No server to manage; Docker ready
Stops after about 30 idle minutes
HTTPS URL comes from port forwarding
Free hours are limited (roughly 120 core hours a month)
Everyone gets the same environment
Not an always-on site
Best for: class labs, demos, and testing before a real deploy.
🧑💻 Codespaces · Basic steps
Repo → Code → Codespaces → Create codespace.
Add .devcontainer/devcontainer.json (Python, Docker-in-Docker, ports 5005 and 8000).
Add RASA_LICENSE and your LLM key as Codespaces secrets.
Train and run: rasa train, then rasa inspect (or the Compose command).
In the Ports tab, open the forwarded 5005 URL.
Stop the codespace when done.
Keep Rasa’s port Private. Use a 4-core machine for training.
☁️ Option B · Azure VM
What it is: a Linux VM you control, paid from student credit.
Strength
Limit
Free for students (credit, no card)
Most steps to set up
Always on, with a free cloudapp.azure.com name
A 4 GB VM uses credit, not the free VM allowance
Good fit for a graded, public URL
Billing continues until you deallocate
Best for: a free, always-on deployment you can submit.
☁️ Azure · Basic steps
Create the account and a 5 USD budget alert.
Cloud Shell: create a resource group and a 4 GB Ubuntu VM with a DNS label.
Open ports 80 and 443.
SSH in and install Docker.
Clone the repo, create deploy/.env, run docker compose run --rm assistant train.
docker compose up -d, then open your https:// address.
Deallocate when idle; delete the resource group at the end.
🌊 Option C · DigitalOcean
What it is: a simple paid cloud server (a Droplet).
Strength
Limit
Clean interface and flat, predictable pricing
Costs money from the first hour
Docker-ready images and quick setup
No free HTTPS hostname: bring a domain
Always on
Bill continues until you destroy the Droplet
Best for: the simplest reliable paid option, or when you outgrow free credit.
🌊 DigitalOcean · Basic steps
Create an account and add a payment method (or apply credit).
Create a Droplet: Ubuntu, about 2 vCPU and 4 GB RAM, with your SSH key.
Add a firewall allowing 22, 80, 443.
Point a domain’s A record at the Droplet’s IP.
SSH in, install Docker, clone the repo, create deploy/.env with that domain.
Train, then docker compose up -d.
When finished, destroy the Droplet.
🌐 The domain question
Azure gives a free name. DigitalOcean does not.
Option
Notes
Your own domain
Add an A record to the server IP. Cleanest
A wildcard-DNS service that maps an IP to a name
Free and quick for a class demo, but shared certificate limits may bite; verify it works
HTTPS needs a name, not a bare IP address.
⚖️ Compare, side by side
Question
Codespaces
Azure
DigitalOcean
Money
Free quota
Student credit
Monthly bill
Someone else can visit tomorrow
No
Yes
Yes
Caddy/HTTPS to configure
No
Yes
Yes
Memory for Rasa Pro
Pick 4-core
Pick 4 GB VM
Pick 4 GB Droplet
Risk if you forget it
Hours used up
Credit spent
Money spent
Typical lab effort
Short
Longest
Medium
🧭 How to choose
flowchart TD
A["Do others need to visit<br/>your URL after class?"] -->|No| B["🧑💻 Codespaces"]
A -->|Yes| C["Free required?"]
C -->|Yes| D["☁️ Azure for Students"]
C -->|No| E["Want the simplest<br/>always-on server?"]
E -->|Yes| F["🌊 DigitalOcean"]
E -->|No| D
💡 Recommendations and why
Situation
Choose
Justification
First try, class lab, debugging
Codespaces
Nothing to provision; same environment for everyone; free
Graded project that must stay online, no budget
Azure
Free credit, always on, free HTTPS hostname
Reliable demo, willing to pay, want less friction
DigitalOcean
Simpler interface and pricing; you handle the domain
Not sure
Codespaces first, then Azure
Learn the pieces cheaply, then deploy for real
③ Together in class
Part 3 · Try it, troubleshoot, reflect
Choose → deploy → verify → share what broke
🧪 Class activity
Choose one option.
Finish pre-deployment (the checklist) and show your repo.
Deploy using that option’s basic steps and the detailed deck.
Verify: the Inspector (or webchat.html) works at your URL and the log has events.
Clean up: stop, deallocate, or destroy.
Pairs are fine. Help classmates on other options when you finish.
Done when: you completed a guided lesson at your own URL and can name one thing that went wrong.
🧯 Common problems on every host
Symptom
Likely cause → Fix
License or LLM error at startup
Missing or misnamed variable → check .env / secrets
“No model found”
Not trained on the server → run train
Version warning
Image tag differs from yours → align and retrain
Page loads but chat cannot connect
Wrong public URL, or CORS → use the https address; same origin
Certificate fails
Port 80 blocked or wrong domain → open ports, check DOMAIN
Out of memory
Machine too small → 4 GB or larger
Works locally, not remotely
Secret or file missing in git → compare with .gitignore
💸 Cost and safety, every time
Set a budget alert before creating anything.
Stop (Codespaces), deallocate (Azure), or destroy (DigitalOcean) when you finish.
Never leave Rasa’s port open to the internet.
Never post a URL and its password together.
Delete lesson_log.jsonl when the course ends.
Most surprise bills come from something left running.
💭 Discussion
Which option would you pick for a real older-adult user, and why?
The Inspector exposes History and Memory. Should end users see that? What does webchat.html let you hide or show?
A password protects your LLM key. What other risks come with a public coach?
If your host disappears tomorrow, how fast can you redeploy? What does that say about your repo?