4 ms·
Will that 10s install be anything like production-ready? As a sysadmin, one of my pet peeves is tools where the "install process" is "run this executable and it
by jcrawfordor 10y ago
Will that 10s install be anything like production-ready? As a sysadmin, one of my pet peeves is tools where the "install process" is "run this executable and it's a webserver," because for me to put a tool in a place where my teams rely on it I'm almost always looking at SSL termination, LDAP auth, not to mention putting it under systemd or something so that it'll get restarted if the host system does, and the fact that I'll inevitably be deploying via automation.
The takeaway is that I hope the easy install process won't only be easy in the absolute minimal case. Ideally I'd love to get RPM and DEB packages and example configuration snippets for a frontend web server. At the very minimum, distribute in a form that is amenable to deployment to Ansible/Puppet/etc (no 'setup wizard' please!) and placement behind a reverse proxy.
- alex-m 10y agoGood point. It's definitely not going to be 10 seconds for a more serious installation you described. But it will be faster than anything else. You download the binary or compile it yourself, set the path to your repositories, and you are done. No wizards! I haven't thought about RPM and DEB packages yet, but they will be definitely supported if that's what people want.
- bb88 10y agoThese days I won't run anything more complex than an executable that isn't in a docker container. I think that a lot of people feel this way too. It's just so much easier in the end.
- Twirrim 10y agoHonestly, from my sysadmin perspective, I don't give much of a damn about installation time, provided it's not absurd (e.g. picking a figure out of thin air 30 minutes?) What I care about around install, is can I do it in a automatable fashion, including all configuration. I don't want to have to do anything by hand after the first exploration and evaluation work!
- friendzis 10y agoI must be a terrible sysadmin, because I have never in my life have deployed anything in under 30 minutes, unless I have already deployed several instances and have it scripted. If I can get something up and running [and actually doing what the tool is intended to do] in my infrastructure in a day's amount of work I call it huge success.
- 234dd57d2c8dba 10y agoRight? Jenkins is a perfect example of how NOT to do installations and configurations.
- willejs 10y agoFrom the authors github, I presume its written in go. So its just going to be a binary with a config file. Thats great, and easy to deploy! I get your point, nothing is a 'production ready' deployment in 10 seconds. But, i think the author means it will 'just work' for most people. In reality, our version of production ready wouldnt take more than an our max to deploy that to ecs/kubernetes.