Ask HN: What are the best open source tools you use in your organization? |
Ask HN: What are the best open source tools you use in your organization? |
Eclipse
Vagrant
Bash
Pmwiki
Ubuntu
Nginx
Apache
MySQL
Maven
Puppet
Prosody https://prosody.im/. Open source XMPP server with support for MUCs and all the usual XMPP stuff. Best way for teams to communicate. Extend it with plugins for your NMS and so on to get alerts in realtime.
Nagios https://www.nagios.org/. Solid (if a little fiddly) monitoring / alerting solution. Works best if you write your own plugins and use check_by_ssh instead of NRPE.
bcfg2 http://bcfg2.org/. Configuration management that makes sense. Tidy and well defined "model" for how configuration should be managed, sensible defaults and a bunch of useful powerful features.
I could go on but there are some of my all-time favourites.
Let's talk about the big packages that bring value to organisations.
ElasticSearch (And Kibana, holy shit)
MySQL
React
Ractive
Ubuntu
NGINX
Redis
We stand on the backs of giants. Yet, for some reason, corporations feel entitled to not give back. Modern computing lives by open source. Companies should be obliged to contribute similarly.
Ultimately we decided not to embrace fully yet the Phabricator CI (harbormaster/drydock) as it's been changing a lot (it's a prototype after all) and breaking frequently so we have a mix of Harbormaster and Jenkins which works very well.
We run dozens of microservices and have nearly 100 git repositories. Using `repo`, every dev has every repo in consistent (relative) path from each other. It also greatly simplifies cross-cutting changes across repositories, and staying in sync (`repo sync` updates all repos all at once.)
I also use it to manage my dotfiles: github.com/grahamc/manifest
Second: Go.CD (https://www.go.cd/) -- applying build templates to our 100 repositories has greatly simplified our management of the repositories. Using pipelines has added deep visibility into what is deployed where. I love Go.CD.
The configuration language leaves much to be desired ... but it's otherwise a fantastic piece of software. It's the most configurable, full-featured, stable, and fast proxy server I've ever worked with.
* Multiple load-balancing schemes (round robin, least conn, first, balance-on-src-ip, balance-on-uri, balance-on-uri-param, balance-on-header-value, etc)
* Advanced health-checking (out of band, script-based, remote socket based, HTTP send/expect, etc)
* Really, really easy HTTP request and response manipulation
* Generic counter support - think something like "rate limit request based on the average number of requests over the last 5 minutes that all had this random URL param". That's a contrived example, but it's easy in HAProxy.
* Fantastic ACL support. You can even dynamically update them on the fly based on a response from an upstream server, if you so wanted. Not that you should, but you could.
Honestly, you can do most things you'd need in nginx these days. But HAProxy tends to do it just as well, and in a much, much more flexible manner. And in some ways, the ACL support and terseness of the configuration allows you to write out really complex behavior in ways that would be annoying or difficult in nginx.
I'm guessing most of HN's audience would be using some form of OSS. The coverage of the comments here is large: devops tools, programming tools, libraries, productivity, etc.
Our own org uses a lot of open source components, from desktops, office suite, dev environments, server OSes, programming platforms, libraries, databases, CMSes, heck, does Android count?
More context is better.
I wish I were kidding.
Back in the "dark days", I worked for a couple of Microsoft Certified Partners. One of the things they all had in common was a "no open source" policy. I wasn't even allowed to run emacs as my editor. GPL was explicitly "evil" and even more permissive licenses were "evil enough". Hell, I had to use Visual Source Safe for version control! I would have killed for RCS, let alone something like Subversion.
And, no, not a single Linux box, or even BSD system to be found. Every single server was running Windows. I remember noticing strange network traffic one time and, lacking the tools in Windows, booted up Knoppix and diagnosed the problem -- a former employee had set up a program on an idle machine to forward the source code for our software outside the company. I couldn't tell the network admins how I had found the problem because it was more than my job was worth to admit to having used GPL software on the premises.
Of course, I don't work for companies like that any more. In fact, I'm gratified to discover that they are so rare that nobody believes they could possibly exist. In my current job, apart from 3 SaaS products (Github, Trello and Slack), every single tool I use is open source. I sometimes have to pinch myself to make sure I'm not dreaming...
We had an application from one of our system vendors that incorporated FFmpeg for playing video streams within the app. We had to go and ask them to remove FFmpeg and replace it with some other video package that IT security approved of.
This is normal for my industry. It's kind of depressing. I hear about all these nice open source tools (pandas! numpy! for a couple of examples) and have to make do with closed source equivalents I like much less (MATLAB).
I work for big monolithic company (not a software company). Most of the libraries and dev tools the engineers in my dept use are open source unfortunately the environment they run on isn't.
Previous tools that improved workflow: docker, nginx.
More recently, Drone for CI has been a quantum leap in usability for us over Jenkins. Built on top of Docker, has service container support built in, and has the unique feature of plugins-as-Docker-containers (so you can write them in any language): https://github.com/drone/drone
Ansible, ramping up with some Terraform and really loving it.