Episode 135
Sunsetting a company app without loose ends
No Compromises · Joel Clermont and Aaron Saray
September 13, 202513m 55s
Audio is streamed directly from the publisher (media.transistor.fm) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.
Show Notes
Business change and projects end, but how do you wrap up and sunset an app, especially one you've worked on for years?
In the latest episode of the No Compromises podcast, we share a practical checklist for winding down an app when the whole company is closing. From documenting services and dependencies to deciding what data to retain, we cover backups, credentials, and why deleting local copies matters for security and sanity.
- (00:00) - Sunsetting a company vs project handoff
- (02:15) - First goals: stop charges, purge data
- (03:45) - Document before shutting anything off
- (04:15) - Use README/PRODUCTION.md and password manager
- (05:45) - Decide on retaining code, DB, uploads
- (07:15) - Hunt secrets in .gitignore and dotfiles
- (09:15) - Delete local containers and repos by default
- (11:30) - Silly bit
Want peace of mind that your project is ready for whatever happens in the future. Schedule a call with us today.
Topics
LaravelPHP