Prima Energy
INACT for Prima Energy. One of the big five since 2026-09-08, when Eris confirmed it is an active client; pages verified before that date were not checked on this fork.
At a glance
| Jira | INA15, Prima Energy, for support and hosting work; INA30, Prima Energy CR, for change requests since 2026-09-11 |
| INA05 INACT Instance value | Prima Energy |
| Repository | binari-digital/ina-primaenergy |
| Encrypted twin | none on GitHub |
| INARTS GitLab | inact/inact-prima-energy |
| Permanent branches on origin | main, staging, development; the same three on INARTS |
| Database | MySQL |
| Production | primaenergy.inactsoft.com (108.136.35.221), pulls main from INARTS GitLab; deployed by GitHub Actions since 2026-09-08 |
| Staging | staging-pe.inactsoft.com on its own box (103.123.62.190), pulls staging from INARTS GitLab; local MySQL inact_prim4EnergyDB |
| Dev (QA) | inact-primaenergy.bdt.dev on the Rumah box; the local vhost is inact-primaenergy.eris.place |
Repositories and remotes
The local checkout at www/ina-primaenergy has origin (GitHub) and inarts (INARTS GitLab), like the other forks. From 2025-02-20 until 2026-09-08 nothing moved; on 2026-09-08 the GitHub Actions deploy tooling (deploy/ + .github/workflows/deploy.yml) was added to all three branches (INA15-39). The INARTS GitLab repo keeps its own name inact-prima-energy and cannot be renamed.
Environments and deploy
On GitHub Actions, self-hosted rumah runner, since 2026-09-08 (INA15-39). Plain fork, no encrypted pair — the KTP shape. .github/workflows/deploy.yml runs deploy/{dev,staging,prod}.sh on a push to the matching branch. Each env mirrors GitHub <branch> to INARTS GitLab, then the target box pulls from GitLab and runs php7.3 vendor/bin/phinx migrate. A Slack notice goes to #cicd-inact.
| Env | Branch | Where | URL |
|---|---|---|---|
| dev (QA) | development | Rumah, ~/www/inact-primaenergy (built in place) | inact-primaenergy.bdt.dev |
| staging | staging | own box staging-pe.inactsoft.com (103.123.62.190), /var/www/html/staging_pe | staging-pe.inactsoft.com |
| prod | main | client box primaenergy.inactsoft.com (108.136.35.221), ~/www/inact | primaenergy.inactsoft.com |
Both remote boxes pull from INARTS GitLab (their origin), so the runner mirrors GitHub → GitLab first; SSH to both is on port 22122. The legacy webhook deployer was disabled at cutover. All three environments migrate cleanly. Staging moved to its own box staging-pe.inactsoft.com on 2026-09-12 (was the shared inactsoft.com); it runs a local MySQL inact_prim4EnergyDB whose schema came from a dump, so phinx was baselined once (all migrations marked applied) before the first Actions deploy. The staging deploy also restores two runtime-cached pdfviewer signature.png files before git pull so a dirty tree never blocks it.
Database
| Driver | MySQL |
| Test database | Shared dev DB host 192.168.1.52, port 3357, database inact_primaenergy_eris: 2 projects, 902 MDR rows, 6,613 library rows, newest routing 2025-08-19 |
| Modules enabled | DMS only: five dms modules, master_stamp and config are installed; no ADMS, no procurement, no budget (local dev DB, 2026-09-10) |
| Report menu | the four of master: Documents Library, Routing Overdue, MDR Report, MDR Report Sumary |
How this fork differs from master
Measured on 2026-09-08 against inact at its newest migration, 20260826.
| Module files that differ | 115 |
| Modules with the most changes | dms_reference 19, routing 15, documents 11, documents_master 10, adms 8, adms_reference 7, member 7, reference 6 |
| Libraries that differ | additional_global_variables.inc.php, inweb.lib.php, reference_function.inc.php, tracking_function.inc.php; signature_function.inc.php is missing |
| Top-level files that differ | auto_logout.php, setting.php |
| Migrations | 393 in total. 5 only here, 43 in master not taken. Newest 2024-11-28 |
Files only in this fork
Two backup copies of the multi-upload handler in modules/documents_master/: documents_master_multiupload_upload -WHP.php and documents_master_multiupload_uploadBackup.php. No feature of its own.
Files in master that this fork lacks
modules/adms/adms_rev_sort.inc.phpmodules/adms_reference/adms_reference_import.inc.phpmodules/dms_reference/autopublish_auto_folder_creation.phpmodules/dms_reference/retention.phpmodules/dms_reference/watermark_settings.phpmodules/dms_reference/well_site.phpmodules/documents/export_excel.phpmodules/documents/json/modules/documents_master/documents_master_multiupload_attachment.phpmodules/documents_master/json/progress_column_group.jsonmodules/routing/routing_handler_ready_to_return.phpmodules/routing/routing_handler_republish.php
The five migrations only here are from October and November 2024: ts_doc_classifications, ts_function_codes, a reference column on the MDR and on the library, and rout_sequence_no on ts_map_routing_to. Master has since taken the same features under other migration names, so the tables overlap but the migration history does not.
modules/dms_reference/auto_doc_numbering.php was in this list until 2026-09-13: INA30-2 ported Auto Doc Numbering from master onto development and staging, with three table migrations under master's names and a fourth that seeds enable_auto_doc_numbering = 0. It reaches main at the next release. See Document Library.
inweb_config keys
| Keys | |
|---|---|
| Only in this fork | none |
| Missing here | autopublish_auto_folder_creation, consolidated_routing_view, enable_auto_doc_numbering (both on development and staging since September 2026, see below), enable_doclib_retention, enable_last_login_wins, enable_ldap_browse, enable_ldap_login, enable_return_on_audit, enable_routing_notif_digest, enable_routing_overdue_notif_digest, enable_watermark, enable_well_site, inact_operator_role, routing_notif_digest_hour, routing_return_format |
92 keys against master's 107 on main. development and staging already carry consolidated_routing_view (INA30-1) and enable_auto_doc_numbering (INA30-2). enable_next_issue_code is on in the test database.
Customizations documented so far
The DMS report pages carry a Prima Energy row: Routing Overdue, MDR Report, MDR Report Summary, Documents Library. Document Library has one for Auto Doc Numbering (INA30-2). Everything else is still to be checked.
Known gotchas
- Far behind master. 43 master migrations are not here and the repository was quiet from February 2025 to September 2026, when the INA30 change requests started. A port from master usually needs its prerequisites ported first: no Ready to Return, no republish, no retention, watermark or well site. Auto numbering arrived with INA30-2.
- The old report handlers. The MDR Report still has the SQL Server-only Over Due Status filter (it errors on this MySQL instance), and the MDR Report Summary runs one query per document and status.
- Staging runs on its own box since 2026-09-12 (
staging-pe.inactsoft.com,/var/www/html/staging_pe, local MySQLinact_prim4EnergyDB) — the old shared-box "access denied" migrate failure is gone. Its schema came from a dump with nophinxlog, so phinx was baselined once (all migrations marked applied); a plainmigratewould otherwise re-run the whole history. The deploy alsogit checkouts the two runtime-cachedpdfviewer{,n}/web/api/cache/signature.pngfiles beforegit pullso a dirty tree can't block it. iw_mysql_querystill appears twice inrouting_handler_print_dueroute.php. The helper throws in this fork as in master, so any path that reaches those calls fatals.