docker-node-example VS headwind

Here's a full example project where a Node app is split up between a front-end and back-end with multi-stage builds: https://github.com/nickjj/docker-node-example

Here's a walk through on how to use them https://nickjanetakis.com/blog/docker-tip-94-docker-compose-v2-and-profiles-are-the-best-thing-ever and here's an example Node project that's using profiles https://github.com/nickjj/docker-node-example.

- https://github.com/nickjj/docker-node-example

If your goal is to "learn Docker", I have around 100+ free blog posts and YouTube videos at: https://nickjanetakis.com/blog/tag/docker-tips-tricks-and-tu...

https://github.com/nickjj/docker-node-example is an up to date Node example[0] that's ready to go for development and production and sets up GitHub Actions. Its readme links to a DockerCon talk from about a year ago that covers most of the patterns used in that project and if not some of my more recent blog posts cover the rest.

It doesn't cover feature branch deployments tho, in my opinion that's unrelated to Docker.

[0]: You can replace "node" in the GitHub URL with flask, rails, django and phoenix for other example apps in other tech stacks.

A fully working example Node app that demos the above is here: https://github.com/nickjj/docker-node-example

Added the tailwind-prettier-plugin as not everyone uses headwind

Headwind is a nice addon for VS Code to sort classes automatically and warn you when using conflicting classes: https://github.com/heybourn/headwind

The one I'm using is Headwind which defines itself as:

Headwind is a nice opinionated sorter which probably can be tweaked to understand our Slim templates but as a VS Code plugin it only works inside this particular IDE. We mostly use JetBrains RubyMine in our team and also needed a CLI version.

If you are worried about property sort order (Tailwind is much more readable if you are) then you can use another tool to deal with that for you: Headwind. This VS Code extension will format your Tailwind classes on save and group them by their function, making sure everything is where you expect it.

Headwind - a VS Code extension that sorts your CSS classes on save

I can suggest taking a look at Tailwind CSS Best Practice Patterns and Robin Malfait's Good Example to get an idea of how that would look like. For consistency, I can also recommend having a convention for class ordering or using headwind as an opinionated class sorter.

There's Headwind CSS, which orders classes predictably. But it doesn't move them to separate lines. This could be a config option if you're willing to write a pull request.

https://github.com/heybourn/headwind