Skip to content

Conversation

@melton-jason
Copy link
Contributor

This feature brings the "Dockerize" support once only enjoyed by the primary Specify 7 repository to the Web Asset Server.
Primarily:

Testing Instructions:

  • Re-run all jobs for the Dockerize GitHub Workflow
    • (or optionally) push a branch based on these changes
  • Inspect the runtime logs of all Actions within the Dockerize GitHub Workflow
  • Once complete, ensure the corresponding branch on Docker Hub has been updated

@grantfitzsimmons
Copy link
Member

  • If desired, we can now version the Web Asset Server with the same scheme of the Specify 7 releases (vX, vX.Y, vX.Y.Z, etc.)

I'd like versioning to be independent

@melton-jason
Copy link
Contributor Author

melton-jason commented Oct 7, 2025

  • If desired, we can now version the Web Asset Server with the same scheme of the Specify 7 releases (vX, vX.Y, vX.Y.Z, etc.)

I'd like versioning to be independent

#41 (comment)

Sorry for any confusion! By sharing the same scheme, I meant only that the versioning process/function is the same. That is, if we create a tag in this repository we can expect the same pushed tags on the specify-asset-service as if we had tagged the Specify 7 repository with the same tag name.

Versioning is independent for each service. If we have a tag v2.0.0 for the Web Asset Server, it is independent from all other services (Specify 7, Webportal, Report Runner, etc.).

For example, if we:

  • Tag v7.12.0 on the Specify 7 repository
    • All other services (repositories) will not have any latest v7, v7.12, or v7.12.0 tags pushed or modified
  • Tag v2.0.0 on this repository (Web Asset Server)
    • The corresponding latest, v2, v2.0, and v2.0.0 docker images will be pushed to Docker Hub only for the specify-asset-service base image

@grantfitzsimmons grantfitzsimmons merged commit 67cbd4d into master Nov 14, 2025
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants