Environments

Fangate uses different domains for production, development, and feature testing.

Environment Overview

Domain	Purpose
fangate.app	Marketing website
fangate.co	Development environment for testing before release
feature.fangate.co	Feature testing / staging
fangate.info	Production — live environment after release from fangate.co

API Base URLs

Environment	Base URL
Production	`https://fangate.info/api`
Development	`https://fangate.co/api`
Staging (Feature)	`https://feature.fangate.co/api`

Usage Guidelines

Production (`fangate.info`)

Use for live integrations
Real payment processing
Real user data
All features fully operational

Development (`fangate.co`)

Use for integration testing before going live
Test payments (use test card numbers)
Safe for development and staging integrations

Staging (`feature.fangate.co`)

Use for testing unreleased features
May have experimental or unstable APIs
Useful for QA and pre-release validation

Swagger / OpenAPI

Live backend (Laravel L5-Swagger)

Interactive docs are generated from PHP annotations:

Production: https://fangate.info/api/documentation
Development: https://fangate.co/api/documentation

After changing API annotations in Fangate-backend, regenerate the spec:

bash

cd Fangate-backend
php artisan l5-swagger:generate

Fangate-docs (static copy + Swagger UI)

This documentation site ships /openapi.json and /swagger.html (Swagger UI).
To refresh the JSON from the backend:

bash

cd Fangate-docs
npm run sync-openapi

Then open Swagger UI from the top nav or directly at /swagger.html while running npm run docs:dev.

Security Notes

All API communication uses HTTPS only
Never expose production API credentials in client-side code
Use environment variables for API keys and tokens
Test integrations in development before production deployment