Workflows and requirements

• Build and push container image via docker buildx

  • Make sure the Actions Forgejo unit is enabled for the repository
  • Make sure the Packages Forgejo unit is enabled for the repository
  • Set vars.FORGEJO_DOMAIN_NAME to the current Forgejo's instance domain name (forge.steffo.eu)
  • Set secrets.FORGEJO_PACKAGES_TOKEN to a Forgejo Access Token with the package scope
  • Set vars.CONTAINER_IMAGE_NAME to the tag of the image to build (rookframe)

• Deploy page on a host directory

  • Make sure the Actions Forgejo unit is enabled for the repository

• Release using Poetry a new version of the Python package and deploy docs on a host directory

  • Make sure the Actions Forgejo unit is enabled for the repository
  • Make sure the Packages Forgejo unit is enabled for the repository
  • Set secrets.FORGEJO_PACKAGES_TOKEN to a Forgejo Access Token with the package scope
  • Set secrets.TEST_PYPI_TOKEN to a Test PyPI Access Token
  • Set secrets.PYPI_TOKEN to a PyPI Access Token

• Test with Pytest the Python package using Poetry

  • Make sure the Actions Forgejo unit is enabled for the repository
  • Set vars.PYTHON_PACKAGE to the name of the Python package you want to test

• Test with Cargo the Rust crate

  • Make sure the Actions Forgejo unit is enabled for the repository
  • Set secrets.FORGEJO_PACKAGES_TOKEN to a Forgejo Access Token with the package scope
  • Set secrets.CRATESIO_TOKEN to a Crates.io API token

• Release using Cargo a new version of the Rust crates in the workspace

  • Make sure the Actions Forgejo unit is enabled for the repository
  • Make sure the Packages Forgejo unit is enabled for the repository
  • Set secrets.FORGEJO_PACKAGES_TOKEN to a Forgejo Access Token with the package scope
  • Set secrets.CRATESIO_TOKEN to a Crates.io API token