Sunsetting a company app without loose ends

https://is1-ssl.mzstatic.com/image/thumb/Podcasts221/v4/9c/42/96/9c429693-a57f-0804-772a-302e453cc9c8/mza_16982737108441617533.jpg/600x600bb.jpg

No Compromises

Joel Clermont and Aaron Saray

139 episodes

1 day ago

Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.

Technology

RSS

All content for No Compromises is the property of Joel Clermont and Aaron Saray and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.

Technology

Sunsetting a company app without loose ends

No Compromises

13 minutes

1 month ago

Sunsetting a company app without loose ends

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.