Versioning: A Proposal #1

New Issue

2023-03-28T15:46:25Z

3wordchant commented

2023-03-28 15:46:25 +00:00

Currently, compose.yml uses a variable for the PHP image in all cases.

This makes it hard to crowbar into our recipe versioning scheme.

Based on recent explorations with the RStudio image, my suggestion is:

Use a specific PHP version in compose.yml (I don't care which), use that version number in the recipe version (e.g. 0.1.0+7.3)
Add an optional compose.version.yml, changing services.app.image to use PHP_VERSION (as current), update .env.sample to show how to enable that extra compose file and set the version.

@mayel, as probably this recipe's only-est user, how does that sound?

Currently, `compose.yml` uses a variable for the PHP image in all cases. This makes it hard to crowbar into our [recipe versioning scheme](https://docs.coopcloud.tech/maintainers/handbook/#how-are-recipes-versioned). Based on recent explorations with the RStudio image, my suggestion is: - Use a specific PHP version in `compose.yml` (I don't care which), use that version number in the recipe version (e.g. 0.1.0+7.3) - Add an optional `compose.version.yml`, changing `services.app.image` to use `PHP_VERSION` (as current), update `.env.sample` to show how to enable that extra compose file and set the version. @mayel, as probably this recipe's only-est user, how does that sound?

3wordchant commented

2024-10-14 20:39:06 +00:00