1---2name: hosting-23description: Choose and manage web hosting services for websites and apps without server administration.4metadata:5 source: https://skillmd.com/skills/johnalbertini14-glitch/hosting-26 clawdbot:7 emoji: 🌍8 os:9 - linux10 - darwin11 - win3212---1314# Web Hosting Guidance1516## Choosing the Right Type17- Static sites (HTML, CSS, JS only): Use Vercel, Netlify, Cloudflare Pages, GitHub Pages — free tier often enough, no server management18- Dynamic sites with backend: Platform hosting (Railway, Render, Fly.io) handles servers without manual management19- WordPress or PHP: Managed WordPress hosts (WP Engine, Kinsta) or traditional shared hosting20- E-commerce: Shopify or platform-specific hosting — payment security is not worth DIY risk21- Don't recommend VPS to someone uncomfortable with terminal — managed hosting exists for a reason2223## Shared Hosting Reality24- "Unlimited" bandwidth and storage always have fair use limits — read the terms25- Performance depends on neighbors — bad neighbors slow your site26- SSH access may be limited or unavailable — verify before assuming27- Cron jobs and background processes often restricted28- Fine for small sites and blogs — not for growing businesses2930## Platform Hosting (Vercel, Netlify, Railway, etc.)31- Free tiers have limits — check build minutes, bandwidth, function invocations32- Serverless functions have cold start latency — first request after idle is slow33- Vendor lock-in varies — static files portable, platform-specific features less so34- Preview deployments per branch are invaluable for review workflows35- Environment variables configured in dashboard — never commit secrets to repo3637## Database Considerations38- Most platform hosts don't include databases — need separate provider (PlanetScale, Supabase, Neon)39- Database location should match app location — cross-region latency hurts performance40- Connection pooling often required for serverless — direct connections exhaust limits41- Backups may or may not be included — verify and test restore process4243## Domain and DNS44- Hosting provider often offers DNS — but separating them gives flexibility45- Point nameservers to host: simpler setup, less control46- Point A/CNAME records: more control, slightly more complex47- SSL certificates usually automatic with modern hosts — verify HTTPS works after setup4849## Email Separation50- Web hosting and email hosting are different services — can use different providers51- Don't rely on free email with web hosting — often limited and unreliable52- Google Workspace, Zoho, or dedicated email providers are more reliable53- MX records for email don't affect web hosting5455## Backups56- Managed hosts usually include backups — verify frequency and retention57- Download periodic backups locally — host backups don't help if host goes away58- Know the restore process before you need it59- Database backups separate from file backups — need both6061## Cost Awareness62- Monthly vs yearly billing — annual often 20-40% cheaper but commits you63- Traffic spikes can trigger overage fees — understand the billing model64- Free tiers often enough for side projects — don't overpay for unused capacity65- Compare total cost including add-ons — base price rarely tells the whole story6667## Migration Readiness68- Keep content in portable formats — avoid excessive platform-specific features69- Document how the current setup works — needed when moving70- Export data regularly — don't assume you can always access it71- DNS propagation takes up to 48 hours — plan migrations with overlap7273## Common Mistakes74- Choosing by price alone — support quality matters when things break75- Not testing staging before production — preview environments prevent disasters76- Ignoring geographic location — hosting in US for European users adds latency77- Assuming backups exist — verify and test before you need them78- Overcomplicating for small sites — a blog doesn't need Kubernetes