Phase 1 covers: file-based data storage, staff login (owner/staff roles), and owner-side item management (add/edit/delete services & products with photo capture and stock tracking). Customer-facing booking pages, the “My Bookings” login, and the staff bookings/payment dashboard are Phase 2–3.
No database — everything lives in JSON files under /data:
items.json — services & productsstaff.json — staff/owner loginscustomers.json, bookings.json — ready for Phase 2/3, currently unusedPhotos are saved as actual files under /uploads/items/.
/data/.htaccess blocks direct browser access to the JSON files (Apache).
Do not remove it — without it, anyone could download the customer list
by visiting the file’s URL directly.
temple-app folder contents to your public_html
(or a subfolder, if this should live at yourdomain.com/temple)./data and /uploads/items are writable by PHP
(Hostinger’s default permissions are usually fine; if you get a
“could not save” error, set both folders to permission 755 via
File Manager, or 775 if that’s not enough).https://yourdomain.com/setup.php in your browser.setup.php from the server immediately after this step.
It’s only meant to run once; leaving it up would let anyone create
their own login.https://yourdomain.com/admin/login.php and log in.There’s no “add staff” screen yet in Phase 1 — for now, ask me and I’ll either add that screen in Phase 2, or I can give you a one-off snippet to create additional staff logins directly.
wa.me links