

I never set up the actual bank sync, I think what I did was basically a CSV export and then import, rather than the bank sync.
But it’s been about a year so not remembering exactly how the import was.


I never set up the actual bank sync, I think what I did was basically a CSV export and then import, rather than the bank sync.
But it’s been about a year so not remembering exactly how the import was.


I use actual as well.
The docker compose works really well, basically set it up once and then it works, even with running updates by pulling new container versions.
I used the account importing to start but now input everything manually and don’t do live sync.
Never heard of the other options so didn’t know about them to compare before setting up actual. I do like the methodology of actual, where it has you only budget money that actually exists in your account, that feels very sane to me.
For what it’s worth I was able to migrate my docker of gitea to a docker of forgejo by just changing the image to be forgejo and remaining some if the environment variables. It uses the game data and database so it’s basically a drop in replacement that they have instructions for on their website.
Makes trying it out pretty simple, not sure about migrating back to gitea from forgejo though.


Worse than that, the issue the article states isn’t that it’s a flat pack, it’s that fedora is pushing their rebuilt flat pack of obs that’s buggy instead of the official obs one from flat hub that works, and then the obs project is getting bug reports for a third party distribution that’s broken.
Because fedora isn’t just pushing flat packs, they’re pushing made by fedora versions of them instead of the official builds from the maintainers.


The proxmox interface let’s you make the containers, but you have to install the software you want to host in that container after creation.
These scripts let you run a script that makes the container and also installs what you want to host within the container and does the setup.
I used their script to set up a home assistant vm, you run the script and it downloads the HaOS install media and does the install in the VM for you, preconfigured, and starts it so all I had to do was go access the web interface.
I think when I set up vault warden with the docker compose it had scripts to generate it’s own self-signed certificate. So it was already set up to use https.
I have a CA I created with easyrsa so I went and found the csr from vault warden and signed it with my own CA, so I didn’t have to juggle two certs.
But otherwise yeah, running it on my local LAN, no let’s encrypt.