Overview / Repositories

GitHub Repositories

Account Agiliotti (a personal account, not an org) holds 5 private repos. Two of the names are misleading — here's what each actually contains.

Two things to know up front

1) The repo called redesigned-spoon-Dashboard is actually the entire Laravel backend, not a dashboard frontend. 2) Three separate repos (HSF-Code, Hatch-Front-End-Code, HSFE) each contain the same mobile app — they are duplicates, not different projects.

1. redesigned-spoon-Dashboard — the Laravel backend

Laravel 9 PHP ^8.0.2 419 MB last push 2026-04-14 most important repo

This is the backend that powers both the mobile API and the admin dashboard — a single Laravel application. The actual code is double-nested inside hatch-social-backend-master/hatch-social-backend-master/ (a zip extracted into a zip), which is why the name and structure are confusing.

Routes	`routes/api.php` (267 lines, the mobile API) · `routes/web.php` (246 lines, the dashboard UI) · `channels.php` (broadcasting)
Controllers	~160 PHP controllers under `app/`
Key packages	Sanctum (auth), Cashier + `stripe/stripe-php` (payments), `kreait/firebase-php` (Firebase), `boogiefromzk/agora-token` (Agora calls), `pusher/pusher-php-server` (real-time), `twilio/sdk` (SMS), `google/apiclient`, `barryvdh/laravel-dompdf` (PDFs), `unisharp/laravel-filemanager`
Deployed as	`api.hatch.social` and `dash.hatch.social` on the production droplet (see Architecture)

Repo hygiene problems

406 MB of storage/ and 254 MB of public/ are committed, including 171 MB of user uploads under public/uploads — this is why the repo is 419 MB. Build artifacts and uploaded media should not be in git.
Two database dumps are committed under public/ (web-accessible). See Databases.
storage/app/google-services.json (Firebase service config) is committed.
Good news: no real .env is committed — only .env.example.

2–4. The mobile app — three copies of one React Native project

React Native 0.78.2 React 19 app id com.hatchsocial 79 dependencies

All three repos build the same app — internal name hatchSocial, display name "hatchSocial". It is a single React Native codebase that produces both the iPhone (ios/) and Android (android/) apps. Stack highlights: React Navigation 7, Redux, @react-native-firebase, @stripe/stripe-react-native, react-native-agora (video/audio), axios.

Repo	Last commit	SRC files	Verdict
`HSF-Code`	2025-12-28 ("4.1")	354	Newest — treat as canonical
`HSFE`	2025-12-27	354	Duplicate (code nested in a `Hatch-Social-Updated-main/` subfolder)
`Hatch-Front-End-Code`	2025-12-26	354	Duplicate — `package.json` & `SRC/` byte-identical to HSF-Code

Confirmed by diffing: HSF-Code and Hatch-Front-End-Code have identical package.json and identical SRC/ file lists. HSFE is the same app with an extra wrapping folder. You should pick one (HSF-Code) as the single source of truth and archive the other two to avoid editing the wrong copy.

Where the app points its API

In SRC/Config/index.js the active backend URL is:

export const baseUrl = 'https://hatch-social.cstmpanel.com';
// commented-out history:
//   https://hatch-social.ad-wize.net
//   https://trusting-brown.67-225-179-38.plesk.page   (Plesk)
//   https://c248-103-138-50-45.ngrok-free.app          (ngrok tunnel)

The commented-out URLs show the backend has moved across several hosts (an ad-wize domain, a Plesk server, an ngrok dev tunnel). The current target hatch-social.cstmpanel.com is not one of your two servers — see Findings.

iOS bundle identifier is still a placeholder

The Xcode project ships with PRODUCT_BUNDLE_IDENTIFIER = org.reactjs.native.example.$(PRODUCT_NAME...) — the React Native template default. For App Store builds this needs to be a real identifier (e.g. com.hatchsocial, which Android already uses). android/app/google-services.json is also committed.

5. HSB-Code — empty stub

2 KBno application code

"HSB" presumably means "Hatch Social Backend," but the repo contains only a one-line README.md and a GitHub Actions workflow named "Ultimate Sync Solution" (sync-to-client.yml) that mirror-pushes a source repo into this one using a SYNC_TOKEN secret. There is no backend code here — the real backend is in redesigned-spoon-Dashboard. This repo can be ignored or repurposed.

Summary & recommendation

What you have	Where it really is	Action
Backend (API + dashboard)	`redesigned-spoon-Dashboard`	Rename to something obvious; un-nest; purge committed uploads/dumps from history
Mobile app (iOS + Android)	`HSF-Code` (+ 2 duplicates)	Make `HSF-Code` canonical; archive `HSFE` & `Hatch-Front-End-Code`
"Backend" stub	`HSB-Code`	Empty — ignore or delete

All five repos were cloned (read-only, shallow) and inspected on 2026-06-08. Clones are stored privately on this host under /sites/hatch/_src and are not served publicly.