projects list
List all projects in the database.Syntax
Output
Information Shown
- Project name: Identifier used in all commands
- Spider count: Number of spiders in this project
- Queue items: Number of items in queue for this project
Empty Database
Project Organization
Projects are implicit - they don’t need to be created explicitly. When you import a spider or add a queue item with--project <name>, the project is automatically associated.
--project is not specified, commands use default.
Project Naming
Project names should be:- Descriptive:
news,ecommerce,research - Lowercase:
newsnotNews - No spaces:
tech_blogsnottech blogs - Consistent: Choose a naming scheme and stick to it
Use Cases
Multi-Domain Projects
Group related spiders:Team Organization
Separate projects by team or purpose:Development vs Production
Separate test and production spiders:Project-Level Operations
List Spiders by Project
Run All Spiders in Project
Queue Management by Project
Export Project Data
Data Organization
Files are organized by project:Database Schema
Projects are stored as string fields:spiders Table
crawl_queue Table
Project Uniqueness
- Spiders: Unique by
(name, project)- same spider name can exist in different projects - Queue: Unique by
(project_name, website_url)- same URL can be in different projects
Renaming Projects
Projects can be renamed via direct database updates:Deleting Projects
Delete all spiders in a project:Parallel Processing by Project
Run multiple projects in parallel:Project Statistics
Get detailed stats per project:Best Practices
- Use descriptive names:
tech_news_monitoringnotproj1 - Separate dev and prod: Use
dev_andprod_prefixes - Document project purpose: Maintain a
projects.mdfile describing each project - Consistent naming: Choose a convention (simple names, prefixed names, or dated names) and stick to it
Migrating Between Projects
Next Steps
Spider Management
Import spiders into projects
Queue Management
Add URLs to project queues