> 1Password ssh agent and git ssh signing

I’m still working through how to use this but I have it basically setup and it’s great!

It’s fast because it sucks the life force from bad developers to make them into something good.

Jokes aside…

I really like uv but also really like mise and I cannot seem to get them to work well together.

Why? They are pretty compatible. Just set the venv in the project's mise.toml are you are good to go. Mise will activate it automatically when you change into the project directory.

I believe I was trying it the other way around. I installed uv and python with mise but uv still created a .python_version file and using the one installed in the system instead of what was in mise

I like Go but it’s dependency management is weird and seems to be centered around GitHub a lot.

It's mostly tradition rather than a hard requirement. Go has long supported vanity import paths: https://pkg.go.dev/cmd/go#hdr-Remote_import_paths

For example, we use Hugo to provide independent Go package URLs even though the code is hosted on GitHub. That makes migrating away from GitHub trivial if we ever choose to do so (Repo: https://github.com/foundata/hugo-theme-govanity; Example: https://golang.foundata.com/hugo-theme-dev/). Usage works as expected:

  go get golang.foundata.com/hugo-theme-dev

Edit: Formatting

There is nothing tying Go to GitHub.

Not at all. It can grab git repos (as well as work with other VCSs). There's just a lot of stuff on GitHub, hence your impression.

I was thinking of using that in combination with Beelink ME Mini N150 with proxmox installed on it and host different net tools, git, etc that’s available on the go. I might be overthinking the setup

I have trust issues using actions that are not from official and reputable sources like GitHub official and AWS actions. I don’t know why an ssh action is necessary, seems like a nice way to get your ssh credentials stolen and ssh isn’t that hard.

AWS code (build|deploy) supports GitHub actions workflow, gitlab does, gitea (codeberg, forgejo) too

The biggest issue is the compatibility, forgejo doesn’t have all the actions available that GitHub does nor some of the same functionality

My biggest thing for UUIDs is don’t UUID everything. Most things should be okay with just regular integers as PKs.

Can you actually customize that Cloudflare error page? I thought that was their error page when they lose connection with your site and custom error pages was just the ones your app creates, like 404, 403, etc?

I think the intent is for joke pages, like the demo link which acts like error 500 saying the host is on fire etc but really serves as 200 OK, not your actual Cloudflare service errors.

You can, on the $30 plan - you can give it a hidden url on your current domain and it will cache & serve that content.

On free plans you can't, on business/enterprise plans you can.

Edit: Gemini says you could make a custom worker and do a 5XX redirect that way, but I haven't tried it. Does make sense though.

This works for errors at the origin or in a Worker, but won't for errors at the edge, because those are in front of Workers.

I think Gemini refers to Web Workers API rather than a Cloudflare Worker. And that should work indeed.

the custom error page is configurable at a domain (zone) level

which sometimes gets annoying because branding for subdomains could be different.

https://developers.cloudflare.com/rules/custom-errors/edit-e...

> Error Pages do not apply to responses with an HTTP status code of 500, 501, 503, or 505. These exceptions help avoid issues with specific API endpoints and other web applications. You can still customize responses for these status codes using Custom Error Rules.

From that page ;)

The only pain point I had using letsencrypt, and it wasn 100% not their fault, was I tried using it to generate the certificate to use with FTPS authentication with a vendor. Since LE expires every 90 days and the vendor emails you every week when you’re 2 months from expiring, that became a pain point and it wasn’t easier to just by a 1 or 2 year cert from godaddy. Thank goodness that vendor moved to sftp with key authentication so none of that is needed anymore

This was the only objection I had gotten about using letsencrypt 6 years ago but that guy is gone and now we either have letsencrypt or AWS certificates