- Added a comprehensive plan for history rewrites in `docs/plans/history_rewrite.md`, including backup requirements and a checklist for destructive operations. - Created a QA report for history-rewrite scripts in `docs/reports/qa_report.md`, summarizing tests, findings, and recommendations. - Introduced `check_refs.sh` script to list branches and tags, saving a tarball of tag references. - Updated `clean_history.sh` to include non-interactive mode and improved error handling for backup branch pushes. - Enhanced `preview_removals.sh` to support JSON output format and added shallow clone detection. - Added Bats tests for `clean_history.sh` and `validate_after_rewrite.sh` to ensure functionality and error handling. - Implemented pre-commit hook to block commits to `data/backups/` directory. - Improved validation script to check for backup branch existence and run pre-commit checks. - Created temporary test scripts for validating `clean_history.sh` and `validate_after_rewrite.sh` functionality.
5.4 KiB
Getting Started with Charon
Welcome! Let's get your first website up and running. No experience needed.
What Is This?
Imagine you have several apps running on your computer. Maybe a blog, a file storage app, and a chat server.
The problem: Each app is stuck on a weird address like 192.168.1.50:3000. Nobody wants to type that.
Charon's solution: You tell Charon "when someone visits myblog.com, send them to that app." Charon handles everything else—including the green lock icon (HTTPS) that makes browsers happy.
Step 1: Install Charon
Option A: Docker Compose (Easiest)
Create a file called docker-compose.yml:
services:
charon:
image: ghcr.io/wikid82/charon:latest
container_name: charon
restart: unless-stopped
ports:
- "80:80"
- "443:443"
- "8080:8080"
volumes:
- ./charon-data:/app/data
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
- CHARON_ENV=production
Then run:
docker-compose up -d
Option B: Docker Run (One Command)
docker run -d \
--name charon \
-p 80:80 \
-p 443:443 \
-p 8080:8080 \
-v ./charon-data:/app/data \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
-e CHARON_ENV=production \
ghcr.io/wikid82/charon:latest
What Just Happened?
- Port 80 and 443: Where your websites will be accessible (like mysite.com)
- Port 8080: The control panel where you manage everything
- Docker socket: Lets Charon see your other Docker containers
Open http://localhost:8080 in your browser!
Step 2: Add Your First Website
Let's say you have an app running at 192.168.1.100:3000 and you want it available at myapp.example.com.
- Click "Proxy Hosts" in the sidebar
- Click the "+ Add" button
- Fill in the form:
- Domain:
myapp.example.com - Forward To:
192.168.1.100 - Port:
3000 - Scheme:
http(orhttpsif your app already has SSL)
- Domain:
- Click "Save"
Done! When someone visits myapp.example.com, they'll see your app.
Step 3: Get HTTPS (The Green Lock)
For this to work, you need:
- A real domain name (like example.com) pointed at your server
- Ports 80 and 443 open in your firewall
If you have both, Charon will automatically:
- Request a free SSL certificate from a trusted provider
- Install it
- Renew it before it expires
You don't do anything. It just works.
By default, Charon uses "Auto" mode, which tries Let's Encrypt first and automatically falls back to ZeroSSL if needed. You can change this in System Settings if you want to use a specific certificate provider.
Testing without a domain? See Testing SSL Certificates for a practice mode.
Common Questions
"Where do I get a domain name?"
You buy one from places like:
- Namecheap
- Google Domains
- Cloudflare
Cost: Usually $10-15/year.
"How do I point my domain at my server?"
In your domain provider's control panel:
- Find "DNS Settings" or "Domain Management"
- Create an "A Record"
- Set it to your server's IP address
Wait 5-10 minutes for it to update.
"Can I change which certificate provider is used?"
Yes! Go to System Settings and look for the SSL Provider dropdown. The default "Auto" mode works best for most users, but you can choose a specific provider if needed. See Features for details.
"Can I use this for apps on different computers?"
Yes! Just use the other computer's IP address in the "Forward To" field.
If you're using Tailscale or another VPN, use the VPN IP.
"Will this work with Docker containers?"
Absolutely. Charon can even detect them automatically:
- Click "Proxy Hosts"
- Click "Docker" tab
- You'll see all your running containers
- Click one to auto-fill the form
What's Next?
Now that you have the basics:
- See All Features — Discover what else Charon can do
- Import Your Old Config — Bring your existing Caddy setup
- Configure Optional Features — Enable/disable features like security and uptime monitoring
- Turn On Security — Block attackers (enabled by default, highly recommended)
Stuck?
Ask for help — The community is friendly!
Maintainers: History-rewrite Tools
If you are a repository maintainer and need to run the history-rewrite utilities, find the scripts in scripts/history-rewrite/.
Minimum required tools:
git— install:sudo apt-get update && sudo apt-get install -y git(Debian/Ubuntu) orbrew install git(macOS).git-filter-repo— recommended install via pip:pip install --user git-filter-repoor via your package manager if available:sudo apt-get install git-filter-repo.pre-commit— install via pip or package manager:pip install --user pre-commitand thenpre-commit installin the repository.
Quick checks before running scripts:
# Fetch full history (non-shallow)
git fetch --unshallow || true
command -v git || (echo "install git" && exit 1)
command -v git-filter-repo || (echo "install git-filter-repo" && exit 1)
command -v pre-commit || (echo "install pre-commit" && exit 1)
See docs/plans/history_rewrite.md for the full checklist, usage examples, and recovery steps.