3 ms·
If it needs access to the production DB, I use regular ol' authentication/authorization for pages built into the site. If you're not me and you access it, you
by patio11 16y ago
If it needs access to the production DB, I use regular ol' authentication/authorization for pages built into the site. If you're not me and you access it, you get kicked out. (There are a variety of reasons why one would not choose this approach for extraordinarily sensitive setups, but it is quick to implement and adequate for teaching tools.)
Things typically get promoted to my admin panels after I get sick of doing them manually on another site (e.g. log into Paypal for refunds or parse-and-crunch a CSV repeatedly).
I keep all my notes either in paper or Dropbox. If I had a team, I'd have a wiki running on a physically separate machine. (Putting software with that sort of risk profile on a machine with production data scares me.)
- albahk 16y agoGood point about waiting for things to really annoy you before promoting to the admin panel. I'm wary of spending too much time on this given the userbase is 1. When you say auth access, do you mean a .htaccess password over SSL? I had not thought of such a simple solution.
- arianb 16y agoI generally use HTTP Digest Authentication for personal projects - since I don't really require fancy login boxes, and it's really trivial to implement.