This commit implements a comprehensive reorganization of project documentation and adds explicit Gitea platform context throughout the project. ## Documentation Reorganization ### File Moves (Content Preserved) - Moved CURSOR_WINDOWS_SETUP.md to kb/_guides/ for better organization - Moved docs/PHASE-UPDATES/ to kb/_guides/PROJECT-SETUP-GUIDE/: - COMPLETE-SYSTEM-REPLICATION-GUIDE.md - PHASE-0-GITEA-UPDATES.md - README.md - Added new file: kb/_guides/PROJECT-SETUP-GUIDE/PHASE-1-PLAN.md **Reason**: Consolidate project setup and configuration guides into the knowledge base structure for better discoverability and organization. ### New Phase Documentation Structure Created tendril/phases/ directory with structured phase documentation: - phase-00-foundation/: blueprint, changelog, decisions, tasks - phase-01-testing-validation/: blueprint, changelog, decisions, tasks **Reason**: Establish consistent phase documentation structure following project guidelines for phase management and tracking. ## Gitea Platform Context Integration ### .cursorrules Updates - Added comprehensive Gitea platform context section - Added Gitea documentation references for workflows and platform questions - Added platform terminology guidelines (Gitea vs GitHub) - Added references to docs/GITEA/ documentation throughout rules **Reason**: Ensure all AI agents and contributors use correct Gitea terminology and have clear guidance on where to find Gitea-specific documentation. ### Documentation Path Updates - CONTRIBUTING.md: Updated CURSOR_WINDOWS_SETUP.md path reference - docs/AGENT-GUIDELINES.md: Updated path references to moved documentation - PROJECT_STATUS.md: Updated comment to mention Gitea Actions **Reason**: Maintain link integrity after file reorganization and ensure documentation references point to correct locations. ## Impact and Benefits 1. **Better Organization**: Documentation is now organized in logical structures (kb/ for knowledge base, tendril/phases/ for phase docs) 2. **Clear Platform Context**: Explicit Gitea platform references prevent confusion with GitHub terminology and provide clear documentation paths 3. **Consistent Structure**: Phase documentation follows standardized format (blueprint, changelog, decisions, tasks) for easier maintenance 4. **Improved Discoverability**: Guides consolidated in kb/_guides/ make it easier to find setup and configuration information All file moves preserve content - no information was lost in this reorganization.
6.0 KiB
Gitea Development Environment Setup Guide for Windows & Cursor
Objective: This document details the complete process for configuring a local development environment on a Windows PC to work with a Gitea-hosted source code repository. It covers connecting the Cursor IDE using the Model Context Protocol (MCP) and cloning a project repository to begin work.
Core Components
-
Gitea: The remote Git server where the project's code is stored.
-
Gitea MCP Server: A command-line application that acts as a bridge between Cursor and Gitea.
-
Cursor IDE: The code editor used for development.
-
Git for Windows: The underlying version control software used for all
gitcommands.
Phase 1: Environment Setup and Configuration
Step 1: Download and Prepare the Gitea MCP Server
The first step is to get the bridge application that allows Cursor to communicate with Gitea.
-
Download the Binary:
-
Navigate to the official Gitea MCP releases page: https://gitea.com/gitea/gitea-mcp/releases
-
From the latest release, download the zip archive for Windows, named
gitea-mcp_Windows_x86_64.zip.
-
-
Create a Permanent Location:
- Create a dedicated folder on your computer where this tool will live permanently. For this guide, we used:
D:\OneDrive\GIT_Parkingmeter\gitea-mcp_Windows_x86_64
- Create a dedicated folder on your computer where this tool will live permanently. For this guide, we used:
-
Extract the Files:
- Extract the contents of the downloaded
.zipfile into the folder you just created. The most important file isgitea-mcp.exe.
- Extract the contents of the downloaded
Step 2: Generate a Gitea Access Token
Cursor needs a secure "password" to access your Gitea account. This is called an Access Token.
-
Navigate to Gitea Settings: Go to your Gitea instance's Applications page: https://git.parkingmeter.info/user/settings/applications
-
Generate a New Token:
-
Give the token a descriptive name (e.g., "Cursor on Windows PC").
-
Set the following permissions to Read and Write:
-
issue -
repository -
user
-
-
Click "Generate Token".
-
-
Copy and Save the Token:
- CRITICAL: Gitea will display the token only once. Copy it immediately and save it in a secure place (like a password manager or a temporary text file). You will need it in the next steps.
Step 3: Create the Server Startup Script (run-gitea.bat)
To ensure the Gitea MCP Server starts reliably every time, we will create a simple startup script.
-
Create the File:
- In the same folder where you extracted
gitea-mcp.exe, create a new file namedrun-gitea.bat.
- In the same folder where you extracted
-
Edit the Script:
- Open
run-gitea.batwith a text editor (like Notepad) and paste the following content:
@echo off echo Starting Gitea MCP server in HTTP mode... echo Do not close this window! D:\OneDrive\GIT_Parkingmeter\gitea-mcp_Windows_x86_64\gitea-mcp.exe -t http --host https://git.parkingmeter.info --token YOUR_GITEA_TOKEN_HERE - Open
-
Add Your Token:
-
In the script, replace
YOUR_GITEA_TOKEN_HEREwith the actual Gitea token you copied in Step 2. -
Save and close the file.
-
Step 4: Configure Cursor's MCP Tools
This is the most important step. We need to tell Cursor how to find and use your new Gitea server.
-
Open Cursor's MCP Settings:
-
In Cursor, navigate to the settings UI.
-
Go to the "Tools & MCP" section.
-
You will see a file named
mcp.json. Open this file.
-
-
Add the Gitea Server Configuration:
- Inside the
"mcpServers": { ... }object, add the following configuration block. Be sure to add a comma,after the preceding entry.
"gitea-local": { "url": "http://localhost:8080/mcp", "headers": { "Authorization": "Bearer YOUR_GITEA_TOKEN_HERE" } } - Inside the
-
Add Your Token:
-
Again, replace
YOUR_GITEA_TOKEN_HEREwith your actual Gitea token. -
IMPORTANT: The word
Bearerfollowed by a space must be kept in front of the token.
-
-
Save the
mcp.jsonfile.
Step 5: Test the Connection Workflow
This is the process you will follow each time you want to use the Gitea integration.
-
Manually Start the Server:
-
Using File Explorer, navigate to your
gitea-mcp_Windows_x86_64folder. -
Double-click the
run-gitea.batscript. -
A black command prompt window will appear and stay open. This is your server. You must keep this window running while you use the integration in Cursor.
-
-
Restart and Test in Cursor:
-
Completely close and reopen the Cursor application to ensure it loads the new configuration.
-
Open the AI Chat panel (
Ctrl + L). -
Send the command:
@gitea-local list my repositories. -
The AI may initially be confused. Confirm that it should make a direct API call to your Gitea instance, providing the URL (
https://git.parkingmeter.info) when prompted. -
Success is confirmed when the AI returns a formatted list of your Gitea repositories.
-
Step 6: Clone the Project Repository
The final setup step is to download the project's source code to your machine.
-
Open a Terminal in Cursor:
- Go to the top menu and select Terminal -> New Terminal.
-
Navigate to Your Projects Directory:
-
In the terminal, change to the folder where you want to store your projects. We used:
cd /d/OneDrive/GIT_Parkingmeter
-
-
Clone the Repository:
-
Run the
git clonecommand with the project's URL:git clone https://git.parkingmeter.info/Mycelium/tendril.git
-
Phase One Complete
At this point, your environment is fully configured. You have successfully linked Cursor to your Gitea account and downloaded a local copy of the project code. You are now ready to move on to Phase Two: The Development Workflow (editing, pushing, and pulling code).