Website: https://hctr.dev
Banner image from: https://nightsky.hctr.dev
Time for a quick #introduction I think:
- Software developer (10+ years)
- Backend & a little frontend
- Go
- Kotlin
- Svelte π§‘
- Exploring gamedev with Godot πΉοΈ
- Hosting my own stuff for fun π‘
- Hiking, nature & traveling
- Learning digital art
- Plant-based π±
#promosky
I usually don't, but I often wonder if I should. Just in case something changes between the time I wrote the message and the time it gets received. Is there any "scheduled message etiquette" I should know about?
I usually don't, but I often wonder if I should. Just in case something changes between the time I wrote the message and the time it gets received. Is there any "scheduled message etiquette" I should know about?
One I came across:
- User IDs are sequential
- Passwords are 7 characters (only numbers)
- 2FA only with SMS
- Login asks for only 3 digits of your 7 number code
π€―
One I came across:
- User IDs are sequential
- Passwords are 7 characters (only numbers)
- 2FA only with SMS
- Login asks for only 3 digits of your 7 number code
π€―
API tests run the entire app locally (with some dependencies mocked out) and call the API over HTTP to test the entire flow.
The synthetic monitoring calls APIs in prod.
But maybe what I call API testing isn't the same as what you call API testing π
API tests run the entire app locally (with some dependencies mocked out) and call the API over HTTP to test the entire flow.
The synthetic monitoring calls APIs in prod.
But maybe what I call API testing isn't the same as what you call API testing π
I don't have a good answer for this one. AI to filter out AI code? π
I don't have a good answer for this one. AI to filter out AI code? π
By pulling random code from your account I'd hope to show the real you.
By pulling random code from your account I'd hope to show the real you.
Maybe using code from PRs would mitigate this a little?
Or a more complex system to detect and exclude copied code?
Maybe using code from PRs would mitigate this a little?
Or a more complex system to detect and exclude copied code?
It would connect to your Github and pull random pieces of code to show other people (nothing else about you). If you both like each other's code you could connect π«Ά
It would connect to your Github and pull random pieces of code to show other people (nothing else about you). If you both like each other's code you could connect π«Ά
But I suppose it's a good reminder to set up uptime monitoring/alerts on important services, specially self-managed ones. I know I've been putting it off for a long time π¬
But I suppose it's a good reminder to set up uptime monitoring/alerts on important services, specially self-managed ones. I know I've been putting it off for a long time π¬
In my case it was my own fault - I added a build step to minify the HTML back when I was using 11ty and I kept it after the rewrite to Svelte. I never thought it would be an issue π€·
In my case it was my own fault - I added a build step to minify the HTML back when I was using 11ty and I kept it after the rewrite to Svelte. I never thought it would be an issue π€·
I noticed HEAD elements were getting duplicated and I couldn't figure out why. Turns out Svelte actually uses comments in the markup to handle updates without duplication! So I broke it by removing them π
github.com/sveltejs/sve...
I noticed HEAD elements were getting duplicated and I couldn't figure out why. Turns out Svelte actually uses comments in the markup to handle updates without duplication! So I broke it by removing them π
github.com/sveltejs/sve...
It's now completely written in Svelte
hctr.dev/post/rewriti...
It's now completely written in Svelte
hctr.dev/post/rewriti...
As for the script, the core of it is:
HETZNER_API_KEY="xxx" lego --email mail@domain.com --dns hetzner --domains "*.domain.com" renew
The rest of the script just runs this for a few different domains and moves the certs to the right folder π
As for the script, the core of it is:
HETZNER_API_KEY="xxx" lego --email mail@domain.com --dns hetzner --domains "*.domain.com" renew
The rest of the script just runs this for a few different domains and moves the certs to the right folder π
The lego CLI does all the hard stuff to get the actual certificate. I just need to run the right command and provide credentials (since I'm using a DNS-based challenge to verify domain ownership)
The lego CLI does all the hard stuff to get the actual certificate. I just need to run the right command and provide credentials (since I'm using a DNS-based challenge to verify domain ownership)
I have a simple cronjob once a week to renew wildcard certs for my domains using Lego (github.com/go-acme/lego). Then I run a Traefik proxy for all my containers that uses those certs. Haven't thought about it much since I set it up!
I have a simple cronjob once a week to renew wildcard certs for my domains using Lego (github.com/go-acme/lego). Then I run a Traefik proxy for all my containers that uses those certs. Haven't thought about it much since I set it up!
First time I've heard of Dokploy though π€
First time I've heard of Dokploy though π€
My favourite "feature" so far is that the fans no longer spin up as soon as I plug in the power π€―
My favourite "feature" so far is that the fans no longer spin up as soon as I plug in the power π€―
Now I'm trying really hard to resist the urge to rewrite it all π
Now I'm trying really hard to resist the urge to rewrite it all π
I agree with the main point though, nothing wrong with an open source project copying a familiar layout!
I agree with the main point though, nothing wrong with an open source project copying a familiar layout!