Prerequisites
Before you begin, ensure you have the following installed:.NET 9.0 SDK
Download from dotnet.microsoft.com
Node.js 18+
Download from nodejs.org
PostgreSQL 14+
Download from postgresql.org
Git
Download from git-scm.com
Setup Steps
Configure the database
Create a PostgreSQL database for the project:Navigate to the backend API project and create an Create
appsettings.json file:appsettings.json with your database connection:appsettings.json
Start the backend API
Restore dependencies and run the .NET API:The API will start on
http://localhost:5000. You should see:Visit
http://localhost:5000/swagger to explore the API documentationWhat’s Next?
Now that you have Huellitas running locally, you can:Explore the Architecture
Learn about the three-tier architecture and design patterns
Backend Setup
Deep dive into the .NET API configuration
Frontend Development
Understand the React SPA structure
API Reference
Explore all available endpoints
Test the Application
Browse Products
- Open
http://localhost:5173in your browser - Browse the product catalog
- Click on a product to view details
Add Items to Cart
- Click “Agregar al carrito” on any product
- Navigate to the cart page using the cart icon
- Adjust quantities or remove items
Admin Access
- Navigate to
http://localhost:5173/#/login - Log in with admin credentials
- Access the dashboard at
http://localhost:5173/#/admin
Troubleshooting
Database connection errors
Database connection errors
Verify your PostgreSQL service is running:Check your connection string in
appsettings.json matches your PostgreSQL configuration.Port already in use
Port already in use
If port 5000 or 5173 is already in use, you can change it:Backend (5000): Edit
Properties/launchSettings.json in Huellitas.APIFrontend (5173): Vite will automatically try the next available portCORS errors
CORS errors
The backend is configured to allow all origins in development. If you still see CORS errors:
- Check that the backend is running
- Verify the API URL in your frontend code
- Clear your browser cache
JWT authentication fails
JWT authentication fails
Common JWT issues:
- Ensure the JWT
Keyinappsettings.jsonis at least 32 characters - Verify
IssuerandAudiencematch between backend and frontend - Check that tokens haven’t expired (default lifetime is set in
AuthService)
Development Scripts
Backend Commands
Frontend Commands
Next Steps
Learn More
Read the full introduction to understand the project’s goals and features