hadolint VS fourmolu

Hadolint Dockerfile Linter

Hadolint — Linter for your Dockerfile

[Source: Hadolint on GitHub]

One such linter is hadolint. It parses a Dockerfile and shows a warning for any errors that do not match its best practice rules.

Like hadolint: Dockerfile linter, validate inline bash, written in Haskell; Purescript, Unison, Idris languages implemented in Haskell. I recommend to check ideas behinds those projects. Especially Unison's mind-blowing something naive idea about infinite computational resources.

3. Hadolint: https://github.com/hadolint/hadolint Hadolint is a Dockerfile linter that helps you build best practice Docker images, reducing vulnerabilities in your container configurations.

To skip the "move your scripts to standalone files" step some devs don't like, consider something like https://github.com/hadolint/hadolint which runs Shellcheck over inline scripts within Containerfiles.

This is neat :)

I love going and making containers smaller and faster to build.

I don't know if it's useful for alpine, but adding a --mount=type=cache argument to the RUN command that `apk add`s might shave a few seconds off rebuilds. Probably not worth it, in your case, unless you're invalidating the cached layer often (adding or removing deps, intentionally building without layer caching to ensure you have the latest packages).

Hadolint is another tool worth checking out if you like spending time messing with Dockerfiles: https://github.com/hadolint/hadolint

With Depot, we make use of two Dockerfile linters, hadolint and a set of Dockerfile linter rules that Semgrep has written to make a bit of a smarter Dockerfile linter.

The Haskell type checker has science behind it. It is baked into the compiler. When I want to make sure that I am doing the right thing, compiling my code is usually enough. Passing -Wall and -Werror gives me good mileage. Then, I have fourmolu as a formatter, and hlint, stan and weeder as static analyzers -- or commonly referred to as linters -- which give me the courage of an MMA fighter when I am refactoring my code, regardless of the size of the change or how old the codebase is.

Great work! If I'm not mistaken, it looks like the web app is built using the new WASM backend for GHC which is a pretty nice example of a real-world application :)

In Haskell I know of at least of one successful spite driven development project: https://github.com/fourmolu/fourmolu

Here's an example of using the new WASM backend to run a Haskell library in the browser: https://github.com/fourmolu/fourmolu/pull/289