glynnforrest

6 ms·

1.
by glynnforrest 5y ago
Yeah, this pains me too. Here's a relevant issue to keep an eye on: https://github.com/hashicorp/nomad/issues/3854 I've used an nginx-based S3 proxy in the past to get around this. Not ideal but it
2.
by glynnforrest 5y ago
> Is terraform generally used to deploy workloads to nomad instead of writing tasks directly? It can be, although it has some weird shortcomings. For example, if the job is already present in Nomad but not running ("dead"), I d
3.
by glynnforrest 5y ago
> the frustration is knowing someone, tucked away on a private network, has already done this. Hard agree. I know this person and have been this person before. I've toyed with the idea of writing a book of Nomad recipes and tips, I
4.
by glynnforrest 5y ago
Good point! Although Docker does add a networking layer on top. I'd prefer to run something like HAProxy without Docker if possible.
5.
by glynnforrest 5y ago
I understand what you're saying. Fewer runtimes = fewer problems. It's not going to force your hand. You can disable all the task drivers except the docker driver if you want a container-only cluster. The drivers themselves are li
6.
by glynnforrest 5y ago
> Flexible Workload Support This is Nomad's most underrated feature, IMHO. You don't have to use containers for everything if you don't want to. For example, if you're a golang shop you can run everything as native bi
7.
by glynnforrest 6y ago
I only have praise for the HashiStack (Nomad, Consul, Vault). Folks often reach for Kubernetes as part of a larger initiative to containerize their apps, add ephemeral test environments, etc, but I really think Nomad is better suited to thi
8.
The search for the perfect setup script(backbeat.tech)
1 points by glynnforrest 6y ago|0 comments
9.
by glynnforrest 6y ago
That's terrible. There's nothing worse than losing data. I'm working on this exact problem at the moment: a dashboard to keep track of your backups to check they never fail. https://backupshq.com * Get notified wh
10.
by glynnforrest 6y ago
Oh! I'm working on this exact problem at the moment: a dashboard to keep track of your different backups. * Get notified when backups fail or take too long via email, slack, webhook, etc. * Run your backup scripts and tools with our op
11.
by glynnforrest 6y ago
Agree 100%. 3 different copies of the data, on at least 2 different mediums, with 1 off-site. Reducing the obstacles to making any backups at all is a good first step though!
12.
by glynnforrest 6y ago
Firstly, sorry to hear about your backup woes. There's nothing worse than losing data. Three tricks that have worked for me: 1) Reduce the resistance in your brain to making backups Easy wins can be made here without changing anything.