MokoConsulting/mokoplatform
1
0
Fork 0
Code Issues 9 Pull Requests Releases 8 Wiki Activity

feat: Infrastructure-as-Code � provision client environments in minutes #4

New Issue
Closed
opened 2026-05-08 00:51:00 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-08 00:51:00 +00:00
Owner
Copy Link
Copy Source

Terraform/Ansible definitions for spinning up new client environments (Joomla + Dolibarr + monitoring + backups) automatically.

Vision

New client onboarding goes from days to minutes. Run one command, get a fully configured environment.

Acceptance Criteria

  • Client provisioning orchestrator (cli/client_provision.php - PR #88)
  • Repo creation from template (via Gitea API)
  • Auto-inject Gitea Actions variables and secrets
  • Auto-configure monitoring (Grafana dashboard push + endpoint registration)
  • DNS record creation via DreamHost API
  • SSL certificate provisioning
  • Terraform modules for server provisioning (future - currently on DreamHost shared hosting)
  • Ansible playbooks for Joomla/Dolibarr setup (future)

Delivered (2026-05-25)

cli/client_provision.php orchestrates the full onboarding from a single JSON config:

  1. Create repo from Template-Client-WaaS
  2. Inject variables (hosts, paths, ports)
  3. Inject secrets (SSH keys via @file references)
  4. Push Grafana monitoring dashboard
  5. Register monitoring URLs/domains

Example: php cli/client_provision.php --config clients/newclient.json --dry-run

Remaining

DNS and SSL automation depend on DreamHost API integration. Server provisioning (Terraform) is deferred until cloud migration.

Terraform/Ansible definitions for spinning up new client environments (Joomla + Dolibarr + monitoring + backups) automatically. ## Vision New client onboarding goes from days to minutes. Run one command, get a fully configured environment. ## Acceptance Criteria - [x] Client provisioning orchestrator (`cli/client_provision.php` - PR #88) - [x] Repo creation from template (via Gitea API) - [x] Auto-inject Gitea Actions variables and secrets - [x] Auto-configure monitoring (Grafana dashboard push + endpoint registration) - [ ] DNS record creation via DreamHost API - [ ] SSL certificate provisioning - [ ] Terraform modules for server provisioning (future - currently on DreamHost shared hosting) - [ ] Ansible playbooks for Joomla/Dolibarr setup (future) ## Delivered (2026-05-25) `cli/client_provision.php` orchestrates the full onboarding from a single JSON config: 1. Create repo from Template-Client-WaaS 2. Inject variables (hosts, paths, ports) 3. Inject secrets (SSH keys via @file references) 4. Push Grafana monitoring dashboard 5. Register monitoring URLs/domains Example: `php cli/client_provision.php --config clients/newclient.json --dry-run` ## Remaining DNS and SSL automation depend on DreamHost API integration. Server provisioning (Terraform) is deferred until cloud migration.
jmiller added the type: feature label 2026-05-11 17:08:45 +00:00
Sign in to join this conversation.
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels type: feature
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/mokoplatform#4
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?