JOTRE

INACT for JOTRE, the Joint Operation of Timas and Rekind. One of the big five. Not the same client as Timas or KTP.

At a glance

Jira	INA36, Timas Rekind
INA05 INACT Instance value	JOTRE
Repository	binari-digital/ina-jotre. Renamed on 2026-08-23 from ina-timas-rekind.
Encrypted twin	binari-digital/ina-jotre-encrypted
INARTS GitLab	inact/inact-timas-rekind, plus the encrypted twin. The old name stays; INARTS cannot rename it.
Permanent branches on origin	main, staging, development. Only development and main deploy.
Database	MySQL
Production	The client's own server, on premise. Pulled by hand from INARTS over VPN.
Staging	none
Dev (QA)	inact-jotre-encrypted.bdt.dev on the Rumah box

TODO: production MySQL version.

Repositories and remotes

The inarts remote points at the old name, inact-timas-rekind. That is deliberate, not a mistake. Because INARTS own INACT, they receive the plain repository as well as the encrypted one.

Environments and deploy

Push to	Script	What happens
development	deploy/dev.sh	Sync plain to encrypted, push both to GitHub and INARTS. The consumer pulls ~/www/inact-jotre-encrypted on the Rumah box and runs php7.3 vendor/bin/phinx migrate.
main	deploy/prod.sh	Sync plain main to encrypted main, push to GitHub and INARTS. No consumer. Eris connects over VPN and pulls encrypted main from INARTS onto the client's machine by hand. After the push the code is available to release, not released.

Database

Driver	MySQL
QA database	MySQL on the Rumah box itself, database inact_timas_rekind_encrypted
Test database	Shared dev DB host 192.168.1.52, port 3357, database inact-timas-rekind

How this fork differs from master

Measured on 2026-09-05.

Module files that differ	141
Modules with the most changes	routing 20, dms_reference 19, purchase_order 12, documents_master 9, documents 9, adms 8, member 7
Libraries that differ	additional_global_variables.inc.php, inweb.lib.php, numbering_function.inc.php, procure_function.inc.php, reference_function.inc.php, tracking_function.inc.php
Top-level files that differ	_menu.php, auto_logout.php, setting.php
Migrations	433 in total. 27 only here, 25 in master not taken. Newest 2026-08.

Files only in this fork

• modules/delivery_order/delivery_order_print_publish.php
• modules/documents_master/documents_master_handler_print_mdr_report_gde.php
• modules/documents_master/documents_master_handler_print_mdr_report_summary_gde.php
• modules/expedite/expedite_import_master_schedule.php
• modules/expedite/expedite_upload.php
• modules/expedite/form_evidence_upload.inc.php
• modules/expedite/form_import_master_schedule.inc.php
• modules/member/direct_download_report/jotre_procurement_status_report.php and its .inc.php
• modules/procurement_reference/item_master.php
• modules/routing/routing_bcc_helper.php
• modules/spb/spb_ajax.php, spb_ajax_direct.php, spb_handler_ajax_form.php

The fork also holds .bak, .tmp and .working copies under expedite/, purchase_order/ and spb/. They are leftovers, not features.

Files in master that this fork lacks

• modules/adms/adms_rev_sort.inc.php
• modules/adms_reference/adms_reference_import.inc.php
• modules/dms_reference/autopublish_auto_folder_creation.php
• modules/dms_reference/well_site.php
• modules/routing/routing_handler_ready_to_return.php
• modules/routing/routing_handler_republish.php

inweb_config keys

	Keys
Only in this fork	none
Missing here	autopublish_auto_folder_creation, consolidated_routing_view, enable_ldap_browse, enable_ldap_login, enable_return_on_audit, enable_routing_notif_digest, enable_routing_overdue_notif_digest, enable_well_site, inact_operator_role, routing_notif_digest_hour, routing_return_format

Customizations documented so far

None yet. Feature pages arrive in phase 3 of the docs plan.

Known gotchas

• Three names for one client. GitHub says ina-jotre, INARTS says inact-timas-rekind, Jira says Timas Rekind. Older tickets and chat use "Timas Rekind" too.
• staging exists but does not deploy. The workflow only maps development and main.
• Raw SQL files in db/migrations. accurate_field_population.sql, accurate_integration_migration.sql and db_accurate_tables.sql sit next to the phinx migrations. phinx ignores them; they were run by hand.
• Has Single Session. enable_last_login_wins is present here and in master, but not in Jadestone.
• The only client instance with the procurement chain switched on. Read from its QA database on 2026-09-06: spb, rfq, bid_evaluation, purchase_order, procurement_documents, mrr, expedite, vendor_management. Approved documents are pushed to the Accurate accounting system by the twelve accurate_* cron scripts and hooks in the SPB and PO handlers. See Requisition and Purchase Order.
• iw_mysql_query() still works here. Legacy paths that fatal elsewhere (Multiple Sign Off, Unpublish, the correspondence print listing, the procurement tabulation and email screens) run on this instance.