# Shared-hosting deployment guide

Publication: OpenForex Society / OpenForex Foundation. Updated 2026-09-24.

## Current package layout
The public_html directory contains the PHP entry point, shared renderer, and assets. Documentation directories sit beside it. Deploy the complete package and set the web document root to public_html so the renderer can read sibling content without exposing the entire source tree as the website root.

The portal is a read-only Markdown publication. It does not require a DokuWiki installation. The existing dokuwiki-overlay is a separate integration artifact and does not itself install an editing engine.

## Deployment sequence
1. Retain a backup of the existing site and content.
2. Upload the public_html, seed-content, docs, developer, foundation, community, and legal directories while preserving their relationship.
3. Configure a compatible PHP runtime and the intended public document root.
4. Supply the official repository URL through OPENFOREX_REPOSITORY_URL if available.
5. Open the homepage, several articles, a Markdown download, and a missing route.
6. Check styles, icons, search, and mobile navigation in a browser.

The application is designed to use relative asset paths, including when mounted below a domain root. Confirm that the server's directory-index setting includes index.php.

## Content updates
Edit the reviewed Markdown source and deploy the corresponding files. Keep the root workspace and shared package synchronized. Adding a file to a public content directory makes it available in the catalog automatically; there is no separate draft-access control in this reader.

## Backups and access
Back up the application and sibling content directories together. Keep configuration, credentials, and backup archives outside publicly served paths. Grant the web runtime only the filesystem access needed for reading this portal; editing takes place through the deployment workflow.

## Optional authoring engines
DokuWiki or Wiki.js can provide a separate editing workflow, but each requires an actual installation, permission configuration, and an agreed synchronization process. The supplied files do not prove either engine is deployed.

See [architecture](?page=docs/architecture), [migration](?page=docs/migration-shared-to-vps), and [portal operations](?page=docs/wiki-portal).