Cloudron Forum

andreasdueren

@creative567145 Yes this was an upstream change I needed to implement. Unfortunately the only good way to do that is to create a backup, uninstall, install fresh with OIDC and then roll back your to your old backup

timconsidine

@marcusquinn nice work

marcusquinn

I've packaged LibreCrawl (MIT), a self-hosted website crawler for SEO audits, as a Cloudron community app.

It crawls sites from your server and shows status codes, titles, meta descriptions, headings, structured data, issues, internal and external links and a site-structure graph. Crawls are saved, reloadable and exportable (CSV, Excel, JSON, XML), and a REST API lets other tools start crawls and fetch results.

Install (Cloudron 9.1 or later): from Community Apps, or add this versions URL under Community apps in your dashboard settings, or run:

cloudron install --versions-url https://raw.githubusercontent.com/marcusquinn/cloudron-librecrawl-app/main/CloudronVersions.json --location librecrawl

Sign in as admin with the generated password from /app/data/admin-password (the post-install note shows how), then change it.

What the package does

Signed-in use only. Registration and guest access are off, and modes that skip sign-in stop the app at startup. Create accounts with librecrawl-user add in the app's Terminal, one per person or per site.
Users, settings, and crawls live in SQLite under /app/data and are backed up. The database is snapshotted before a new LibreCrawl version migrates it.
A daily task removes finished crawls older than 90 days (CRAWL_RETENTION_DAYS in /app/data/env).
Memory defaults to 2 GiB. On a test, a 5,000-page HTML crawl peaked at 1.16 GiB. Allow 4 GiB for several large crawls in the same hour, or for JavaScript rendering beyond small sites.
Chromium rendering is available but off by default. tini runs as PID 1 so Chromium's helper processes are reaped.

Please read before giving anyone an account:

LibreCrawl has no filter for private addresses.

Anyone who can sign in can make the server request any address it can reach, including other apps on your Cloudron and your private network.

Only create accounts for people and sites you trust. An upstream pull request proposes a guard; it isn't merged yet.

Upstream behaviour worth knowing

The crawl delay only slows JavaScript crawls. HTML crawls are limited only by concurrency, plus up to five HEAD checks at a time.
JavaScript crawls send their own user agent (jsUserAgent). Set both if a firewall allowlists your crawler.
The page limit counts fetched pages, but results also list every image and external link that was only HEAD-checked.
A crawl session idle for an hour is dropped, even mid-crawl. API clients should keep polling or use the saved-crawl endpoints.

Source, docs and issues: https://github.com/marcusquinn/cloudron-librecrawl-app.

It's packaged independently of the LibreCrawl project.

Feedback welcome, especially memory figures from larger or JavaScript-heavy sites.

Website & screenshots

https://librecrawl.com/

timconsidine

@marcusquinn said:

I'm just happy to be unconstrained to create what we need, and share the joy for the wisdom of the crowd to be more important than any one of us.

well said

marcusquinn

Whatever you guys want is fine by me.

I generally keep up with notifications from here regardless, so if anyone has any issues with the apps packaged, just reply on the threads discussing them or log an issue in github.

If Cloudron does or doesn't also want to adopt any apps, also fine.

Needs and preferences are what they are. I'm just happy to be unconstrained to create what we need, and share the joy for the wisdom of the crowd to be more important than any one of us.

timconsidine

Heads up for OpenCode users (opencode-web and opencode-worker) :

authors (anomalyco) are working on v2 which has some significant differences to v1
v1 is still shown as the main release channel but it's likely to switch at some point, possibly soon.

I will package for v2 when I feel the time is right.

To avoid breaking changes, I am leaning towards making v2 as separate apps, allowing continued use of v1 apps without breaking them, and eventually retire them when upstream indicates no further updates coming.

marcusquinn

@huehner thanks — just discovered that shortly after posting. We're all good then, and safe from the future

fbartels

Yes, i guess it should be phrased the other way around "if your app needs PHP, node or pip use the dedicated base images for these platforms"

timconsidine

In https://docs.cloudron.io/packaging/cheat-sheet, there is this comment :

Do not put PHP, Node, or pip/venv back into cloudron/base.

It reads strangely to me, almost a note for cloudron base image builders, rather than for app packagers. Maybe the emphasis is intended to be "into cloudron/base".

Packagers using this "slim" package will likely need to add some language components.

Can this document content be clarified ?

Out of interest, I tested the main base image variants with a 'hello world' page :

cloudron-base6:0.0.1 size: 1.19GB
cloudron/node-base:24-20260920 size: 1.46GB
cloudron/python-base:3.14-20260920 size: 1.26GB
cloudron/php-base:8.5-20260920 size: 1.54GB

msbt

much obliged, thanks @james and @codev

Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Cloudron Forum

AppDev

Posts

Member List