radrebeldeveloper.com

A sticker board of everything that has shipped. Each project is its own logo, die-cut into a shape generated from its name, dealt into a pile you can drag around.

Live: https://radrebeldeveloper.com

One static HTML file - no framework, no build step, no dependencies. The Node scripts run before deploy, never on the server.

Files

index.html	The whole page.
projects.json	What the page reads. Generated - don't hand-edit.
scan.mjs	Rebuilds the manifest, the icons and the zip from what is live.
pack.mjs	Zips the uploadable files into dist/.
deploy.sh	Uploads them to Hostinger over FTPS.
overrides.json	Hand-set names, taglines, categories. Wins over the scan.
extras.json	Projects not on a radrebeldeveloper.com subdomain.

Adding a project

A subdomain finds itself: ship it with a favicon and the next scan picks it up through certificate transparency. Anything else - another domain, or a repository with nothing deployed - goes in extras.json by hand, one line:

{ "hosts": ["clawconnected.com", "github.com/RadRebelSam/videomark"] }

A repository with no site of its own is listed wearing GitHub's mark, since it has no logo to show.

No favicon of its own = still being built. It is listed in the menu under IN PROGRESS with a grey dot, and kept off the board. A host that has stopped answering is dropped entirely.

Categories are guessed from the page copy and settled in overrides.json:

{ "rewordly": { "category": "chrome-extension" } }

chrome-extension · obsidian-plugin · saas · skill · directory · site · misc

Deploying

.github/workflows/scan.yml scans daily, commits what changed and uploads to Hostinger. It needs three secrets and, where your host differs from the defaults, two variables - all of them straight off hPanel → Files → FTP Accounts:

hPanel row	Add as
FTP IP (hostname)	secret FTP_HOST
FTP username	secret FTP_USER
Forgot your FTP password?	secret FTP_PASS
Folder to upload files	variable FTP_DIR - skip if /public_html
FTP port	variable FTP_PORT - skip if 21

The upload demands FTPS, so FTP_HOST has to be a name the server's certificate covers. Hostinger presents a *.hstgr.io certificate, so use the server hostname hPanel shows for your account (srvNNNN.hstgr.io). There is no ftp.yourdomain record, and an IP can never match a certificate. If you would rather not chase the name, set the variable FTP_INSECURE to 1: the upload stays encrypted, it just stops checking who answers.

By hand instead: node scan.mjs, then unzip dist/radrebeldeveloper.com.zip into public_html, or run ./deploy.sh ftp with those values in the environment.

Subdomains are untouched either way - they have their own document roots, and the upload only ever writes index.html, projects.json, assets/ and icons/ into the apex one.

Notes

• Icons are named after a hash of their contents, so a changed logo can never be served stale from a cache, and superseded files are pruned each scan.
• index.html carries an inline copy of the manifest so it still works opened from disk. scan.mjs rewrites it; the block is marked @generated:fallback.