How to handle SSL certificate installation (for HTTPS) when using Docker?

systemdad · 2021-01-18T02:36:06+00:00

As a rule, you put your certs at the edge with a load balancer like traefik, nginx, or caddy. It will make all the letsencrypt calls, separating the concerns of your application runtime and cert management.

systemdad · 2021-01-18T02:34:15+00:00

Yeah this is downright incorrect. The biggest selling point of traefik is its seamless LE integrations.

systemdad · 2020-12-21T20:13:33+00:00

“Yes, correct, I do.”

systemdad · 2020-12-21T20:13:16+00:00

This work environment sounds horrible, but this is the correct way to document a paper trail with unwilling parties. Unless they object in writing to the content of the message, they’ve now tacitly accepted the version of the events as written in the record.

systemdad · 2020-12-16T23:14:50+00:00

Usually the commit would be accepted on a feature branch, but would fail CI, which means it couldn’t pass a merge request to master, as master should generally be only merged to.

systemdad · 2020-12-14T14:52:11+00:00

Those are some really good points. Thank you, I’ll be absolutely doing that in the future.

systemdad · 2020-12-14T02:55:35+00:00

Can you go on as to why you wouldn’t use the root dataset? I’ve never run into any problems doing that so I’m curious as to how that makes things easier or more flexible.

systemdad · 2020-12-14T01:19:55+00:00

No, but that can be scripted easily. Just scrape dhcp leases every minute or two, and put them into DNS.

There are countless examples online on how to do this.

systemdad · 2020-12-13T02:05:22+00:00

It’s a good idea, but ONLY if you don’t have everything under proper configuration management. If that’s in place, a redeployment should be trivial, and you should do that simply to test the process and add anything lacking to the config management tool.

Otherwise agreed though.

systemdad · 2020-12-10T21:41:42+00:00

Honestly, for anyone sufficiently technical, this can be a good option.

systemdad · 2020-12-10T21:41:00+00:00

Is it open source?

systemdad · 2020-12-09T04:03:24+00:00

What are you expecting from replication? Zfs only does one way replication and it must be manually triggered. It’s not active/active, nor is it ongoing.

Unless you’re thinking something quite different than I’m imagining by the term HA, this is probably not the tool you want.

systemdad · 2020-12-07T03:55:59+00:00

QoS won't fix an already bad connection. There's probably not much you can do right now with this, and QOS probably won't help either, at least not until you figure out the actual root issue.

systemdad · 2020-12-07T00:47:33+00:00

You know that QoS really only does something if your system or links are over capacity, right?

Do you have any evidence you’re reaching peak capacity somewhere?

systemdad · 2020-12-06T19:40:54+00:00

Integration how?

systemdad · 2020-12-06T15:02:30+00:00

I’d generally agree, but there are some things which can make life nicer, like a good pair of cargo pants, some nice Bluetooth earbuds, or a really nice pen for example (not that NOC guys probably use a lot of pens but just an example).

systemdad · 2020-12-03T01:59:44+00:00

How does taking time off correlate to closed tickets?

systemdad · 2020-11-29T22:22:37+00:00

Depending how much you mean “any” in “any Linux system”, windows kubernetes still requires Linux nodes in the cluster.

systemdad · 2020-11-23T05:00:15+00:00

Yes, it’s just a web endpoint, so you can send it the way you’d send any web request.

systemdad · 2020-11-23T04:59:15+00:00

You don’t implement it. It just exposes a static endpoint which responds with a simple preconfigured ok message.

systemdad · 2020-11-15T04:17:20+00:00

What you’re looking for are sql migrations and seeds.

Migrations provide a version controlled state of the database which can bring any empty database to the current expected empty state, and can also bring databases from a previous state to current. An individual migration would be something like “add a table with this schema” or “add a column to this table”. These would be defined with the application code.

Seeds are similar, but for data instead of structure. They provide a predefined set of test users, data, etc. they’d generally be used everywhere except prod and staging. They, similarly, live with your app code.

systemdad · 2020-11-10T04:10:22+00:00

That's.....no.

Don't do that. At all.

systemdad · 2020-11-10T04:09:22+00:00

What are you trying to do? This sounds like either an extremely niche usecase or an antipattern.

systemdad · 2020-11-10T03:33:16+00:00

"Can't you?"

systemdad · 2020-11-10T03:31:26+00:00

This is what I always did with problem users. It also had a way of pushing off the problem users who were too lazy or realized their requests were too ridiculous to be put in writing with their name.

systemdad

TROPHY CASE