HowTo: Reverse Proxy with Caddy
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Hi everybody,
just a quick guide to get bobarr running via reverse Proxy.
1. Setup 2 domains `bobarr.xyz.com | bobarrapi.xyz.com`
2. `git clone https://github.com/iam4x/bobarr.git`
3. `cd bobarr`
4. `nano packages/web/utils/api-url.ts`
5. change the line export `const apiURL = process.env.WEB_UI_API_URL || 'http://${host}:4000';` to `export const apiURL = 'https://bobarrapi.xyz.com';` (PLease use ` instead of ' for the URL)
6. `docker-compose build web`
7. cd to some other place e.g. /opt and run the setup script for bobarr `curl -o- https://raw.githubusercontent.com/iam4x/bobarr/master/scripts/install.sh | bash`
8. Stop bobar `./bobarr.sh stop`
9. include Caddy-Docker-Proxy in the docker-compose.yml for api and web `https://github.com/lucaslorentz/caddy-docker-proxy`
10. example for api:
```
networks:
- default
- caddy
labels:
caddy: https://bobarrapi.xyz.com
caddy.reverse_proxy: "{{upstreams 4000}}"
```
11. Add the networks: part to all other Container.
12. ./bobarr.sh start
13. Now everything should work.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking packages/web/utils/api-url.ts, docker-compose.yml, and scripts/install.sh, then verify the Caddy Docker Proxy reference and the commands in the issue against the current repository. Done means the reverse-proxy setup is documented clearly and the listed steps, labels, and networks are reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, typescript
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100