Skip to content

[Feature Request] Dynamic Dockerfile(s) / Compose File Setup #236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
KyleAESI opened this issue May 7, 2025 · 0 comments
Open

[Feature Request] Dynamic Dockerfile(s) / Compose File Setup #236

KyleAESI opened this issue May 7, 2025 · 0 comments

Comments

@KyleAESI
Copy link

KyleAESI commented May 7, 2025

Not sure how ambitious of a feature this would end up being but I thought it would be cool for anyone aiming to self host any of their stack to have a flag for setting up the required docker files.

Might look something like this:

apps
├── server
│   ├── src
│   ├── Dockerfile
├── web
│   ├── src
│   ├── Dockerfile
├── packages
└── .dockerignore
└── docker-compose.yml

I think the winning formula here though is creating minimal matching Dockerfile's (multi-stage, small footprint) + creating a .env workflow that allows for handling the different permutations of stack configs (i.e a docker-compose that sets up the services for a TanStack Frontend + Hono Backend and handles the default route and ports or flags) But by controlling all those aspects in the compose by ENV values we allow the user to dynamically change things as needed for custom or edge cases.

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

No branches or pull requests

1 participant