Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
dockerfiler vs webfakes
A side-by-side editorial comparison of dockerfiler and webfakes — release velocity, themes, recent moves, and the top alternatives to consider.
dockerfiler vs webfakes: 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 webfakes?
A fake web server for tests that keeps closing the gap with the real thing.
webfakes runs a real HTTP server inside R tests so packages can exercise network code without hitting the internet. Its releases follow a consistent logic: find a class of behaviour that only the real internet could reproduce, then implement it locally. HTTPS arrived in 1.4.0; before that the httpbin clone reached full parity with the Python original, and a fake git HTTP server landed alongside CGI middleware. The most recent release, 1.5.0, is about the server's own rough edges — keep-alive timeouts, locale-independent HTTP date parsing, and trailing-slash route matching.
dockerfiler vs webfakes: 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.
webfakes
0.0INFRA · APIS
A fake web server for tests that keeps closing the gap with the real thing.
◆ Current state
webfakes runs a real HTTP server inside R tests so packages can exercise network code without hitting the internet. Its releases follow a consistent logic: find a class of behaviour that only the real internet could reproduce, then implement it locally. HTTPS arrived in 1.4.0; before that the httpbin clone reached full parity with the Python original, and a fake git HTTP server landed alongside CGI middleware. The most recent release, 1.5.0, is about the server's own rough edges — keep-alive timeouts, locale-independent HTTP date parsing, and trailing-slash route matching.
◆ Where it's heading
The package is converging on being indistinguishable from a real server for test purposes, which is the only way it stays useful — every unsupported protocol feature is a piece of code someone cannot test offline. The remaining work has visibly shifted from missing endpoints to correctness details: date header parsing under unusual locales, keep-alive tuning, request body handling across content types.
◆ Prediction
Expect continued fidelity work against real-server behaviour rather than new app types, with HTTP/2 or authentication schemes the most plausible next gaps given the direction HTTPS opened. The entries do not indicate a specific planned feature.
Alternatives to dockerfiler and webfakes
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 webfakes.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
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.
See all dockerfiler alternatives → · See all webfakes alternatives →
Recent activity from dockerfiler and webfakes
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agowebfakesKeep-alive tuning, locale-safe HTTP dates, looser routes
- 3mo agodockerfilerMulti-arch, non-root defaults and a closed injection surface ⚡
- 1y agowebfakesHTTPS support lands in the fake server ⚡
- 1y agowebfakesNew decode_url server option
- 2y agodockerfilerSystem-requirement detection moves to pak::pkg_sysreqs()
- 2y agowebfakesAdds a fake git HTTP server and CGI middleware
- 2y agodockerfilerDockerfile generation from renv.lock, and parsing back
- 2y agowebfakesFixes tmpl_glue() on affected macOS builds
- 3y agowebfakeshttpbin clone reaches parity with the Python original
- 3y agodockerfilerGraceful failure without network access
Frequently asked questions
What is the difference between dockerfiler and webfakes?
They serve adjacent needs but don't currently overlap on shipped themes. dockerfiler and webfakes 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 webfakes?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dockerfiler and webfakes 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 webfakes?
Top webfakes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "webfakes alternatives" section above for the current picks, or visit /alternatives/webfakes for the full list with editorial commentary on each.