Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
dockerfiler vs goodpractice
A side-by-side editorial comparison of dockerfiler and goodpractice — release velocity, themes, recent moves, and the top alternatives to consider.
dockerfiler vs goodpractice: at a glance
What is dockerfiler?
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
After two years of small parameter additions, ThinkR shipped a 1.0.0 that changes the tool's output for every existing user. The vendored copy of renv is gone, generated images default to multi-arch rocker/r-ver running as a non-root rstudio user, and packages come from Posit Public Package Manager binaries instead of a source CRAN mirror.
What is goodpractice?
The R package-quality checker returns from CRAN limbo with checks you can select by category.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
dockerfiler vs goodpractice: editorial side-by-side
dockerfiler
0.0INFRA · APIS
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
◆ Current state
After two years of small parameter additions, ThinkR shipped a 1.0.0 that changes the tool's output for every existing user. The vendored copy of renv is gone, generated images default to multi-arch rocker/r-ver running as a non-root rstudio user, and packages come from Posit Public Package Manager binaries instead of a source CRAN mirror.
◆ Where it's heading
The package is being hardened rather than extended. Every user-supplied value that reaches a Dockerfile shell context is validated at function entry, and two long-standing code-injection paths — a crafted renv.lock version string and DCF continuation lines in DESCRIPTION fields — were closed after an internal audit. The new parameters point at production image builds: github_pat via BuildKit secret mounts, strict_install turning install warnings into build failures, and a configurable renv cache path.
◆ Prediction
With the injection surface closed and the defaults flipped, the next releases are more likely to be compatibility work against renv and pak than new generators.
goodpractice
0.0INFRA · APIS
The R package-quality checker returns from CRAN limbo with checks you can select by category.
◆ Current state
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
◆ Where it's heading
The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.
◆ Prediction
With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.
Alternatives to dockerfiler and goodpractice
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either dockerfiler or goodpractice.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
packrat
R's old dependency manager now runs on a vendored copy of its own successor.
See all dockerfiler alternatives → · See all goodpractice alternatives →
Recent activity from dockerfiler and goodpractice
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agogoodpracticeChecks organized into 16 selectable groups with presets ⚡
- 3mo agodockerfilerMulti-arch, non-root defaults and a closed injection surface ⚡
- 2y agodockerfilerSystem-requirement detection moves to pak::pkg_sysreqs()
- 2y agogoodpracticerOpenSci takes over maintenance, package restored to CRAN
- 2y agodockerfilerDockerfile generation from renv.lock, and parsing back
- 3y agodockerfilerGraceful failure without network access
- 4y agogoodpracticeConfigurable cyclomatic complexity limit and output length
- 5y agogoodpracticePackage logo added
Frequently asked questions
What is the difference between dockerfiler and goodpractice?
They serve adjacent needs but don't currently overlap on shipped themes. dockerfiler and goodpractice are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is dockerfiler better than goodpractice?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dockerfiler and goodpractice are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to dockerfiler?
Top dockerfiler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dockerfiler alternatives" section above for the current picks, or visit /alternatives/dockerfiler for the full list with editorial commentary on each.
What are the best alternatives to goodpractice?
Top goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.