Skip to content

Conversation

@jrasm91
Copy link
Member

@jrasm91 jrasm91 commented Sep 15, 2025

Split out the development related Dockerfile sections, since it's completely separate from the production build.

Copy link
Member

@danieldietzler danieldietzler Sep 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This breaks the github higlighting. Does vscode automatically pick up that it's still a Dockerfile?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure. You can always manually configure it though

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe calling it dev.Dockerfile should fix the highlighting

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like VS Code highlighting works fine for both conventions. Having the file named dev.Dockerfile right next to Dockerfile looks really weird to me though. I think I prefer Dockerfile.dev (next to Dockerfile), so I'll keep it as is for now at least.

@jrasm91 jrasm91 force-pushed the chore/split-dockerfile branch from 09a41c7 to e6433e5 Compare September 16, 2025 03:32
@jrasm91 jrasm91 merged commit 5fad1fd into main Sep 16, 2025
51 checks passed
@jrasm91 jrasm91 deleted the chore/split-dockerfile branch September 16, 2025 03:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants