Hacker News new | ask | show | jobs
by mcos 4989 days ago
"It's built with simplicity and power in mind -- The simplicity for a non-technical user to be given the reigns to deploy from a master branch to a "staging" server… or to a production server after any tests have passed."

I'm sure there's good reasoning behind wanting to give a non-technical user the rights to deploy code to servers, but I'm afraid I can't seem to conceive of them right now. Can you elaborate why you would want someone without the requisite technical skills deploying code?
1 comments
wahnfrieden 4989 days ago
Copy changes. "Knobs" (configuration parameter changes that affect product-level behavior, things a product manager could decide about.)

Sure you can abstract copy from your codebase or markup, but that's not trivial or necessarily a benefit.

link
yakshaving 4989 days ago
Exactly - Changing copy via a tool like the now-defunct but open sourced CopyCopter, small tweaks here and there could completely be within the scope for a non-technical analyst to deploy once deemed ready.

It's also nice for a consultant who manages many clients, which we included in the copy in other places.

link
trhtrsh 4989 days ago
Why on earth would you put your copy and configuration in your code base, and not in a CMS (for copy) or a database (for configuration)?
link
wahnfrieden 4989 days ago
Because that's a lot of extra work and our product manager at our small startup is competent enough to change e.g. the number of a constant in a knobs.py without wrecking things.
link