You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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:
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.The text was updated successfully, but these errors were encountered: