a6484de35e
Some checks failed
Build and Push Docker Images / docker (push) Failing after 1m57s
Phase 2 Backend Integration Complete: Backend Infrastructure: - Created NocoDB client abstraction layer (src/api/nocodbClient.ts) - Clean TypeScript API hiding NocoDB query syntax complexity - Helper methods for orders, stats, search, timeline, and filtering - Automatic date range handling and pagination support API Routes: - POST /api/admin/stats - Dashboard statistics with time range filtering - GET /api/admin/orders - List orders with search, filter, sort, pagination - GET /api/admin/orders/[id] - Single order details - PATCH /api/admin/orders/[id] - Update order fields - DELETE /api/admin/orders/[id] - Cancel order (soft delete) - GET /api/admin/orders/export - CSV/Excel export with filters Dashboard Updates: - Real-time data fetching from NocoDB - Time range selector (7d, 30d, 90d, all time) - Recharts line chart for orders timeline - Recharts pie chart for status distribution - Loading states and error handling - Dynamic stat cards with real numbers Dependencies Added: - papaparse - CSV export - xlsx - Excel export with styling - @types/papaparse - TypeScript support Data Types: - OrderRecord interface for NocoDB data structure - DashboardStats, TimelineData, OrderFilters interfaces - Full type safety across API and UI Environment Configuration: - NOCODB_BASE_URL, NOCODB_BASE_ID configured - NOCODB_API_KEY, NOCODB_ORDERS_TABLE_ID configured - All credentials stored securely in .env.local Ready for testing with sample data in NocoDB! 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Puffin Offset - Carbon Offsetting for Yachts
This application helps users calculate and offset the carbon footprint of yachts through verified carbon offset projects.
Features
- Carbon footprint calculation for yacht trips
- Integration with Wren carbon offset projects
- Responsive UI for mobile and desktop
- Contact forms powered by Formspree
Setup
Local Development
- Install dependencies:
npm install
- Create a
.envfile with your API tokens:
VITE_WREN_API_TOKEN=your-token-here
VITE_FORMSPREE_CONTACT_ID=your-formspree-contact-form-id
VITE_FORMSPREE_OFFSET_ID=your-formspree-offset-form-id
- Run the development server:
npm run dev
Docker Setup
This project can be run in Docker containers using Docker Compose, and is configured to work with an Nginx reverse proxy on the host.
Prerequisites
- Docker
- Docker Compose
- Nginx (on the host system for SSL termination and reverse proxying)
Running with Docker Compose
- Build and start the containers:
docker compose up -d
-
The Docker container will listen on port 3800, which should be reverse-proxied by your host Nginx.
-
Stop the containers:
docker compose down
Nginx Configuration
The project includes two Nginx configuration files:
nginx.conf: Used INSIDE the Docker container to serve the static files on port 3800nginx-host.conf: A reference config for setting up your Nginx on the HOST to reverse proxy to the Docker container
To set up the host Nginx:
- Copy the nginx-host.conf to your Nginx sites directory:
sudo cp nginx-host.conf /etc/nginx/sites-available/puffinoffset.com
sudo ln -s /etc/nginx/sites-available/puffinoffset.com /etc/nginx/sites-enabled/
- Uncomment the SSL certificate lines after you've obtained certificates using Certbot or another SSL provider
- Test and reload Nginx:
sudo nginx -t
sudo systemctl reload nginx
Environment Variables
When using Docker, the environment variables are mounted as a volume from your local .env file. Make sure it contains:
VITE_WREN_API_TOKEN=your-token-here
VITE_FORMSPREE_CONTACT_ID=your-formspree-contact-form-id
VITE_FORMSPREE_OFFSET_ID=your-formspree-offset-form-id
Backend Service (Optional)
The docker-compose file includes a commented section for running the backend script (app.js) in a separate container. To enable it:
- Uncomment the
backendservice indocker-compose.yml - Ensure your
.envfile contains the needed variables - Run
docker compose up -dto start both services
API Documentation
For Wren API documentation, visit: https://wren.co/api
Building for Production
# Without Docker
npm run build
# With Docker
docker compose build
The production build will be available in the dist directory, or served by Nginx in the Docker container.