Deployment module
Choosing a Hosting Path
Choose between traditional shared hosting, manual static hosting, and Git-connected deployment using realistic student and business scenarios.
Learning Objectives
By the end of this lesson, you'll be able to:
- Compare traditional shared hosting, manual static hosting and Git-connected hosting
- Match hosting paths to realistic project scenarios
- Explain how update workflows differ
- Check provider terms without treating changing prices as permanent facts
Why This Matters:
A sensible hosting choice fits the project, the update workflow, support needs and account ownership.
Three Beginner Deployment Paths
Choosing hosting is not about finding the one perfect provider. It is about choosing a path that matches the project and the person who will maintain it. A classroom exercise can tolerate a simpler workflow than a client site with renewals, email and support responsibilities.
How Updates Reach the Live Site
Edit -> Zip -> Upload
Edit -> Save -> Upload changed files with SFTP
Edit -> Commit -> Push -> Automatic deploymentThe first workflow is simple but easy to lose track of. The second is more controlled if you know which changed files matter. The third is repeatable and traceable, but only once Git basics make sense.
| Question | Shared hosting | Manual static hosting | Git-connected hosting |
|---|---|---|---|
| Who is it best for? | Small business sites needing traditional account tools. | Quick static exercises and demonstrations. | Ongoing projects where changes should be traceable. |
| What can go wrong? | Wrong public folder, unclear ownership, renewal surprises. | Wrong upload folder, stale files, missing build output. | Wrong branch, failed build command, missing environment variables. |
| What should be recorded? | Account owner, renewal date, web root, support process. | Upload method, public URL, source folder, last upload date. | Repository, branch, build command, output directory, deploy URL. |
Hosting Decision Exercise
Now try this on your own without hints!
Your Task:
Choose a hosting path for each scenario and explain why.
Requirements:
- Scenario A: a small HTML and CSS classroom exercise
- Scenario B: a Vite portfolio project that will be updated regularly
- Scenario C: a small business website requiring reliable support, email and clear account ownership
Stretch Goals (Optional):
- Name one risk for each path
- List which provider details must be checked before purchase or signup
Hosting Path Knowledge Check
Before moving forward, can you answer these?
- Which path suits a Vite portfolio that will be updated regularly?
- Which path may suit a small business site that needs email and clear account ownership?
- Why is Edit -> Zip -> Upload risky for long-term updates?
Check Your Answers
- Usually Git-connected hosting, because commits can trigger builds and deployments.
- Traditional shared hosting can be appropriate if the plan, support, renewals and ownership are clear.
- It is easy to lose track of which files changed and which version is live.
How confident are you with this concept?
Still confused | Getting there | Got it | Could explain it to a friend
Ready for the Next Deployment Step
Key Takeaways:
- Deployment is a publishing workflow, not just a button.
- The live URL is where deployment evidence is gathered.
- The right hosting path depends on files, update workflow, support needs and ownership.
- Troubleshooting starts with the first meaningful error.
Learning Objectives Review:
Look back at what you set out to learn. Can you now:
- Choose between traditional shared hosting, manual static hosting, and Git-connected deployment using realistic student and business scenarios. Check!
If you can name which part of the system you are changing, test the live result and record the outcome, deployment is becoming a repeatable workflow.
Think & Reflect:
Deployment evidence
- What would prove this site works for someone else?
Next action
- What should be recorded so this deployment can be repeated later?
Looking Ahead:
Next: continue with Traditional Shared Hosting and Control Panels.
Recommended Next Steps
Continue Learning
Ready to move forward? Continue with the next tutorial in this series:
Traditional Shared Hosting and Control PanelsRelated Topics
Explore these related tutorials to expand your knowledge: