Skip to content

Conversation

@featheredtoast
Copy link
Member

Parameterize which filename to write to (write config) and which file is copied from (dockerfile)

Allows for external apps to control which filenames the config writes to, so multiple configuration files and dockerfiles can be written to the same path without conflict.

featheredtoast added a commit to featheredtoast/discourse-launcher-extras that referenced this pull request Nov 16, 2024
use parameterized config filenames.
needed for multi container builds on docker compose

depends on discourse/launcher#2 to be merged
first for parameterization
featheredtoast added a commit to featheredtoast/discourse-launcher-extras that referenced this pull request Nov 16, 2024
use parameterized config filenames.
needed for multi container builds on docker compose

depends on discourse/launcher#2 to be merged
first for parameterization
featheredtoast added a commit to featheredtoast/discourse-launcher-extras that referenced this pull request Nov 16, 2024
use parameterized config filenames.
needed for multi container builds on docker compose

depends on discourse/launcher#2 to be merged
first for parameterization
Parameterize which filename to write to (write config) and which file is copied from (dockerfile)

Allows for external apps to control which filenames the config writes to, so
multiple configuration files and dockerfiles can be written to the same path
without conflict.
@featheredtoast featheredtoast force-pushed the parameterize-config-filename branch from 5584e18 to 7671dc1 Compare July 9, 2025 20:34
@featheredtoast featheredtoast merged commit 737e88e into main Jul 10, 2025
5 checks passed
@featheredtoast featheredtoast deleted the parameterize-config-filename branch July 10, 2025 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants