Skip to main content
Version: Next

Release Artifact Policy

Before doing anything else, confirm that support gave you the backend school bundle for the site.

Backend school bundle​

This is the standard production artifact.

It comes from the backend release workflow and is the right choice when you need the full on-prem school appliance flow.

Typical contents:

  • school-bundle-release-<releaseVersion>/
  • school-bundle-release-<releaseVersion>.tar.gz
  • school-bundle-release-<releaseVersion>.tar.gz.sha256.json
  • optional trusted signing public key

Use this artifact when you need:

  • backend + frontend deployed together as one supported stack
  • packaged migrations and health checks
  • nginx reverse proxy in front of the services
  • bundle-level checksum and optional signature verification

Frontend deployment pack​

This is a support-only exception artifact.

Typical contents:

  • school-deployment-pack-<releaseVersion>/
  • school-deployment-pack-<releaseVersion>.tar.gz
  • school-deployment-pack-<releaseVersion>.tar.gz.sha256.json
  • optional signature files and trusted signing public key

Use this artifact only when support explicitly instructs the site to deploy from the frontend release handoff.

Normal school installs and normal school updates should not start here.

Required inputs for the standard workflow​

Have these before deployment starts:

  • the release directory or archive set provided by support
  • the checksum manifest for the archive
  • the trusted public signing key when the release is signed
  • school-specific environment values
  • network access to pull the pinned images during install or update

What is no longer part of the production workflow​

Do not treat these as the standard school deployment path anymore:

  • cloning mn-school-fe or mn-school-be directly onto the school machine
  • running raw development compose files from source checkout
  • building frontend or backend images locally on the school machine
  • copying old .env files forward without checking the packaged templates

Next step​

Continue with Deploy with the Backend School Bundle.

If support explicitly moved the site onto the frontend exception path, use Deploy with the Frontend Deployment Pack.