Advanced25-30 minDeploymentLesson 4

Deployment module

Traditional Shared Hosting and Control Panels

Understand shared hosting accounts, public web roots, control panels, account ownership, support boundaries, backups, and provider comparisons.

Learning Objectives

By the end of this lesson, you'll be able to:

  • Explain what shared hosting is
  • Identify common control panel tools
  • Recognise public web root folder names
  • Compare provider guidance without relying on fragile pricing claims
  • Record account ownership and support responsibilities

Why This Matters:

Traditional hosting is still common for small websites, so students should understand the account, not only the upload button.

Before You Start:

You should be familiar with:

What Shared Hosting Includes

Shared hosting means many customer sites live on managed hosting infrastructure. A hosting account may include storage, bandwidth, domains, email, databases, backups, SSL, logs and support. The host manages the server environment; you still manage your files, renewals, credentials, content and backups.

For client or business sites, account ownership matters. The business should know who owns the account, who pays renewal invoices, where support is requested and where backups live.

Shared hosting is common because it bundles many practical website needs into one account. That convenience is also why students need to read carefully. Storage, bandwidth, email accounts, databases, backup frequency, support hours and renewal prices can vary across plans from the same provider. A cheap first year is not the same thing as a cheap website over three years.

  • Account ownership: the client or organisation should own the account where possible.
  • Billing responsibility: someone must receive and pay renewal notices.
  • Backup responsibility: provider backups are useful, but students should still keep project copies.
  • Support boundaries: hosts may help with server/account issues, but not custom code bugs.

Control Panels You May See

cPanel, DirectAdmin, Plesk and proprietary dashboards look different, but often provide equivalent functions.

ToolPurpose
File ManagerUpload, move, rename, extract and delete files on the host.
Domains and subdomainsConnect names such as example.com or shop.example.com to sites.
SSL certificatesEnable HTTPS so browsers can use a secure connection.
Email accountsCreate mailbox accounts when the hosting plan includes email.
DatabasesManage database-backed sites such as some CMS or PHP apps.
PHP versionsSelect runtime versions for PHP-based websites.
BackupsCreate or restore copies, depending on what the host provides.
DNS toolsEdit records when DNS is managed by the hosting provider.
Error logsInspect server-side errors when a page fails.

The Public Web Root

public_html/
├── index.html
├── css/
│   └── styles.css
├── js/
│   └── script.js
└── images/
    └── logo.svg

The public folder may be named public_html, htdocs, www, httpdocs or something provider-specific. Confirm the correct folder in your host's documentation.

Provider Guidance for Students

This section is educational, not promotional. Hosting prices, free plans, renewal rates and feature limits change frequently. Check each provider's current official website before signing up, distinguish introductory pricing from renewal pricing, and check currency, GST and cancellation terms where relevant.

Provider details below were checked against current official provider pages on 14 July 2026. They are deliberately written as comparison guidance rather than promises. Before students buy hosting, they should open the provider's current plan page and record the first-term price, renewal price, currency, GST/tax treatment, storage, email, databases, SSL, backups, support and cancellation policy.

ProviderPositioningCompare carefullyChecked
VentraIPPrimary Australian shared-hosting example for students who want local account management and support context.Official pages currently describe Australian ownership, Australian support context, cPanel-based hosting options and promotional monthly prices. Compare entry price, renewal price, storage, backups, email, SSL, support, data location and cancellation policy. Do not assume it is always cheapest.14 July 2026
HostingerBudget-focused international option.Official pages currently show discounted long-term introductory pricing, renewal prices, storage, free SSL, backups and email inclusions that vary by plan. Check the subscription length and renewal rate before treating it as low-cost.14 July 2026
Namecheap shared hostingUseful for students already managing domains there.Official pages currently position shared hosting around cPanel, email accounts, SSD storage, backups and discounted first-term pricing. Check whether keeping domain and hosting together helps or reduces flexibility.14 July 2026
DreamHostBeginner-friendly international shared-hosting option.Official hosting pages currently present shared and managed options for small sites. Compare support, renewal cost, included email, backup model, control panel differences and data-location expectations.14 July 2026
SiteGroundOften positioned around stronger support and managed features.Official Australian pages currently show discounted introductory pricing, renewal pricing excluding GST, SSL, CDN, daily backups and email. Students should compare total cost and whether the extra managed support is needed.14 July 2026
Crazy DomainsA provider Australian students may encounter.Official Australian pages currently list shared Linux hosting tiers with websites, NVMe storage, email accounts, MySQL databases, free SSL and Cloudflare CDN. Compare renewal pricing, account ownership, support boundaries and cancellation policies carefully.14 July 2026

Free Traditional Hosting

Free shared hosting can be useful for experimentation, but it should not be recommended for real client or business sites. If you mention providers such as InfinityFree, AwardSpace or FreeHosting.com, verify their current terms first.

  • reduced storage or bandwidth
  • limited databases or no email
  • restricted support
  • provider subdomains
  • advertising, branding or disabled features
  • account inactivity rules
  • uncertain long-term availability
  • restrictions on commercial use

Free shared hosting is most useful when the learning goal is to see a control panel, upload files and understand limitations. It is not a sensible default for a real client or business website because support, continuity, backups and commercial-use terms matter.

Preferred Free Modern Hosting for Static Projects

GitHub Pages, Netlify, Vercel and Cloudflare Pages are not traditional shared hosting services. They are generally better suited to static sites and frontend projects than free shared hosting, especially when a project is already in Git.

Shared Hosting Knowledge Check

Before moving forward, can you answer these?

  1. What is the public web root?
  2. Why should students compare renewal pricing separately from entry pricing?
  3. Why is free shared hosting unsuitable for a real business site?
Check Your Answers
  1. The folder the host serves to the web, such as public_html, htdocs, www or httpdocs.
  2. Introductory prices are often temporary; the renewal price is what the site may cost after the first term.
  3. It may have limited support, uncertain continuity, restrictions, branding, reduced resources or unclear commercial terms.

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:

  • Understand shared hosting accounts, public web roots, control panels, account ownership, support boundaries, backups, and provider comparisons. 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 Uploading a Plain HTML, CSS and JavaScript Website.

Recommended Next Steps

Continue Learning

Ready to move forward? Continue with the next tutorial in this series:

Uploading a Plain HTML, CSS and JavaScript Website

Related Topics

Explore these related tutorials to expand your knowledge:

Progress tracking is disabled. Enable it in to track your completed tutorials.