Yep - I feel that, especially after the branded hard disk carry on last year.

I’m a +1 on this. A secondhand Synology set up with some RAID will delay this decision for a few years and give you time to build your expertise on the other aspects without worrying much about data security. It’s a pity that you’re nearly at the limit of 8TB - otherwise I would have suggested a two bay NAS with 2x8TB, but if you’re going to use second hand drives (I do because I’m confident of my backup systems) maybe 4x6TB is better. Bigger drives are harder to come by 2nd hand - and plenty of people will not be comfortable with secondhand spinning rust anyway - if that’s you, then a 2 bay with 2x12TB might be a good choice.

The main downside (according to me) of a Synology is no ZFS, but that didn’t bother me until I was two years in and the owner of three of them.

Thanks for this thoughtful write up of your process. I’m increasingly thinking about what context the model has and keeping it as focused as possible - both to reduce token usage, and to ensure it doesn’t have any cruft in it that potentially causes the model to go down an un-useful path. The prompts for this read like what I imagine a conversation with a junior developer would be when handing off a task.

In practice, this is usually clearing the context after quite small changes and the prompting for the next one with just what I think it is going to need. I guess this is ‘context engineering’ although that sounds like too fancy a term for it.

Proxmox on the metal, then every service as a docker container inside an LXC or VM. Proxmox does nice snapshots (to my NAS) making it a breeze to move them from machine to machine or blow away the Proxmox install and reimport them. All the docker compose files are in git, and the things I apply to every LXC/VM (my monitoring endpoint, apt cache setup etc) are all applied with ansible playbooks also in git. All the LXC’s are cloned from a golden image that has my keys, tailscale setup etc.

100% this. And Lenovos and HPs designed for the business market generally are a pleasure to work on (in the hardware sense) if you need, with good manuals and secondhand spare parts.

Thanks - I have now! It looks like updates of repos I’ve stared? But I’ll never go there again, and suggest OP not do that either if it’s upsetting to them. I just go to my profile, or the project I’m interested in.

I’m local first - stuff I’m testing, playing with, or “production” stuff like Jellyfin, Forgeo, AudioBookshelf, Kavita etc etc. Local is faster, more secure, and storage is cheap. But then some of my other stuff that needs 24/7 access from the internet - websites and web apps - they go on the VPS.

Wait, there’s a GitHub “feed”?

None of the bad things mentioned here have happened to me using GitHub on the daily. Totes agree it’s probably not great to depend on a business for free hosting, but it’s also pretty straightforward to move in the future if needed.

I just do one Docker container per LXC. All the convenience of compose, plus those sweet Proxmox snapshots.

Is there a reason not to use Tailscale for this?

Forgejo - actively developed open source. It’s what powers Codeberg. Easy to set up and manage with Docker. I moved to it from Gogs and skipped Gitea after reading about the forks.

Yep. Glad he’s got a system that works for him, but as a solo dev I love my Forgejo. I self host it, (so no Trust issues) and if you’ve hosted any other services before, the setup is a simple Docker compose - so I’m not sure I accept the Heavyweight argument either.

Is there an easier way to give them money than becoming a member?

It got enshittified. I went to use it one day and it wouldn’t work without creating an account.

Same - As an Insomnia refugee, I thought “Oh no, not this again” and felt foolish for evangelising it.

I switched from Copilot to Codeium after only a couple of months of Copilot use - just based on the cost since currently I’m just a hobby coder.

The main difference I’ve noticed is that Codeium doesn’t seem as smart about the local context as Copilot. Copilot would look at how I’m handling promises in a project, and stick to that, whereas Codeium would choose a strategy seemingly at random.

A second, and maybe more telling example, is that I do my accounts using ‘plain text accounting’ in VS Code. This is a very niche approach to accounting software and I imagine is hardly in the training sets at all - there certainly would not be a lot of public domain text accounts in the particular format (BeanCount) I use in public code repositories. Codeium doesn’t make any suggestions for entries as I’m entering transactions, whereas Copilot would see that the account names I’m using are present in another file in the project and suggest them, and very quickly figure out the formatting of transactions and suggest them correctly.

If we’re making a list of great projects written in Go, I’m putting in a word for PocketBase which is a based around sqlite that works as a backend-as-a-service and does all the tedious auth work for you. It’s the perfect sideproject backend.

For anyone without the inclination to wade through 47 pages, here’s what they say about HTMX, which they’ve classified as “Assess” rather than “Trial” or “Adopt”

htmx is a small, neat HTML UI library that recently became popular seemingly out of nowhere. During our Radar discussion, we found its predecessor intercooler.js existed ten years ago. Unlike other increasingly complex pre-compiled JavaScript/TypeScript frameworks, htmx encourages the direct use of HTML attributes to access operations such as AJAX, CSS transitions, WebSockets and Server- Sent Events. There’s nothing technically sophisticated about htmx, but its popularity recalls the simplicity of hypertext in the early days of the web. The project’s website also features some insightful (and amusing) essays on hypermedia and web development, which suggests the team behind htmx have thought carefully about its purpose and philosophy.

Us looking at developers still on dBase III ~inserts Judgmental Volturi meme~