MyInfra PPA (Asset Management Service)

Microservice for asset management, split from the main myinfra-backend.

Architecture Overview

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│                 │     │                 │     │                 │
│  myinfra-       │     │  myinfra-       │     │  myinfra-ppa    │
│  frontend       │────▶│  backend        │     │  (this service) │
│  (Nuxt 3)       │     │  (Laravel)      │     │  (Laravel)      │
│                 │     │                 │     │                 │
│  Port: 3000     │     │  Port: 8000     │     │  Port: 8001     │
└─────────────────┘     └─────────────────┘     └─────────────────┘
        │                       │                       │
        │                       │                       │
        │               ┌───────┴───────┐               │
        │               │               │               │
        │               ▼               ▼               │
        │       ┌───────────────────────────┐           │
        │       │      PostgreSQL           │           │
        │       │  ┌─────────┬───────────┐  │           │
        │       │  │myinfra_db│myinfra_ppa│ │◀──────────┘
        │       │  │ (core)  │ (assets)  │  │
        │       │  └─────────┴───────────┘  │
        │       └───────────────────────────┘
        │                       │
        │                       ▼
        │               ┌───────────────┐
        └──────────────▶│   Keycloak    │
                        │   Port: 8080  │
                        └───────────────┘

Service Responsibilities

myinfra-backend (Core)

• User authentication/authorization
• User management
• Roles and permissions (Spatie)
• Organizations hierarchy
• Pegawai (staff) profiles
• Shared reference data (Negeri, Daerah, Bandar, etc.)

myinfra-ppa (This Service)

• Asset (Aset) management - buildings and roads
• SubDPA management
• DAK (Daftar Aset Khusus)
• PTRA (Asset reception plans)
• Asset-related reports and statistics

Database Configuration

This service uses dual database connections:

Connection	Database	Purpose
pgsql (default)	myinfra_ppa	Asset tables (Aset, SubDpa, Dak, etc.)
core	myinfra_db	Users, roles, permissions, organizations

Models that connect to core database have protected $connection = 'core';

Authentication

Uses Keycloak JWT authentication via custom guard. The flow:

1. Frontend authenticates with Keycloak via myinfra-backend
2. JWT token stored in HTTP-only cookie
3. This service validates JWT using Keycloak's JWKS endpoint
4. User lookup happens against core database using preferred_username

Getting Started

Prerequisites

• myinfra-backend must be running (provides PostgreSQL, Redis, Keycloak)
• Docker and Docker Compose

Setup

1. Copy environment file:

cp .env.example .env

2. Generate app key:

php artisan key:generate

3. Start the service:

make up

4. Run migrations (if needed):

make artisan cmd="migrate"

Available Commands

make up              # Start containers
make down            # Stop containers
make restart         # Rebuild and restart
make bash            # Shell into container
make artisan cmd="..." # Run artisan commands
make logs            # View logs

API Endpoints

All endpoints require authentication.

Variable	Used By	Format (no /api)
STAGING_PGSN_API_URL	PPA, OPA, PPUN	http://myinfra-pgsn.url
STAGING_PPA_API_URL	OPA, PPUN	http://myinfra-ppa.url
BACKEND_PGSN_API_URL	Frontend (SSR)	http://myinfra-pgsn.url
BACKEND_PPA_API_URL	Frontend (SSR)	http://myinfra-ppa.url
BACKEND_OPA_API_URL	Frontend (SSR)	http://myinfra-opa.url
BACKEND_PPUN_API_URL	Frontend (SSR)	http://myinfra-ppun.url

Assets

Method	Endpoint	Description
GET	/api/aset	List assets
POST	/api/aset	Create asset
GET	/api/aset/{id}	Get asset
PUT	/api/aset/{id}	Update asset
DELETE	/api/aset/{id}	Delete asset
GET	/api/aset/statistik	Asset statistics
POST	/api/aset/dropdown-data	Get dropdown options
GET	/api/aset/{id}/subdpas	Get asset's sub-DPAs

Health Check

Method	Endpoint	Description
GET	/api/health	Service health status

Frontend Integration

The frontend calls this service via proxy:

Browser -> /api-ppa/* -> Nuxt Server -> http://localhost:8001/api/*

Environment variables:

NUXT_API_PPA_URL_SERVER=http://localhost:8001/api
NUXT_PUBLIC_API_PPA_URL=/api-ppa

Docker Network

This service connects to the existing myinfra-backend network:

networks:
  myinfra-network:
    external: true
    name: myinfra-backend_myinfra-network

This allows access to shared services (PostgreSQL, Redis, Keycloak) running in myinfra-backend.

File Structure

myinfra-ppa/
├── app/
│   ├── Guards/
│   │   └── KeycloakGuard.php      # JWT validation
│   ├── Helpers/
│   │   └── helpers.php            # getCurrentUser(), etc.
│   ├── Http/
│   │   ├── Controllers/Api/
│   │   │   └── AsetController.php
│   │   └── Middleware/
│   │       ├── Authenticate.php
│   │       └── InjectTokenFromCookie.php
│   ├── Models/
│   │   ├── Aset.php               # Main asset model
│   │   ├── User.php               # Uses 'core' connection
│   │   └── ...
│   └── Providers/
│       └── AuthServiceProvider.php
├── config/
│   ├── auth.php                   # Keycloak guard config
│   ├── cors.php                   # CORS settings
│   └── database.php               # Dual DB connections
├── routes/
│   └── api.php                    # API routes
├── docker-compose.yml
├── Dockerfile
└── Makefile

Troubleshooting

Cannot connect to database

Ensure myinfra-backend containers are running and the network exists:

docker network ls | grep myinfra

Authentication failing

1. Check Keycloak is accessible at configured URL
2. Verify KEYCLOAK_REALM and KEYCLOAK_CLIENT_ID match
3. Check cookie is being forwarded (credentials: true)

CORS errors

Ensure APP_FRONTEND_URL in .env matches the frontend origin.

...