1,405 karma · joined December 1, 2012
Also, what's immature about Vault?
> Simple, you get the secrets very rarely: at deployment.
Do you mean writing custom scripts to get secrets? Where do you store secrets in such a scenario? What if you need to change secrets at runtime.
Vault is nice in that you can fine grain access:
- ACLs which allow some team members to be responsible for setting secrets and other team members for using them,
- temporary credentials for well known DBMSs which helps secure logs from leaks,
- PKI Management,
- temporary SSH keys.
And more. Not sure how you'd get that with a deploy time script.
Some industries legally require you to plan for the case where a cloud provider cuts you off. So sometimes you don't have a choice.
If you want to convince, do it with data and logic, not by taking away rights.
In a democracy, yes it does.
In fact, it's pretty cool that the only requirement is to stay up to date. Some companies make you pay to get upgrades, which is less secure in a way.
> It’s important to note that this change does not prevent our users from using, modifying, or providing our open source software to others — provided, however, that under the AGPL license, users have to share source code if they are modifying it and making it available to others (either as a distribution or over a network). For distributors, AGPL has the same source code sharing requirements as GPL. Those conditions are designed to encourage third parties looking to modify the software to also contribute back to the project and the community.
Unless you can deploy something like Postgresql to a FaaS. If that's doable, I'd like to read more about it.
I think that's exactly the kind of complexity arusahni was referring to. Being able to deploy a single binary with `go get` or `cargo build` without worrying about anything else is really convenient.
I guess it depends on the use case though, I use Python extensively at work and have little complaints.
People tend to use ready-made Docker containers for PHP deployment. The official PHP image has apache and fpm versions: https://hub.docker.com/_/php/
Also, teams with SRE expertise most likely use modern tech because SRE itself is a rather new way of managing infrastructure. So you'll probably be able to get your hands dirty with lots of cool tech.
Sure, shaving a few milliseconds off the load time is nice, but it's just one parameter amongst a whole bunch.
PHP has a reliable ecosystem of 3rd libraries with LTS releases. I am not aware of something like Symfony [1] for Rust or Go.
[0] https://www.indiehackers.com/podcast/007-john-onolan-of-ghos...
The thing I'm concerned about that doesn't seem addressed on your home page is security : by installing your agent on my machine, I'm basically giving you access to my machine non-stop, no ? What guarantees do I have that your agent can't be used as a backdoor ?