You must log in or register to comment.
Did the coffee mug go through the wall or up is ass?
Yes
Just later that day? Clearly, comic man doesn’t have to cojones to fuck up as badly as I have.
Sure feels like that sometimes, LOL
Is he giving himself cigarette burns?
Wow that’s subtle. Good catch
Every single day
Who is OP, and how did you get pictures of me last night?
if ([]){ // I miss common Lisp's detection of empty }LoL, blue shirt has no persistence. Anger and giving up gets you nowhere.
![XKCD #349 - "Success": [Four full-width panels arranged vertically, each with a label for number of hours elapsed, with a title above the stack of panels.]; Title: As a project wears on, standards for success slip lower and lower.; [Megan is standing behind Cueball, watching him as he sits at a desk working on a desktop computer on the desk.]; Label: 0 hours; Cueball: Okay, I should be able to dual-boot BSD soon.; [Cueball is on the floor fiddling with the open tower in front of him. Megan is not shown in the panel, but may be off-panel unless Cueball is talking to himself.]; Label: 6 hours; Cueball: I'll be happy if I can get the system working like it was when I started.; [Cueball is standing in front of the computer, which now has a laptop plugged into the tower. Megan is still not shown in the panel, but may be off-panel again.]; Label: 10 hours; Cueball: Well, the desktop's a lost cause, but I think I can fix the problems the laptop's developed.; [Cueball and Megan are swimming in the sea; an island and a beach can be seen in the distance.]; Label: 24 hours; Cueball: If we're lucky, the sharks will stay away until we reach shallow water.; Megan: If we make it back alive, you're never upgrading anything again.](https://lemmy.ml/api/v3/image_proxy?url=https%3A%2F%2Fimgs.xkcd.com%2Fcomics%2Fsuccess.png)
Title text:
40% of OpenBSD installs lead to shark attacks. It’s their only standing security issue.
I don’t like being on this picture.
I would be sad too, if someone broke my PC and smashed my home.
“oh it was just a missing semicolon”
Rubber duck debugging often helps.
Linter issue.
Even if you’re not using one, you should be instinctively looking for the semicolon the moment you get a syntax error after a while.
Aw come on, debugging can be fun. I love the investigative vibe of it. You get to be your favorite detective. You start asking around. You pin the the culprit. You get closer and closer to damning evidence. And then Bam! Fixed. Another mystery solved. Mine’s Columbo.
It’s fun when you debug your own code.
I love asking,
“What sick fuck thought this was an acceptable solution?”
And a few moments later:
“Oh. It was me.”
Just finished with a refractoring project. I said this a LOT.
Agreed, for any non-trivial bug I just start dumping text into a word file to track what I’m doing. Like: error messages, values of variables at key places, libraries used, URLs of documentation and background reading and stackoverflow pages looked at, test fixes and their effects, etc. Then if someone asks me wtf I’ve been doing all day I can easily show them. Also, if I have the same problem a couple months later I can remind myself.
so the other day I sat down trying to setup a SSL cert for my self-hosted services
Might want to check out swag from linuxserver.io
It’s a docker/kubernetes container image with a working certbot client in it.
Have you heard of our Lord and Savior, Traefik + ACME issuers?
Does Trafik also allow DNS based challenges with additional certbot plugins, or does it only work by serving a challenge in /.well-known/?
I’ve set up my internal homelab with LE certificates, but if I could get rid of certbot and do this automagically, it’d be nice…
Not all dns providers support acme, I’ve discovered to my recent annoyance. The one I use at work, for instance.
I already use certbot with my DNS provider, so it should generally be supported. And indeed, O found the docs, where all supported providers are listed.
Yeah. For wildcard DNS from letsencrypt, you can’t do HTTP validation, only DNS, which involves creating a TXT record.
Your DNS provider needs to run an ACME server, which runs an API that’ll add the required TXT records on request.
As I understand it.
The DNS provider needs to provide an API, but not an ACME server.
Your server contacts Lets Encrypt and wants a certificate - say for homeserver.example.com. It tells Let’s Encrypt to use DNS based authentication. Let’s encrypt answers with a challenge code, that you now publish as a txt record with a defined name via your providers API for this (sub)domain. Let’s encrypt then checks the TXT record and if it finds the challenge there, it sends you the certificate.
Wouldn’t the authentication API provided by your DNS host be the ACME server?
I have it setup to use DNS challenges through Cloudflare, but it supports different providers as well. I just add the labels to my docker container and voila, I have TLS
Let’s Encrypt Expiry Bot just entered the chat.
Let’s encrypt brother
Reminder to all you chaos monkeys: use
[Object object]on web forms occasionally for a bit of fun.I shit you not I got that object object response with a 200 status.
My favorite so far:
$ gdb -ex 'file /bin/gdb' run corrupted double-linked list Thread 1 "gdb" received signal SIGABRT, Aborted.
