Self-host Proxyscotch with Levelrail
A small CORS proxy that lets Hoppscotch call APIs from the browser.
- Authorhoppscotch
- LicenceMIT
- Memory64 MiB
- Archarm64
- Services1
How to self-host Proxyscotch
-
Pull the images
One image is pulled on your server.
Show images
hoppscotch/proxyscotch:v0.1.4
-
Create the app
One service starts in a single Compose app, on port 9159.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Proxyscotch requirements
- Memory
- About 64 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 9159
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 9159 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Proxyscotch. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Proxyscotch docs page.
Deploy Proxyscotch your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Proxyscotch from the CLI
levelrail-cli templates deploy proxyscotch --name my-proxyscotch Deploy Proxyscotch with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/proxyscotch/deploy Proxyscotch configuration
Proxyscotch services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| proxyscotch | hoppscotch/proxyscotch:v0.1.4 | 9159 | none |
Proxyscotch environment variables
| Variable | Service | Value |
|---|---|---|
| PROXYSCOTCH_ALLOWED_ORIGINS | proxyscotch | Preset by the template |
| PROXYSCOTCH_TOKEN | proxyscotch | Generated at deploy |
Ports and volumes
- Ports
- 9159
- Volumes
- none
Proxyscotch FAQ
How much memory does Proxyscotch need?
The catalog lists about 64 MiB of memory for Proxyscotch.
Does Proxyscotch run on arm64?
For Proxyscotch, an arm64 image is published; amd64 is image published.
What licence is Proxyscotch under?
Proxyscotch is licensed under MIT, which is permissive, with few conditions on reuse.
Does Proxyscotch need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Proxyscotch use?
Proxyscotch listens on port 9159 inside the stack.
Can I deploy Proxyscotch on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Proxyscotch, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image hoppscotch/proxyscotch:v0.1.4 is what you deploy there.