docs: Add Gitea authentication configuration to Windows development guide
- Add step-by-step Git configuration for Gitea - Include both token and username URL methods - Add troubleshooting section for common Git issues - Provide credential helper configuration examples
This commit is contained in:
parent
c7132ae7d5
commit
b53386c882
|
@ -14,6 +14,37 @@ Previously, Windows users couldn't clone the repository due to files with charac
|
|||
|
||||
## Windows Development Setup
|
||||
|
||||
### Step 1: Configure Git for Gitea
|
||||
|
||||
#### Option A: Using Personal Access Token (Most Secure)
|
||||
1. Go to your Gitea instance: `https://gitea.casaparma.dscloud.me`
|
||||
2. Navigate to Settings → Applications → Generate New Token
|
||||
3. Copy the generated token
|
||||
4. Configure Git credentials:
|
||||
|
||||
```bash
|
||||
git config --global credential.helper store
|
||||
git config --global user.name "Your-Gitea-Username"
|
||||
git config --global user.email "your-email@domain.com"
|
||||
```
|
||||
|
||||
5. Clone the repository:
|
||||
```bash
|
||||
git clone https://gitea.casaparma.dscloud.me/Miguel/SIDEL_ScriptsManager.git
|
||||
```
|
||||
|
||||
6. When prompted, use your username and the **token** as password.
|
||||
|
||||
#### Option B: Using Username in URL (Quick Setup)
|
||||
```bash
|
||||
git clone https://YOUR-USERNAME@gitea.casaparma.dscloud.me/Miguel/SIDEL_ScriptsManager.git
|
||||
cd SIDEL_ScriptsManager
|
||||
```
|
||||
|
||||
This will prompt for password only once and store it securely.
|
||||
|
||||
### Step 2: Development Environment Setup
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- **Git for Windows** with WSL support (recommended)
|
||||
|
@ -259,7 +290,56 @@ When developing new script groups on Windows:
|
|||
|
||||
### Database
|
||||
|
||||
The PostgreSQL database runs in Docker and is consistent across platforms. No special Windows considerations needed.
|
||||
The PostgreSQL database runs in Docker and data persists in `data/postgres/`.
|
||||
|
||||
## Git Configuration Troubleshooting
|
||||
|
||||
### Credential Issues
|
||||
|
||||
If you're repeatedly asked for credentials:
|
||||
|
||||
```bash
|
||||
# Check current configuration
|
||||
git config --list | grep credential
|
||||
|
||||
# Reset credential helper
|
||||
git config --global --unset credential.helper
|
||||
git config --global credential.helper store
|
||||
|
||||
# For Gitea specifically, use username in URL
|
||||
git remote set-url origin https://USERNAME@gitea.casaparma.dscloud.me/Miguel/SIDEL_ScriptsManager.git
|
||||
```
|
||||
|
||||
### Token Authentication
|
||||
|
||||
When using Personal Access Tokens:
|
||||
- Username: Your Gitea username
|
||||
- Password: The generated token (NOT your regular password)
|
||||
|
||||
### Windows-Specific Git Issues
|
||||
|
||||
```bash
|
||||
# If you get line ending warnings
|
||||
git config --global core.autocrlf true
|
||||
|
||||
# If you get filename issues
|
||||
git config --global core.protectNTFS false
|
||||
```
|
||||
|
||||
### Verify Your Configuration
|
||||
|
||||
```bash
|
||||
# Test your setup
|
||||
git fetch origin
|
||||
git status
|
||||
|
||||
# Check remotes
|
||||
git remote -v
|
||||
|
||||
# Check user configuration
|
||||
git config user.name
|
||||
git config user.email
|
||||
```
|
||||
|
||||
### Proxy System
|
||||
|
||||
|
|
Loading…
Reference in New Issue