個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Split expenses with friends, see who owes whom, settle up. An open-source, self-hosted alternative to Tricount that installs on your phone as an app.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Split expenses with friends, see who owes whom, settle up. A self-hosted, open-source alternative to Tricount that installs on your phone like an app.
See every screen, on a desktop and a phone
?).The full documentation lives in docs/ and is published at
https://orochibraru.com/opencount: install and configuration, every screen,
the admin area, backups and upgrades, troubleshooting.
OpenCount is one container and one SQLite file. The image,
docker.io/orochibraru/opencount,
is built for linux/amd64 and linux/arm64.
Download the compose file into an empty directory:
mkdir opencount && cd opencount
curl -fsSLO https://raw.githubusercontent.com/orochibraru/opencount/main/compose.prod.yaml
services:
opencount:
image: docker.io/orochibraru/opencount:latest
restart: unless-stopped
ports:
- 3000:3000
volumes:
- opencount:/data
environment:
AUTH_SECRET: ${AUTH_SECRET:?set AUTH_SECRET, e.g. openssl rand -base64 32}
# The URL people open, like https://opencount.example.com.
ORIGIN: ${ORIGIN:-}
volumes:
opencount: {}
Write a .env next to it with a fresh secret and your public URL, then start
it:
cat > .env <<EOF
AUTH_SECRET=$(openssl rand -base64 32)
ORIGIN=https://opencount.example.com
EOF
docker compose -f compose.prod.yaml up -d
Keep AUTH_SECRET with your backups: it signs sessions and encrypts the secrets
stored in the database. Changing it signs everyone out and loses them.
| Variable | Default | What it does |
|---|---|---|
AUTH_SECRET | none, required | Signs sessions and encrypts stored secrets; 32 characters or more |
ORIGIN | from the proxy headers | The public URL; required on plain HTTP with no proxy |
DATABASE_PATH | /data/opencount.sqlite | The SQLite file, on the /data volume |
PORT | 3000 | The HTTP port |
LOG_LEVEL | info | trace, debug, info, warn or error |
LOG_FORMAT | console | json or console |
Put it behind an HTTPS reverse proxy that sets X-Forwarded-Proto and
X-Forwarded-Host: passkeys and installing the app both need HTTPS. On plain
HTTP with no proxy, ORIGIN must be the exact URL you open (like
http://192.168.1.10:3000), or every form is refused as cross-site.
Every other variable, from the background worker to traces and error reporting, is in Configuration. Sign-ups, sign-in methods, email and receipt reading are set in the app's admin area.
A fresh instance has no account, and every page sends you to the setup screen. It asks for a code only the server's log shows, so nobody who stumbles on the URL can claim the instance:
docker compose -f compose.prod.yaml logs opencount
Look for the line starting with Setup code: six digits, valid 15 minutes.
Enter it, then your email, name and password. That first account is the admin.
From the admin area, set up email, secure your account with an authenticator app
or a passkey, and invite people.
On a phone, use Add to Home Screen to install it.
Step by step, with what each screen does: First run.
docker compose -f compose.prod.yaml pull
docker compose -f compose.prod.yaml up -d
Migrations run at boot. Your data is the opencount volume: back it up, with
AUTH_SECRET, or download a backup from the admin area's Backup tab. See
Backups and upgrades.
See CONTRIBUTING.md.