Wallabag Camo Bundle Laravel Package

Product Decisions This Supports

• Not a general Laravel package — flag the mismatch before it reaches a roadmap. wallabag-camo-bundle is a Symfony bundle that wires the Camo image proxy into Wallabag, a self-hosted read-it-later application. It is not installable into a Laravel app via Composer in any meaningful way, and it does not provide reusable, framework-agnostic image-proxy logic. Any decision it "supports" is scoped to teams running or forking Wallabag itself.
• Privacy-preserving image delivery for read-it-later / content-ingestion products. Camo rewrites remote image URLs to HTTPS endpoints proxied by your own server. The product-relevant capabilities are: eliminating mixed-content warnings on HTTPS pages, preventing third-party image hosts from seeing your users' IPs and reading habits, and keeping archived articles rendering correctly after the origin image disappears. If your roadmap includes a "save for later," "reader mode," or "web clipping" feature, this is the class of component you'd evaluate — but you'd evaluate Camo, not this bundle.
• Build vs. buy leans heavily to "buy the proxy, skip the bundle." Camo is a standalone Go binary (originally Node) maintained upstream. Adopting the bundle means adopting Wallabag's internals, its release cadence, and its upgrade path. For a non-Wallabag product, the correct build-vs-buy line item is "run Camo (or an equivalent like imgproxy, Imaginary, or a Cloudflare Image Resizing tier)" and write ~100 lines of URL-rewriting glue yourself.
• Roadmap signal, not a roadmap input. The 1.0.0-alpha.1 tag confirms the integration is pre-stable and pre-1.0. It should not anchor a delivery commitment; it is at most a "watch" item if Wallabag compatibility is explicitly on your matrix.
• Use cases where it is genuinely load-bearing: self-hosted Wallabag instances behind a reverse proxy where mixed content breaks the reading view; operators who want image requests to terminate at their own infrastructure rather than Google/Facebook/Medium CDNs; forks that need to keep the proxy in sync with Wallabag's bundle registration and config tree.

When to Consider This Package

Consider it only when all of the following hold:

• You are running, forking, or shipping a Wallabag-based product — i.e. the host application is Symfony with Wallabag's bundle and configuration conventions, not Laravel.
• You are self-hosting and can operate a Camo instance (Go binary, HMAC key, shared secret, outbound egress).
• You need URL rewriting at the application layer rather than at the edge — for example, because articles are stored with original remote URLs and rendered dynamically.
• You are comfortable pinning to an alpha and reading Wallabag's changelog rather than this one.

Look elsewhere when:

• You are on Laravel. There is no Laravel service provider, facade, config publishing, or Blade/Debugbar integration here. Use imgproxy, glide, Intervention Image, or an edge CDN instead; expect to write your own middleware.
• You want a stable dependency. 1.0.0-alpha.1 is the second alpha. The only "release note" is a compare link — no changelog entries, no migration notes, no security review, no stated support window. Treat it as unversioned.
• You need vendor support or an SLA. Single-maintainer repository, no commercial backing evident.
• Your problem is broader than image proxying (full HTML sanitization, offline archival, tracking-pixel stripping). Camo is a narrow, single-purpose component; this bundle is narrower still.
• You can solve it at the edge. If your CDN or reverse proxy already offers image optimization and proxying, adopting an application-layer bundle adds a failure domain for no unique capability.

How to Pitch It (Stakeholders)

To executives — one line: "A tiny, pre-1.0 integration bundle for a self-hosted image proxy inside Wallabag. Not applicable to our stack; no budget or headcount implication. Recommending we track it as a reference implementation, not adopt it."

To engineering — the honest framing:

• This is a Symfony/Wallabag bundle, not a Laravel package. It registers Camo's URL-rewriting into Wallabag's container. The reusable idea is the pattern — HMAC-signed image URLs, application-layer rewrite at render time, proxy termination on your own domain — not the code.
• If we need this capability, the build is: stand up Camo or imgproxy, generate signed proxied URLs when rendering stored article HTML, and add egress allow-listing. Estimate days, not weeks, and it is independent of Wallabag.
• The current release is 1.0.0-alpha.1. The changelog is a single compare link with no described changes. We cannot assess breaking changes, security posture, or intent from it. Do not pin production to this tag.
• Recommendation: do not adopt. If privacy-preserving image proxying enters the roadmap, evaluate Camo/imgproxy directly and treat this bundle as a documented prior-art reference. Re-evaluate this package only if it reaches a non-alpha release and we take on a Wallabag dependency for some other reason.