Help for owners
The settings and passwords my app needs exist only on one developer's laptop
Short answer
Apps need settings such as database addresses and keys for outside services, often kept in an environment file. If that file exists only on one laptop, a lost device or a departed developer can stop deployments. Record where each secret is used, store them in a company-owned password manager or secrets service, and rotate them.
Does this sound like your situation?
- Only one developer can deploy the app, because only their machine has the settings.
- When that person is away or leaves, nobody can release a fix.
- Keys and passwords were sent by chat or email.
- A new developer cannot run the app without asking for a file.
- Nobody can list which outside services the app logs in to.
Why does this happen?
Secrets are kept out of the code on purpose
Passwords and keys should not be stored in the shared code, so they live in a separate file. If nobody builds a shared place for that file, it stays on whichever machine created it.
The first developer set it up and nobody wrote it down
Early setup is quick and informal. The file is copied by chat to the next person, and the original knowledge is never documented.
Accounts are in the developer's name
Keys are often created in a developer's own account at a hosting, email or payment service. When they leave, the company does not control the account behind the key.
Secrets are shared in unsafe ways
Keys in chat messages, emails or shared spreadsheets stay readable for a long time and cannot be taken back.
What can I do about it today?
- Ask for a list of secrets, not their valuesAsk your developer for a list of the settings the app needs and which service each one belongs to. Do not ask anyone to send the values by chat or email.
- Find who owns each accountFor each outside service, check whose name and email the account is under. Move any that belong to individuals to a company email you control.
- Set up a company password managerChoose a password manager for the business and make sure you are an administrator.
- Do not copy the file aroundAvoid sending the settings file to others while you sort this out. Each extra copy is another place a secret can leak from.
- Keep the laptop safeAsk that the machine has a screen lock and disk encryption and is not left unattended. Do not delete anything from it.
When should I bring someone in?
- The developer who holds the file has left or stopped responding.
- A secret has been shared in a public place such as a code repository or a chat group.
- Nobody can say which accounts the app depends on.
How do I handle it?
- Map every settingI read how the app starts and list each setting, what it unlocks and who owns that account.
- Move secrets to a shared, controlled placeThey go into a company-owned secrets store or password manager, with named people having access.
- Rotate the ones that were exposedKeys that were shared by chat or stored on a laptop are replaced with new ones, in an order that avoids downtime.
- Make setup reproducibleA template file lists the names of the settings without values, so a new person can run the app with the right access.
- Document who can do whatA short page says where settings live, who can change them and how to replace a key.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
What is an environment file?
A small file next to the app that holds settings such as database address and keys for outside services. It is kept out of the shared code on purpose.
Is it safe to email me the file?
No. Email and chat keep copies. Use a password manager with access limited to named people.
Do I have to change all my passwords?
Not necessarily. Anything that was shared in unsafe places or tied to someone who left should be replaced. The list of secrets shows which ones.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.