NASPO ValuePoint¶

naspovaluepoint.org is part of the website portfolio maintained and supported by Online Services.

Repository¶

Item	Value
GitHub repository	`NASPO-ValuePoint/NVP`
Canonical local path	`~/Sites/naspo/naspovaluepoint.org`

Operational Overview¶

NASPO ValuePoint is operated with separate production, staging, and development environments. Code is promoted through Git branches, and each branch maps to the matching server environment.

Branch	Environment	Deployment
`dev`	Development	Automatic when commits are pushed or merged into `dev`
`staging`	Staging	Automatic when commits are pushed or merged into `staging`
`main`	Production	Manual from GitHub Actions
`automation`	Cross-environment refresh workflow	Used for `refresh-environment`; not part of normal app deployment

The manual production deployment is intentional. Production-ready changes can be merged into main without immediately changing the production site. The production deployment is started later from the GitHub Actions tab when the timing is approved.

The automation branch exists so refresh-environment can connect to production for exports and then to the target environment for imports without loosening the branch-to-environment protections on normal deployment workflows. Normal app deployment remains tied to dev, staging, and main.

For the full promotion model, see Dev, Staging, and Main Git Workflow. For deployment configuration, GitHub Environments, Tailscale, SSH, rsync, and .deployignore behavior, see Deployment Pipelines.

Environments¶

Environment status last verified: July 31, 2026.

Environment	Operational Notes
Production	Runs from the production deployment target. Code on `main` is production-ready, but production is deployed manually.
Staging	Receives automatic deployments from the `staging` branch. The staging server uses a static public IP address, and Cloudflare DNS has been updated to point to that static address.
Development	Receives automatic deployments from the `dev` branch. The development server is fully configured, site files and database are in place, and deployments to development are working. The development server uses a static public IP address, and Cloudflare DNS has been updated to point to that static address.

Do not document public IP addresses, private IP addresses, secret values, keys, or unnecessary host details in OSKB. Record where configuration is managed and what it affects.

Deployment Configuration¶

Each NASPO ValuePoint environment has a matching GitHub Environment. The GitHub Environment stores deployment variables and secrets for that environment and restricts deployment to the associated Git branch.

Credentials and secret material are managed in Keeper and GitHub Environment secrets. Do not copy credential values into this knowledge base.

Deployment deletion behavior

Deployments use rsync --delete, subject to .deployignore. A file under the deployment path that is not tracked in Git may be removed during deployment unless it is protected by the active .deployignore file.

.deployignore is separate from .gitignore. Confirm the active application repository's .deployignore before relying on server-only files remaining in place after deployment.

Integrations and Administration¶

Transactional Mail¶

Status last verified August 12, 2026:

NASPO Secure Mail 0.1.0 is active in production.
Development uses gateway capture mode.
Staging uses gateway redirect mode and has been verified with controlled real delivery to the configured redirect recipient.
Production uses gateway send mode and has been verified with controlled real delivery.
WP Mail SMTP is inactive and retained temporarily as a rollback path during the proof window.

Production gateway policy last verified August 12, 2026:

Setting	Value
Gateway identity	`nvp-prod`
Environment	`prod`
Status	`active`
Allowed From	`webmaster@naspo.org`
Default From	`NASPO ValuePoint`, `webmaster@naspo.org`
Delivery mode	`send`
SendGrid sandbox	`false`
Max recipients	`50`
Max payload	`10 MiB`
Rate limit	`60` per minute, `600` per hour

Production WordPress account-reset mail was tested successfully through NASPO Secure Mail on August 12, 2026. Gateway tail showed nvp-prod mail_sent, SendGrid showed delivery, and the message was received.

Do not remove WP Mail SMTP from the repository or deployment workflow until NASPO Secure Mail has completed the proof period and the rollback path is no longer needed.

In Progress¶

Refresh Environments Workflow¶

The Refresh Environments workflow is currently in development. Its final scope, triggers, and handling of site files and databases have not yet been documented. Update this section after the workflow has been completed and validated.

Documentation to Capture¶

Continue adding validated information about:

Search and indexing services
Analytics, pixels, and tag management
SEO and accessibility
Known issues and recovery procedures