|
9 | 9 | </p> |
10 | 10 |
|
11 | 11 | <p align="center"> |
12 | | - <a href="#perfect-for">Perfect For</a> • |
13 | | - <a href="#features">Features</a> • |
14 | | - <a href="#why-devdocs">Why DevDocs</a> • |
15 | | - <a href="#getting-started">Getting Started</a> • |
16 | | - <a href="#pricing-comparison">Compare to FireCrawl</a> • |
17 | | - <a href="#join-our-community">Discord</a> |
| 12 | + <a href="#-perfect-for">Perfect For</a> • |
| 13 | + <a href="#-features">Features</a> • |
| 14 | + <a href="#-why-devdocs">Why DevDocs</a> • |
| 15 | + <a href="#-getting-started">Getting Started</a> • |
| 16 | + <a href="#-scripts-and-their-purpose">Scripts</a> • |
| 17 | + <a href="#-pricing-comparison">Compare to FireCrawl</a> • |
| 18 | + <a href="#-join-our-community">Discord</a> |
18 | 19 | </p> |
19 | 20 | </div> |
20 | 21 |
|
@@ -90,72 +91,125 @@ DevDocs brings documentation to you. Point it at any tech documentation URL, and |
90 | 91 |
|
91 | 92 | ## 🚀 Getting Started |
92 | 93 |
|
93 | | -We made using DevDocs extremely easy, no complex documentation to learn DevDocs. (UI is very intuitive and self learning) |
| 94 | +DevDocs is designed to be easy to use with Docker, requiring minimal setup for new users. |
94 | 95 |
|
95 | | -<ins>Mac & Linux(WSL) Users</ins> |
| 96 | +### Prerequisites |
96 | 97 |
|
| 98 | +- [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/install/) installed on your system |
| 99 | +- Git for cloning the repository |
| 100 | + |
| 101 | +### Quick Start with Docker (Recommended) |
| 102 | + |
| 103 | +For Mac/Linux users: |
97 | 104 | ```bash |
98 | 105 | # Clone the repository |
99 | 106 | git clone https://github.com/cyberagiinc/DevDocs.git |
100 | 107 |
|
101 | | -# Install all good stuff |
| 108 | +# Navigate to the project directory |
102 | 109 | cd DevDocs |
103 | | -./fast-markdown-mcp/setup.sh |
104 | | - |
105 | | -# Run Devdocs, (next time just run ./start.sh as all requirements are already installed) |
106 | | -./start.sh |
107 | 110 |
|
108 | | -#logs are located under /logs for |
109 | | -backend.log |
110 | | -frontend.log |
111 | | -mcp.log |
| 111 | +# Start all services using Docker |
| 112 | +./docker-start.sh |
112 | 113 | ``` |
113 | 114 |
|
114 | | -Visit `http://localhost:3001` and start scraping and discovering documents! |
| 115 | +For Windows users: |
| 116 | +```cmd |
| 117 | +# Clone the repository |
| 118 | +git clone https://github.com/cyberagiinc/DevDocs.git |
115 | 119 |
|
116 | | -<ins>Windows Users</ins> |
| 120 | +# Navigate to the project directory |
| 121 | +cd DevDocs |
117 | 122 |
|
118 | | -#### Option 1: Using Batch Scripts (Command Prompt) |
| 123 | +# Start all services using Docker |
| 124 | +docker-start.bat |
| 125 | +``` |
119 | 126 |
|
120 | | -1. Run the setup script: |
121 | | - ``` |
122 | | - fast-markdown-mcp\setup.bat |
| 127 | +> **Note for Windows Users**: If you encounter permission issues, you may need to run the script as administrator or manually set permissions on the logs, storage, and crawl_results directories. The script uses the `icacls` command to set permissions, which might require elevated privileges on some Windows systems. |
| 128 | +> |
| 129 | +> **Manually Setting Permissions on Windows**: |
| 130 | +> |
| 131 | +> If you need to manually set permissions, you can do so using either the Windows GUI or command line: |
| 132 | +> |
| 133 | +> **Using Windows Explorer**: |
| 134 | +> 1. Right-click on each directory (logs, storage, crawl_results) |
| 135 | +> 2. Select "Properties" |
| 136 | +> 3. Go to the "Security" tab |
| 137 | +> 4. Click "Edit" to change permissions |
| 138 | +> 5. Click "Add" to add users/groups |
| 139 | +> 6. Type "Everyone" and click "Check Names" |
| 140 | +> 7. Click "OK" |
| 141 | +> 8. Select "Everyone" in the list |
| 142 | +> 9. Check "Full control" under "Allow" |
| 143 | +> 10. Click "Apply" and "OK" |
| 144 | +> |
| 145 | +> **Using Command Prompt (as Administrator)**: |
| 146 | +> ```cmd |
| 147 | +> icacls logs /grant Everyone:F /T |
| 148 | +> icacls storage /grant Everyone:F /T |
| 149 | +> icacls crawl_results /grant Everyone:F /T |
| 150 | +> ``` |
| 151 | +
|
| 152 | +This single command will: |
| 153 | +1. Create all necessary directories |
| 154 | +2. Set appropriate permissions |
| 155 | +3. Build and start all Docker containers |
| 156 | +4. Monitor the services to ensure they're running properly |
| 157 | +
|
| 158 | +### Accessing DevDocs |
| 159 | +
|
| 160 | +Once the services are running: |
| 161 | +- Frontend UI: http://localhost:3001 |
| 162 | +- Backend API: http://localhost:24125 |
| 163 | +- Crawl4AI Service: http://localhost:11235 |
| 164 | +
|
| 165 | +### Logs and Monitoring |
| 166 | +
|
| 167 | +When using Docker, logs can be accessed : |
| 168 | +
|
| 169 | +1. **Container Logs** (recommended for debugging): |
| 170 | + ```bash |
| 171 | + # View logs from a specific container |
| 172 | + docker logs devdocs-frontend |
| 173 | + docker logs devdocs-backend |
| 174 | + docker logs devdocs-mcp |
| 175 | + docker logs devdocs-crawl4ai |
| 176 | + |
| 177 | + # Follow logs in real-time |
| 178 | + docker logs -f devdocs-backend |
123 | 179 | ``` |
124 | 180 |
|
125 | | -2. Start all services: |
126 | | - ``` |
127 | | - start.bat |
128 | | - ``` |
| 181 | +To stop all services, press `Ctrl+C` in the terminal where docker-start is running. |
129 | 182 |
|
130 | | -#### Option 2: Using PowerShell Script |
| 183 | +## 📜 Scripts and Their Purpose |
131 | 184 |
|
132 | | -1. First, run the setup batch script: |
133 | | - ``` |
134 | | - fast-markdown-mcp\setup.bat |
135 | | - ``` |
| 185 | +DevDocs includes various utility scripts to help with development, testing, and maintenance. Here's a quick reference: |
136 | 186 |
|
137 | | -2. Then start all services using PowerShell: |
138 | | - ```powershell |
139 | | - .\start.ps1 |
140 | | - ``` |
| 187 | +### Startup Scripts |
| 188 | +- `start.sh` / `start.bat` / `start.ps1` - Start all services (frontend, backend, MCP) for local development. |
| 189 | +- `docker-start.sh` / `docker-start.bat` - Start all services using Docker containers. |
141 | 190 |
|
142 | | - Note: If you encounter execution policy restrictions, you may need to run: |
143 | | - ```powershell |
144 | | - Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process |
145 | | - ``` |
| 191 | +### MCP Server Scripts |
| 192 | +- `check_mcp_health.sh` - Verify the MCP server's health and configuration status. |
| 193 | +- `restart_and_test_mcp.sh` - Restart Docker containers with updated MCP configuration and test connectivity. |
146 | 194 |
|
147 | | -#### Option 3: Using Windows Subsystem for Linux (WSL) |
| 195 | +### Crawl4AI Scripts |
| 196 | +- `check_crawl4ai.sh` - Check the status and health of the Crawl4AI service. |
| 197 | +- `debug_crawl4ai.sh` - Run Crawl4AI in debug mode with verbose logging for troubleshooting. |
| 198 | +- `test_crawl4ai.py` - Run tests against the Crawl4AI service to verify functionality. |
| 199 | +- `test_from_container.sh` - Test the Crawl4AI service from within a Docker container. |
148 | 200 |
|
149 | | -If you prefer a Linux-like environment on Windows: |
| 201 | +### Utility Scripts |
| 202 | +- `view_result.sh` - Display crawl results in a formatted view. |
| 203 | +- `find_empty_folders.sh` - Identify empty directories in the project structure. |
| 204 | +- `analyze_empty_folders.sh` - Analyze empty folders and categorize them by risk level. |
| 205 | +- `verify_reorganization.sh` - Verify that code reorganization was successful. |
150 | 206 |
|
151 | | -1. Install WSL by following the [official instructions](https://docs.microsoft.com/en-us/windows/wsl/install) |
152 | | -2. Open a WSL terminal |
153 | | -3. Navigate to your project directory |
154 | | -4. Run the original Linux scripts: |
155 | | - ```bash |
156 | | - ./fast-markdown-mcp/setup.sh |
157 | | - ./start.sh |
158 | | - ``` |
| 207 | +These scripts are organized in the following directories: |
| 208 | +- Root directory: Main scripts for common operations |
| 209 | +- `scripts/general/`: General utility scripts |
| 210 | +- `scripts/docker/`: Docker-specific scripts |
| 211 | +- `scripts/mcp/`: MCP server management scripts |
| 212 | +- `scripts/test/`: Testing and verification scripts |
159 | 213 |
|
160 | 214 | ## 🌍 Built for Developers, by Developers |
161 | 215 |
|
@@ -226,7 +280,7 @@ Final Output Construction: The final answer should be organized, directly addres |
226 | 280 |
|
227 | 281 | ## 📝 Technology Partners |
228 | 282 |
|
229 | | -<img src="image-6.png" width="200" height="100"> <img src="image-7.png" width="250" height="100"> <img src="image-8.png" width="300" height="100"> |
| 283 | +<img src="assets/image-6.png" width="200" height="100"> <img src="assets/image-7.png" width="250" height="100"> <img src="assets/image-8.png" width="300" height="100"> |
230 | 284 |
|
231 | 285 | ## Star History |
232 | 286 |
|
|
0 commit comments