Gitead/DentalManagement09
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add one-time git credential setup to Quick Install

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Gitead
2026-10-02 23:46:44 -04:00
co-authored by Claude Opus 5.5
parent d67aa75c42
commit 036e26c5d8
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+16
View File
@@ -70,6 +70,22 @@ bash install-all.sh
Enter your password when it asks. The script installs Node.js, Python, Chrome, PostgreSQL, Redis, rclone and nginx; installs the Node and Python dependencies; creates any missing `.env` files (existing ones are kept); sets up the database; and creates the desktop shortcuts. It is safe to re-run. Enter your password when it asks. The script installs Node.js, Python, Chrome, PostgreSQL, Redis, rclone and nginx; installs the Node and Python dependencies; creates any missing `.env` files (existing ones are kept); sets up the database; and creates the desktop shortcuts. It is safe to re-run.
### D — Let git remember your Gitea login (one time)
So `git push` doesn't ask for the password every time:
```sh
git config --global credential.helper store
cd ~/Desktop/DentalManagement09
git push origin main
```
Enter the Gitea username and password once when asked — git saves them and won't prompt again.
> Prefer a Gitea **access token** over your real password: log into https://gitea.mydentalofficemanagement.com → profile picture → **Settings** → **Applications** → **Generate New Token** (give it **Read and Write** access to **repository**), and paste the token when git asks for the password. A token can be revoked in Gitea at any time without changing your password.
> `store` saves the login in plain text in `~/.git-credentials`. The keyring-based helper isn't an option here because Step 1a removes gnome-keyring.
Still done by hand afterwards: the Security Setup above, Step 1 (auto-login / keyring), Step 12a (Cloudflare subdomain), the LAN HTTPS certificate (the script only enables the nginx site once that certificate exists), and the optional Steps 17–18. Still done by hand afterwards: the Security Setup above, Step 1 (auto-login / keyring), Step 12a (Cloudflare subdomain), the LAN HTTPS certificate (the script only enables the nginx site once that certificate exists), and the optional Steps 17–18.
--- ---