Loading repository data…
jdcntdev / repository
Sky.io is a full-stack web application designed to support companies working outdoors with real-time weather intelligence and operational safety recommendations. Backend: Node.js + Express + MySQL with JWT-based authentication. Frontend: Vite-powered SPA (HTML, CSS, JavaScript)
Sky.io Backend (package: skycare-backend) is a comprehensive safety management platform designed for companies that operate outdoors. Its goal is to optimize operational decision-making through AI-based safety recommendations.
The system combines real-time weather data with the company's location and work schedule analysis using natural language processing. With this integration, it generates personalized safety advice that allows businesses to anticipate environmental risks and plan their activities more efficiently.
Overall, Sky.io Backend is a robust backend service that combines climate information, intelligent analysis, and advanced technologies to support the continuity and safety of business operations exposed to external conditions.
| Category | Technology | Purpose | Configuration |
|---|---|---|---|
| Web Framework | Express.js 4.19.2 | HTTP server and routing | Port 3001 default |
| Database | MySQL 8.0+ with mysql2 driver | Data persistence | Connection pooling enabled |
| Authentication | JWT + bcryptjs | User authentication and password hashing | 7-day token expiration |
| AI Integration | OpenAI API 4.58.1 | Schedule parsing and recommendation generation | GPT-4o-mini model |
| Weather Data | Tomorrow.io + Open-Meteo | Real-time and forecast weather data | Fallback strategy implemented |
| Validation | Zod 3.23.8 | Input validation and type safety | Schema-based validation |
| Date/Time | Luxon 3.7.1 + tz-lookup | Timezone-aware date handling | Location-based timezone detection |
| HTTP Client | Axios 1.7.2 | External API communication | Used for weather and AI services |
├── migrations/ # Database migration files
│ ├── 001_roles.sql # User roles setup
│ ├── 002_users.sql # User management tables
│ ├── 003_companies.sql # Company data with geolocation
│ └── 004_history.sql # AI interaction history
├── src/
│ ├── lib/ # Core libraries
│ │ ├── db.js # Database connection pool
│ │ ├── openai.js # OpenAI integration
│ │ ├── recommendations.js # Safety rule engine
│ │ └── weather.js # Weather API integration
│ ├── routes/ # API route handlers
│ │ ├── auth.js # Authentication endpoints
│ │ └── companies.js # Company management
│ ├── migrate.js # Database migration runner
│ └── server.js # Main server application
└── package.json # Dependencies and scripts
This guide provides step-by-step instructions for setting up and running the Sky.io Backend system locally. It covers installation, configuration, database setup, and initial application startup.
For detailed information about individual system components, see Installation and Dependencies and Configuration.
For understanding the overall system architecture, see System Architecture.
Before setting up the Sky.io Backend, ensure you have the following installed:
| Requirement | Minimum Version | Purpose |
|---|---|---|
| Node.js | 18.0+ | JavaScript runtime environment |
| npm | 9.0+ | Package manager (comes with Node.js) |
| MySQL | 8.0+ | Primary database system |
You will also need API keys for the following external services:
# Clone the repository
cd Sky.io_Backend
# Install all project dependencies
npm install
## 2. Install dependencies
# Install dependencies
npm install
# Set up environment variables (see Configuration section)
cp .env.example .env
# Run database migrations
npm run migrate
# Start development server
npm run dev
Create a .env file in the root directory:
# Database Configuration
DB_HOST=localhost
DB_USER=your_db_user
DB_PASSWORD=your_db_password
DB_NAME=skycare_db
# Authentication
JWT_SECRET=your_jwt_secret_key
# API Keys
OPENAI_API_KEY=your_openai_api_key
TOMORROW_API_KEY=your_tomorrow_io_api_key
# Server Configuration
PORT=3001
CORS_ORIGIN=http://localhost:3000
Run the migration script to set up your database:
npm run migrate
# Development
npm run dev
# Production
npm start
POST /api/auth/register
Content-Type: application/json
{
"name": "John Doe",
"email": "john@example.com",
"password": "securepassword",
"role": "customer"
}
POST /api/auth/login
Content-Type: application/json
{
"email": "john@example.com",
"password": "securepassword"
}
GET /api/companies
Authorization: Bearer <jwt_token>
POST /api/companies
Authorization: Bearer <jwt_token>
Content-Type: application/json
{
"name": "Outdoor Adventures Inc",
"latitude": 40.7128,
"longitude": -74.0060,
"description": "Adventure tourism company"
}
GET /api/companies/:id/weather
Authorization: Bearer <jwt_token>
POST /api/companies/:id/advanced-query
Authorization: Bearer <jwt_token>
Content-Type: application/json
{
"query": "What safety precautions should we take for tomorrow's outdoor activities?"
}
GET /api/admin/users # List all users
POST /api/admin/users # Create user
PUT /api/admin/users/:id # Update user
DELETE /api/admin/users/:id # Delete user
GET /api/admin/companies # List all companies
POST /api/admin/companies # Create company
PUT /api/admin/companies/:id # Update company
DELETE /api/admin/companies/:id # Delete company
The application uses a structured migration system with the following tables:
The database connection pool in getPool() implements a singleton pattern with MySQL-specific optimizations.
The pool maintains up to 10 concurrent connections and supports both named placeholders and multiple statements for complex operations.
| Configuration Property | Value | Purpose |
|---|---|---|
| host | process.env.DB_HOST | Database server hostname |
| port | Number(process.env.DB_PORT || 3306) | Database port with default fallback |
| user | process.env.DB_USER | Database username |
| password | process.env.DB_PASSWORD | Database password |
| database | process.env.DB_NAME | Target database name |
| connectionLimit | 10 | Maximum concurrent connections |
| namedPlaceholders | true | Enable :param syntax for queries |
| multipleStatements | true | Allow multiple SQL statements per query |
The query() function provides a simplified interface that automatically handles connection pooling and result extraction through array destructuring of the MySQL2 response format.
Sources:
src/lib/db.js (lines 5–24)
The database implements a simple two-table schema optimized for the safety management platform's core functionality.
Both tables use InnoDB engine with UTF-8 character set for full Unicode support.
| Table | Primary Purpose | Key Features |
|---|---|---|
| users | User authentication and profiles | Email uniqueness constraint, password hashing support |
| companies | Company location and activities | Decimal lat/lon precision, activity categorization |
DECIMAL(10,7) precision for latitude and longitude coordinates, enabling accurate weather API integration.password_hash field.Both tables include auto-incrementing primary keys and TIMESTAMP fields with automatic creation timestamps for audit trails.
The API Layer serves as the primary interface between client applications and the Sky.io Backend system, providing RESTful endpoints for user authentication, company management, weather data retrieval, and AI-powered safety recommendations. This layer implements the Express.js server framework with comprehensive middleware for request processing, validation, and error handling.
For detailed information about server configuration and middleware setup, see 3.2.1. For authentication implementation details, see 3.2.2. For company-specific API functionality, see 3.2.3.
RESTful API Architecture The API layer follows REST architectural principles with a clear separation between authentication and business logic endpoints. The system exposes two main route groups mounted on distinct URL paths.
The system implements a robust weather data fetching strategy:
The Safety Recommendations Engine provides rule-based safety recommendations for outdoor opera
Selected from shared topics, language and repository description—not editorial ratings.
jdcntdev /
Sky.io is a full-stack web application designed to support companies working outdoors with real-time weather intelligence and operational safety recommendations. Backend: Node.js + Express + MySQL with JWT-based authentication. Frontend: Vite-powered SPA (HTML, CSS, JavaScript)