OKLABS Tools & Services

Documentation Platform

GitBook Setup

  • Container: yanqd0/gitbook
  • Port: 4000 (internal), accessible via how.oklabs.my.id
  • Location: /data/core-stack/gitbook/
  • Update Guide: Documentation Update Guide

Content Management

  • Multi-project structure: Organized by project folders
  • Markdown format: All documentation in .md files
  • Live rebuild: Automatic updates with gitbook build
  • Version control: File-based versioning

Development Tools

Monitoring & Analytics

  • Uptime Kuma: System health monitoring at uptime.oklabs.my.id
  • Apache Superset: Data visualization and analytics
  • Netdata: Real-time system metrics
  • Portainer: Docker container management

Workflow Automation

  • n8n: Workflow automation platform
  • GLPI: IT asset and help desk management
  • Paperless: Document management system

Infrastructure Management

  • Docker Compose: Service orchestration
  • Caddy: Reverse proxy with automatic SSL/HTTPS
  • PostgreSQL: Primary database for applications
  • Redis: Caching and session storage

Service URLs

Service URL Purpose
Documentation how.oklabs.my.id Central documentation hub
ProviderTrack track.oklabs.my.id Shipment tracking API
Monitoring uptime.oklabs.my.id System health dashboard
Analytics analytics.oklabs.my.id Data visualization
Workflow automation.oklabs.my.id n8n automation
Assets assets.oklabs.my.id GLPI asset management

Access & Security

Authentication Methods

  • SSH Access: Key-based authentication to VMs
  • API Tokens: For programmatic access to services
  • Web Auth: Individual service authentication
  • SSL/TLS: Let's Encrypt certificates via Caddy automatic HTTPS

Backup & Recovery

  • Database Backups: Automated PostgreSQL dumps
  • File Backups: Docker volume snapshots
  • Configuration: Infrastructure as code approach
  • Documentation: Version-controlled via GitBook

Support Procedures

Getting Help

  1. Check service status at uptime.oklabs.my.id
  2. Review documentation at how.oklabs.my.id
  3. Contact ossie@somagede.com for technical issues
  4. Use project-specific support channels when available

Reporting Issues

  1. Identify affected service and URL
  2. Provide error messages or screenshots
  3. Include steps to reproduce the issue
  4. Specify urgency level (low/medium/high/critical)

Back to OKLABS Documentation Hub

results matching ""

    No results matching ""