Fix Option A deployment to seed host directories before container start

- Add seed_testpoint_host_dirs.sh call to step_deploy_option_a() function
- Update documentation to include seeding step for Option A (matching Option B)
- Document that Option A now seeds /opt/perfsonar-tp/psconfig, /var/www/html, and /etc/apache2
- Bump perfSONAR-orchestrator.sh version to 1.0.2
- Update SHA256 checksum for perfSONAR-orchestrator.sh

This fixes an issue where Option A containers would fail or run unhealthy
because Apache configuration files were missing from /etc/apache2. The
docker-compose.testpoint.yml already had bind mounts for these directories,
but the orchestrator wasn't seeding them before the first container start.

Author: root

docs/perfsonar/tools_scripts/perfSONAR-orchestrator.sh

@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 set -euo pipefail
-# Version: 1.0.1
+# Version: 1.0.2
 # Author: Shawn McKee, University of Michigan
 # Acknowledgements: Supported by IRIS-HEP and OSG-LHC
 
@@ -255,7 +255,7 @@ EOF"
 }
 
 step_deploy_option_a() {
-  run mkdir -p /opt/perfsonar-tp/psconfig
+  run /opt/perfsonar-tp/tools_scripts/seed_testpoint_host_dirs.sh
   run bash -c "curl -fsSL https://raw.githubusercontent.com/osg-htc/networking/master/docs/perfsonar/tools_scripts/docker-compose.testpoint.yml -o /opt/perfsonar-tp/docker-compose.yml"
   run bash -c "cd /opt/perfsonar-tp && podman-compose up -d"
   run podman ps

docs/perfsonar/tools_scripts/scripts.sha256

@@ -10,7 +10,7 @@ dfbdd6abe4f99a9196376de16d92648a0327d1667ddbb1d5d4a354f04e33ce8f  fasterdata-tun
 d4db26fadfa22c2ad5788b70f361740d4e224e949ceb9873121b40f10d370ac1  perfSONAR-auto-enroll-psconfig.sh
 c591cb47a478706921ffcd6317baa7ce33ad2ec5e9f61fefde67b029cf6fa312  perfSONAR-extract-lsregistration.sh
 51db72f7a2398f1836ee0faba4bc8c0cd745473fa3518933abe0dc16a533f047  perfSONAR-install-nftables.sh
-ffe155b820782155312a813c42dcadd45e41a883b91d1c58cd0233d5c5274b67  perfSONAR-orchestrator.sh
+6359eb68bfcfa5849b0b26308fa91f4ffb7269a295762ddaf1d63cb110b0cc08  perfSONAR-orchestrator.sh
 cbf8aed3b49d46cb007ee692051008c76113e1c22fc269f53849ba7ed646cb47  perfSONAR-pbr-nm.sh
 80086418ced033d28bd5976795ff4a90ab644b8fc38a8a048c99673422d812bb  perfSONAR-update-lsregistration.sh
 bedd3dc88debd85605613922d3b35d4b25f5655edfb824e71aacb3d6a9924dc0  repair-state-json.sh

docs/personas/quick-deploy/install-perfsonar-testpoint.md

@@ -500,20 +500,62 @@ You may want to document any site-specific exceptions (e.g., additional allowed
     
 Run the official testpoint image using Podman (or Docker). Choose one of the two deployment modes:
 
-- **Option A:** Testpoint only (simplest) — only bind-mount `/opt/perfsonar-tp/psconfig` for pSConfig.
+- **Option A:** Testpoint only (simplest) — bind-mounts `/opt/perfsonar-tp/psconfig`, `/var/www/html`, and `/etc/apache2` for Apache and pSConfig.
 
 - **Option B:** Testpoint + Let’s Encrypt — two containers that share Apache files and certs via host bind mounts.
 
 Use `podman-compose` (or `docker-compose`) in the examples below.
 
 ### Option A — Testpoint only (simplest)
 
-Prepare the pSConfig directory and a minimal compose file. No other host bind-mounts are required.
+#### 1) Seed required host directories (REQUIRED before first compose up)
+
+**Why seed?** The perfsonar-testpoint container requires baseline configuration files from the image to be present on
+the host filesystem. Without seeding, the bind-mounted directories would be empty, causing Apache and perfSONAR services
+to fail.
+
+**What's seeded:**
+
+- `/opt/perfsonar-tp/psconfig` — perfSONAR pSConfig files (baseline remotes and archives)
+
+- `/var/www/html` — Apache webroot with index.html (required for healthcheck)
+
+- `/etc/apache2` — Apache config including `sites-available/default-ssl.conf`
+
+Run the bundled seeding helper script (automatically installed in Step 2):
+
+```bash
+/opt/perfsonar-tp/tools_scripts/seed_testpoint_host_dirs.sh
+```
+
+??? info "Seed script details"
+
+    - Pulls the latest perfSONAR testpoint image
+    - Creates temporary containers to extract baseline files
+    - Copies content to host directories
+    - Verifies seeding was successful
+    - Skips seeding if directories already have content (idempotent)
+
+Verify seeding succeeded:
 
 ```bash
-mkdir -p /opt/perfsonar-tp/psconfig
+# Should show config files
+ls -la /opt/perfsonar-tp/psconfig
+
+# Should show index.html and perfsonar/ directory
+ls -la /var/www/html
+
+# Should show sites-available/, sites-enabled/, etc.
+ls -la /etc/apache2
 ```
 
+??? tip "SELinux labeling handled automatically"
+    
+    If SELinux is enforcing, the `:Z` and `:z` options in the compose files will cause Podman to relabel the host paths when
+    containers start. No manual `chcon` commands are required.
+
+#### 2) Deploy the container
+
 Download a ready-made compose file (or copy it manually): Browse: [repo
 view](https://github.com/osghtc/networking/blob/master/docs/perfsonar/tools_scripts/docker-compose.testpoint.yml)
 
@@ -541,7 +583,7 @@ The container should show `healthy` status. The healthcheck monitors Apache HTTP
 
 Manage pSConfig files under `/opt/perfsonar-tp/psconfig` on the host; they are consumed by the container at `/etc/perfsonar/psconfig`. 
 
-#### Ensure containers restart automatically on reboot (systemd unit for testpoint - REQUIRED)
+#### 3) Ensure containers restart automatically on reboot (systemd unit for testpoint - REQUIRED)
 
 !!! warning "podman-compose limitation with systemd containers"