Storage and Release Artifacts
Understand the difference between immutable deployment artifacts and application data.
Storage and Release Artifacts#
Each successful build produces the artifact used for that release. Release artifacts are managed by NexHost and are separate from the source archive or repository you uploaded.
Release artifacts#
Static Sites publish the configured output directory. Runtime services use the prepared build and startup configuration for their release. Treat artifacts as deployment outputs: make source changes in your repository or archive, then create a new release rather than editing a previous artifact.
Application data#
Do not rely on a deployment artifact as mutable application storage. Store durable relational data in Postgres or use the data service appropriate to the application. Keep backups and data-retention decisions under your team’s control.
Secrets and uploads#
Keep secrets in Environment Variables, not in source or release files. Decide how user uploads and generated media will be stored before deployment; a deployment release can change independently of that application data.