Before you start, just a friendly reminder that HashiQube by default runs Nomad, Vault, and Consul on Docker. In addition, we’ll be deploying 21 job specs to Nomad. This means that we’ll need a decent amount of CPU and RAM, so Please make sure that you have enough resources allocated in your Docker desktop. For reference, I’m running an M1 Macbook Pro with 8 cores and 32 GB RAM. My Docker Desktop Resource... - Source: dev.to / over 2 years ago

When running cron jobs on Amazon EC2, you can, for example, use a secrets store like Vault. With Vault, your cron jobs can dynamically get the credentials they need. The secrets don’t get stored on the machine that’s running the cron jobs, and if you change a secret, the cron jobs will automatically receive that change. The downside of implementing a solution like Vault, however, is the overhead of managing the... - Source: dev.to / about 3 years ago

Vaultproject.io handles secrets management, so dynamic policies deal with database creds etc. "Manual" creds are stored in 1password or lastpass and added manually to Vault if it needs rebuilding. Source: over 3 years ago

It's all in the blog series, including sample configuration, but it's vaultproject.io and it allows you to do everything from managing simple secrets to auto-rotation of database credentials or even run your own KPI setup. Source: almost 4 years ago

Our team is experimenting with Hashicorp Vault as our new credentials management solution. Thanks to the offical Vault Helm Chart, we are able to get an almost production-ready vault cluster running on our Kubernetes cluster with minimal effort. - Source: dev.to / almost 4 years ago

Every coworker can check out the (private) repo and has working HTTPS without any fuss or configuration. There are projects like https://lcl.host, but they require installing stuff on the machine and/or modifying the browser trust configuration. Why has nobody just registered a similar domain like lcl.host, pointed it to 127.0.0.1, and published the private key for everyone to use? Would the CA revoke this cert?... - Source: Hacker News / 8 months ago

Hi HN! I'm part of the Anchor (https://anchor.dev/) team building lcl.host: We launched lcl.host in March as the easiest way to get HTTPS in your development environment, and today we're launching new features to make lcl.host the best local HTTPS experience for development teams. Before lcl.host, setting up HTTPS in your local development environment was an annoyance, but getting your team to... - Source: Hacker News / 10 months ago

Lcl.host is an easy way to enable HTTPS in local development environments, which improves the security of the development process, ensures feature parity between development and production environments, and enables features like CORS that behave differently on localhost. - Source: dev.to / about 1 year ago

Getting HTTPS setup and working with an app in local development is tricky. There were two options: acquire a publicly-trusted certificate from a CA, or make your own self-signed certificate from the command line. Neither of these options are simple, that's why most developers skip HTTPS in their development environment. But lcl.host now makes this quick and easy. - Source: dev.to / about 1 year ago