The family portal looked dead, replacement CMS options started getting judged, and then the whole “incident” turned out to be a forgotten login.
Original work date
early March
The problem
The Family Portal was running on Ghost and appeared broken. Instead of starting with boring triage, the problem immediately felt bigger than it was. WordPress got dragged back into the conversation. Concrete CMS got judged. The whole platform was briefly on trial.
The environment
- App: Ghost
- Host:
- Cluster / namespace:
- Version:
- Relevant config:
What failed
Then the boring answer showed up. Ghost was not destroyed. The container was fine. The login credentials were the problem.
The fix
Once the password was reset inside the container, the “outage” was basically over
Final state
What I learned
Before replacing the whole platform, make sure the platform is actually broken.
Useful commands / config
paste commands here