Repository navigation
Security
MrJSA edited this page Oct 27, 2026
·
1 revision
- Keep
.envprivate (chmod 600 .env); it contains the database password and is never part of the repository. - The updater service can control Docker on the host (that is how it rebuilds the shop). It has no published port, is only reachable by the backend over a private network and requires a token generated on first start. Remove the
updaterservice fromdocker-compose.ymlif you prefer updating manually. - Files the updater changes in the checkout are owned by
root; usesudofor manual git commands in/opt/rustwebshopafterwards. - Do not open ports 8080, 4000 or 8081 in the firewall (see Installation, step 7).
- Restrict the admin domain further (VPN, IP allow-list or HTTP basic auth) if only a few people need it.
- Backups contain customer data, password hashes and your payment/email keys: keep the backup repository private and turn on two-factor authentication for your GitHub account (see Backups).
Getting started
Running the shop
- Admin Overview
- Updates
- Release Channels
- Domains
- Restoring a Backup
- Own Reverse Proxy
- Troubleshooting
- Security
Help & feedback