86 lines
3.1 KiB
Markdown
86 lines
3.1 KiB
Markdown
---
|
|
title: Local Web Host Set Up
|
|
summary: Transition from inmotion hosting to a local web host
|
|
type: note
|
|
client: sam
|
|
project: websites
|
|
status: active
|
|
priority: 5
|
|
last_verified: 2026-05-12
|
|
tags:
|
|
- self-hosting, networking, email, sysadmin, docker, audasmedia, inmotionhosting, email, rustfs
|
|
- self-hosting
|
|
- Networking
|
|
- email
|
|
- system-config
|
|
- Docker
|
|
- audasmedia
|
|
- inmotionhosting
|
|
- rustfs
|
|
aliases: []
|
|
id: 1778553635-RFCE
|
|
---
|
|
|
|
# Local Web Host Set Up
|
|
|
|
## 🏗 System Architecture
|
|
- **Software/Stack:** RustFS, Cpanel, Mailcow
|
|
- **Components:** {{components}}
|
|
- **Hardware/IOT:** {{hardware_specs}}
|
|
|
|
## 🎯 Objective
|
|
|
|
## 📝 Technical Implementation
|
|
- **Runtime:** {{runtime}}
|
|
- **Environment:** [e.g. Production, Staging, Edge]
|
|
|
|
## 🖇️ Context & Connections
|
|
- **Upstream:** [[Parent Component]]
|
|
- **Downstream:** [[Dependent Services]]
|
|
- **Related:** {{related_links}}
|
|
|
|
|
|
# Local Web Host Strategy
|
|
|
|
A high-performance, cost-effective blueprint for transitioning from managed hosting to a local self-hosted environment while maintaining reliability and deliverability.
|
|
|
|
## 1. Public Access & Connectivity
|
|
To bridge your local network with the public internet without a static IP:
|
|
- **Dynamic DNS (DDNS):** Use **Cloudflare** or **Namecheap** APIs to automatically update your domain's A-record to your home IP.
|
|
- **Traffic Management:** Deploy **Nginx Proxy Manager** (Docker) as a reverse proxy. This allows you to route `site1.yourdomain.com` and `site2.yourdomain.com` to different local containers/servers via ports 80/443.
|
|
|
|
## 2. The Email Problem (Deliverability)
|
|
Residential IPs are frequently blacklisted. Use a **Hybrid Relay Model**:
|
|
- **Local Server:** Run **Mailcow** or **Mail-in-a-Box** in a Docker container for internal storage and receiving.
|
|
- **Outgoing Relay:** Use **Amazon SES** (Simple Email Service) as an SMTP relay.
|
|
- **Cost:** ~$0.10 per 1,000 emails.
|
|
- **Outcome:** High reputation and low spam-flagging compared to traditional web hosts like InMotion.
|
|
- **Security:** Ensure DNS records include **SPF**, **DKIM**, and **DMARC**.
|
|
|
|
## 3. Control Panel (cPanel Alternatives)
|
|
Manage your local environment with lightweight, Docker-friendly GUIs:
|
|
- **aaPanel:** Modular and beginner-friendly.
|
|
- **HestiaCP:** Lightweight for Linux enthusiasts.
|
|
- **OpenPanel:** Specifically built for Docker-based site isolation.
|
|
|
|
## 4. Off-Site Storage & Backups
|
|
Maintain "off-site" redundancy for your local data using S3-compatible protocols:
|
|
- **Backblaze B2:** ~$6/TB/month. Great for "set and forget" backups.
|
|
- **Hetzner Storage Box:** Extremely cheap for raw storage via SFTP/Samba.
|
|
- **Tooling:** Use **Rclone** or **Duplicati** to automate local-to-cloud sync.
|
|
|
|
## 5. Potential Role for RustFS
|
|
- **Local Object Storage:** Use **RustFS** locally if you build apps requiring an S3-compatible backend for large assets (images/video) without paying cloud egress fees.
|
|
|
|
---
|
|
**Next Steps:**
|
|
1. Configure DDNS on your router or via a local cron job.
|
|
2. Set up a Docker host (Ubuntu Server/Debian).
|
|
3. Verify Amazon SES "Sandbox" exit to start sending live mail.
|
|
|
|
|
|
|
|
|
|
---
|
|
*Created: 2026-05-12*
|