ENT365 Host Deployment Guide

This guide walks through provisioning a fresh ENT365 workstation or server to run the Michael J Wright Fedora archive stack with Cloudflare connectivity. Follow the sections in order; once complete, the host will replace the office machine while maintaining the same public endpoints.

1. Prerequisites

2. System Preparation

1. Install/verify WSL2

   wsl --install
   wsl --set-default-version 2
   

2. Install Docker Desktop
   • Turn on “Start Docker Desktop when you log in”.
   • Under Settings → Resources → File Sharing, ensure the drive containing the repo (e.g., C:) is shared.
3. Install supporting tools

   winget install --id Git.Git -e
   winget install --id OpenJS.NodeJS.LTS -e
   winget install --id Cloudflare.cloudflared -e
   

4. Login to Cloudflare WARP (if used)
   • Confirm the client is connected and assigned to the correct Zero Trust team.

3. Repository Bootstrap

1. Clone the repository

   cd C:\services
   git clone https://github.com/Rob142857/fedoraMJWArtist.git
   cd fedoraDockerCloudflare
   

2. Install npm dependencies

   npm install
   

3. Copy and configure environment variables

   Copy-Item .env.example .env
   notepad .env
   

   • Provide strong values for Fedora admin/secondary users and Postgres credentials.
   • Set FEDORA_TUNNEL_HOSTNAME (optional) to the Cloudflare hostname used for the tunnel.
4. Review configuration overrides
   • docker-compose.yml (service definitions)
   • config/tomcat-users.xml (ensure FEDORA_ADMIN/SECONDARY users match .env)
   • fcrepo.properties (storage layout)

4. Cloudflare Tunnel Setup

1. Authenticate cloudflared

   cloudflared tunnel login
   

   Select the michaeljwright.com.au zone.
2. Create or reuse tunnel
   • If reusing: cloudflared tunnel list to find the existing tunnel ID.
   • To create new (if migrating):

     cloudflared tunnel create fedora-ent365
     

3. Configure tunnel routing

   mkdir C:\services\cloudflared
   cloudflared tunnel route dns fedora-ent365 fcrepo.michaeljwright.com.au
   

4. Set tunnel service configuration (C:\services\cloudflared\config.yml)

   tunnel: fedora-ent365
   credentials-file: C:\Users\%USERNAME%\.cloudflared\fedora-ent365.json
   ingress:
     - hostname: fcrepo.michaeljwright.com.au
       service: http://localhost:8080
     - service: http_status:404
   

5. Install tunnel as a service

   nssm install Cloudflared "C:\Program Files\cloudflared\cloudflared.exe" "tunnel run fedora-ent365 --config C:\services\cloudflared\config.yml"
   nssm start Cloudflared
   

   (Alternatively use cloudflared service install if available.)

5. Configure Cloudflare Worker

1. Authenticate Wrangler

   npx wrangler auth login
   

2. Set the Fedora proxy secret

   npx wrangler secret put FEDORA_BASIC_AUTH
   # Paste "Basic base64(fedoraAdmin:SuperSecurePassword!)"
   

3. Deploy the Worker

   npm run deploy
   

   Confirm the route data.michaeljwright.com.au/fcrepo/* appears in the output.

6. Start the Docker Stack

1. Run the automation script

   pwsh -ExecutionPolicy Bypass -File .\quickstartdockerandcloudflared.ps1 -ForceRestartTunnel
   

2. Verify container health

   docker compose ps
   docker compose logs fcrepo --tail=100
   

3. Confirm Fedora API access
   • Local: https://localhost:8080/fcrepo/rest/
   • Through Worker: https://data.michaeljwright.com.au/fcrepo/rest/

7. Post-Install Validation

1. Prometheus & Grafana
   • http://localhost:9090 and http://localhost:3000
   • Update Grafana admin password if not already changed.
2. Documentation check

   npm run build:docs
   npm run pages:preview   # optional preview
   npm run pages:deploy    # publish to production branch
   

3. Backups
   • Schedule nightly snapshots of postgres_data and fcrepo_data volumes (refer to docs/fedora-upgrade-guide.md).
4. Update DNS / Monitoring
   • Ensure fcrepo.michaeljwright.com.au resolves to the tunnel.
   • Confirm Cloudflare Zero Trust policies reflect the new source IP/connector.
5. Record the migration
   • Update docs/development-roadmap.md with the deployment date.
   • Note the new host details in the operations runbook or CMDB.

8. Cut-over Checklist

• Fedora REST API reachable via Worker and direct tunnel.
• Prometheus and Grafana confirm container health.
• Documentation site updated and deployed.
• Backups configured and tested.
• Cloudflare tunnel service auto-starts on reboot.
• Retire or power down the old office host after final verification.

Keep this document updated after each installation or infrastructure change to maintain a reliable reference for future rebuilds.