It’s like YNAB4. For those of us in that vintage it’s perfect. If you’re using the newer YNAB it might have missing features.

The “minimal” part is incorrect; it is a super complicated container. The number of moving parts don’t leave me with any confidence that I could keep it running or fix any issues going forwards.

Mainly for security. I was originally looking at CoreOS but I liked the additional improvements by the UBlue team. Since I only want it to run containers, it is a huge security benefit to be immutable and designed specifically for that workflow.

The Ignition file is super easy to do, even for just one server (substitute docker for podman depending which you have):

Take a copy of the UCore butane file:

https://github.com/ublue-os/ucore/blob/main/examples/ucore-autorebase.butane

Update it with your SSH public key and a password hash by using this command:

# Get a password hash
podman run -ti --rm quay.io/coreos/mkpasswd --method=yescrypt

Then host the butane file in a temporary local webserver:

# Convert Butane file to Ignition file
podman run -i --rm quay.io/coreos/butane:release --pretty --strict < ucore-autorebase.butane > ignition.ign

# Serve the Igition file using a temp webserver
podman run -p 5080:80 -v "$PWD":/var/www/html php:7.2-apache

During UCore setup, type in the address of the hosted file, e.g. http://your_ip_addr:5080/ignition.ign

That’s it - UCore configures everything else during setup.___

Rootless Podman :) It requires you to learn a little bit of new syntax, for example, the way you mount volumes and pass environment variables can be slightly different, but there’s nothing that hasn’t worked for me.

I’m using this on uBlue uCore, which I would also strongly recommend for security reasons.

I switched and was very glad to do so. You increase your security and so far I haven’t seen any downside. Every container I’ve tried has worked without issues, even complex ones.

Just remember that Cloudflare decrypts and re-encrypts all your data, so they can read absolutely everything that passes through those tunnels.

Here is clockwise. One arrow is going to the right and one to the left.

They recommend SimpleFIN instead of Plaid: https://old.reddit.com/r/selfhosted/comments/1cmfk8x/actualbudget_has_anyone_written_a_plaid_importer/

Yes

You jumped to a conclusion on pricing and made a mistake, it’s ok, no big deal.

Lol you weirdo, I even said I did that:

https://lemmy.world/comment/12622960

Try clicking either of those links.

Regardless, this is a thread about self-hosted open-source budgeting, which is why I linked to Actual Budget. I have updated the first post to be the Github link instead to prevent confusion.

all I saw was pricing […] can you really blame me?

I mean I really can. They don’t have any paid option so you definitely didn’t see any pricing. They only have a big open source message:

You’re replying to my comment about Actual Budget, the very open source budgeting solution?

Net worth and investment tracking goes in my spreadsheets, budgeting in Actual Budget.

deleted by creator

Why not Actual Budget, which is also self-hosted, open-source bucket budgeting based off YNAB, however it appears to be a lot more mature.

They also transparently run the project on Open Collective which I like: https://opencollective.com/actual

Any cloud is a secure backup on Linux if you use rclone crypt :)

It works with Google Drive, Dropbox, One Drive, and countless others to create an encrypted cloud storage, where the cloud provider can never view your file contents.

I do it that way for my kid as she prefers it, and the “normal” way for me, and it is identically easy.

I cannot understand the claim that it’s easier the seed end, it’s just not true.

It’s definitely cleaner doing it the normal way from the bunch end as you never get bits of banana on you if it’s a particularly squishy one.

Bunch end wins for me. Just as easy if not easier and no mess.

Very true. The discussion helped me, as I did think it meant not easily editable.

As root of course you can change the system to be any other type of system (layer packages, rebase, whatever), but I did assume it meant not easily modifiable in it’s current state.