Quick Start Guide
After Installation
Once gityar is installed and running, follow these steps to get started quickly.
Step 1: Access gityar
Open your browser and navigate to:
http://localhost:3000
Or your configured domain.
Step 2: Create Admin Account
If this is a fresh installation:
- The installation wizard will appear
- Fill in admin account details:
- Complete the setup
Step 3: Configure Basic Settings
Application Settings
Go to Admin Panel → Application Settings:
- Site Name: Your gityar instance name
- Repository Root Path: Where repositories are stored
- Run User: System user running gityar
- Domain: Your domain name
- External URL: Public URL for your instance
Email Configuration (Optional)
Enable email notifications:
[mailer]
ENABLED = true
HOST = smtp.example.com:587
FROM = gityar@example.com
USER = gityar@example.com
PASSWD = password
Step 4: Create Your First Repository
- Click "+" → "New Repository"
- Fill in:
- Repository name:
my-first-project
- Description: "My first gityar repository"
- Visibility: Public or Private
- Click "Create Repository"
Step 5: Clone and Push Code
Clone Repository
git clone http://localhost:3000/username/my-first-project.git
cd my-first-project
Add Your Code
# Create files
echo "# My Project" > README.md
echo "print('Hello World')" > main.py
# Stage and commit
git add .
git commit -m "Initial commit"
# Push to gityar
git push origin main
Step 6: Explore Features
Issues
Create your first issue:
- Go to Issues tab
- Click "New Issue"
- Title: "Setup project structure"
- Description: Add details
- Submit
Wiki
Add project documentation:
- Go to Wiki tab
- Click "Create first page"
- Write your documentation in Markdown
- Save
Webhooks
Automate workflows:
- Go to Settings → Webhooks
- Click "Add Webhook"
- Configure URL and events
- Save
Step 7: Invite Collaborators
Add Collaborators
- Go to Settings → Collaboration
- Search for users
- Set permission level
- Add
Create Organization
For team projects:
- Click "+" → "New Organization"
- Fill in organization details
- Invite team members
- Create teams with different permissions
Best Practices
- ✅ Use descriptive repository names
- ✅ Always include a README file
- ✅ Add appropriate
.gitignore
- ✅ Choose a license for open-source projects
- ✅ Enable branch protection for main branches
- ✅ Use issues to track work
- ✅ Use pull requests for code review
Next Steps