Verification and Access
Validation Checklist
Database connectivity
psql -h $DB_HOST -U <user> -d insightly connects from host without error
Cache/queue (Redis)
docker exec -it insightly-redis redis-cli ping returns PONG
API readiness
curl http://localhost:80/health returns healthy response
UI access
UI loads at http://<host-ip>:3000 with no console error
Integration connectivity
Connected Jira/GitHub/GitLab shows "connected" status in the UI, (refer to Integrations for more info).
Data flow
Open relevant dashboard in Hivel UI: records/metrics appear for the connected integration
Step 1: Verify All Services Are Running
On the host, run:
docker ps
./deploy.sh --health
./deploy.sh --health auth-svcStep 2: Test Service Endpoints
Run these curl commands on the host to verify each service is responding:
curl http://localhost:80/health # API Gateway
curl http://localhost:8095/health # Auth Service
curl http://localhost:8082/hivelapi/health # Insightly Service
curl http://localhost:3000 # UISuccess: Each endpoint returns a healthy response with no errors
Step 3: Load the UI
Open a browser and navigate to one of the URLs below (see Step 4 to choose which option):
If using Option A:
http://<host-ip>:3000If using Option B or C: Follow those configuration steps first, then access via your configured URL
Success: UI loads with no console errors
Step 4: Access the Application
Choose one of these access methods:
Option A: Direct Host IP (Quick test, non-production only)
Use this only for testing. No HTTPS, no load balancing.
Web UI:
http://<host-ip>:3000API Gateway:
http://<host-ip>
Option B: Your Own Load Balancer / Reverse Proxy (Advanced)
Choose this if you need a load balancer or reverse proxy in front of the host (ports 80, 3000) but prefer not to use Caddy.
Option C: Caddy for Automatic HTTPS (Recommended for Production)
Choose this for automatic HTTPS without a separate load balancer. See HTTPS Setup with Caddy.
Step 5: Confirm Data Flow
Connect at least one integration (Jira, GitHub, or GitLab) and verify it shows connected status and data in the UI. See Application Setup Guide: User Sign-up and Integration for step-by-step instructions.
Installation Complete
Your deployment is complete when all of the following are true:
✓ All containers show Up with healthy status
✓ All service endpoints return healthy responses
✓ UI loads without console errors
✓ At least one integration (Jira/GitHub/GitLab) is connected and shows data
Next Step
Proceed to Application Setup Guide: User Sign-up and Integration to create your first admin account and connect engineering tools.
Last updated