NEUAGEOPS

Asset Hub — Setup Guide

Everything you need to deploy, maintain, and lock down the self-updating hub at neuage.health.

The files Deploy Set as homepage How it stays current Customize Password protection Troubleshooting

AThe files

index.php — the hub itself. Self-updating: scans public_html on every load.
htaccess-sample.txt — server config. You'll rename this to .htaccess.
This guide — keep it in the repo or your ops docs; it's set to noindex.

1Upload

In Hostinger hPanel → File Manager, open public_html.
Upload index.php into that folder.
If you previously uploaded the static index.html, delete it so there's no confusion about which loads.
While you're there, delete the stray {ops,affiliate,branding,assets} folder — it's an accidental leftover and is already hidden by the hub anyway.

2Make it the homepage

Your server currently has a default.php. To guarantee the hub loads at neuage.health, add an .htaccess that lists index.php first.

Upload htaccess-sample.txt to public_html.
Rename it to exactly .htaccess (with the leading dot, no extension).

It contains this line, which does the work:

DirectoryIndex index.php index.html default.php

3How it stays current

You don't maintain the list by hand. On every visit the hub scans public_html and:

Shows your nine curated sections first, with their custom titles and descriptions.
Adds any new folder or file automatically as a card under the Other category — with its size (files) or item count (folders) and last-modified date.
Hides the noise: the script itself, index.html, default.php, .htaccess, all dotfiles, and the stray brace folder.

Page vs. File listing labels

Each folder card is tagged so you know what opens when you click it:

Page File listing File

Page — the folder has its own index.html/index.php, so it opens a finished page.
File listing — the folder has no index, so it opens a raw browsable directory of files.
File — the card links directly to a single file (e.g. a guide or PDF).

"File listing" depends on a server setting. By default Hostinger allows directory browsing, so those folders show a file list. If directory listing is turned off (Options -Indexes), those same folders return a 403 instead. The sample .htaccess leaves listings on; flip the commented line if you'd rather lock raw folders down.

4Customize

Two clearly-commented arrays at the top of index.php are all you ever touch.

Rename or re-describe a section

Edit $CURATED — each line is 'folder' => ['Title','Description','Category','icon']. Order here = display order.

$CURATED = [
  // folder/file name        Title              Description                       Category     icon
  'ops'         => ['Operations Hub', 'Internal ops home — SOPs & processes.', 'Operations', 'gear'],
  'branding'    => ['Branding',       'Logos, color system, typography.',        'Brand',      'palette'],
  // …add a new top-priority section the same way
];

Available icon keys: gear chat users chart palette folderopen image check doc folder file.

Hide something from the hub

Add its exact name to $IGNORE. Dotfiles are hidden automatically.

$IGNORE = [
  $SELF, 'index.html', 'index.php', 'default.php', '.htaccess',
  'cgi-bin', '.well-known',
  '{ops,affiliate,branding,assets}',
  // 'staging', 'admin',  ← add anything else to hide
];

5Password protection

Yes — and the right method protects not just the hub page but every asset folder behind it. Use HTTP Basic Auth at the directory level (not a PHP login, which would only guard index.php and leave the raw folders reachable directly).

Easiest — hPanel (recommended)

hPanel → Files → Directory Privacy (sometimes "Password Protect Directories").
Pick the folder to lock (see the note below about which folder).
Turn protection on, set a username and password, save.

Hostinger writes the .htaccess rules and the encrypted .htpasswd for you. Everything in that folder — the hub page and the asset directories — then prompts for login.

Manual — .htaccess Basic Auth

If you prefer to do it yourself, uncomment this block in your .htaccess and create a .htpasswd file (hPanel can generate the hashed line, or use the htpasswd tool). AuthUserFile must be the absolute server path.

AuthType Basic
AuthName "NEUAGE OPS — Restricted"
AuthUserFile /home/uXXXXXXXX/domains/neuage.health/public_html/.htpasswd
Require valid-user

Which folder you protect matters. Locking public_html protects everything on neuage.health — including any public-facing pages like /affiliate. If some sections need to stay public, don't lock the whole root. Instead, move the internal hub and its private assets into a subfolder (e.g. neuage.health/hub/) and apply Directory Privacy to that folder only, leaving public pages reachable at the root.

Basic Auth sends credentials over the connection, so make sure the site is served over HTTPS (Hostinger provides free SSL — enable it in hPanel if it isn't already).

6Troubleshooting

Old page still shows. The .htaccess isn't in place or isn't named exactly .htaccess. Re-check step 2, then hard-refresh.
A new folder didn't appear. It may be named like something in $IGNORE, or it starts with a dot. Otherwise just reload — there's no cache to clear.
A card opens a file list you didn't expect. That folder has no index file — add one, or accept the "File listing" behavior, or turn listings off (see section 3).
Login prompt won't accept the password. The AuthUserFile path is almost always the culprit — it must be the absolute server path to .htpasswd, which you can copy from hPanel's File Manager.