Thomas

u/thomas@lemmy.zell-mbc.com
7 posts · 30 comments

Recent posts

Recent comments

This may be a long shot, but it's what I do, so it might be an option: Set up a crypto gateway like CipherMail which will automatically decrypt inbound email and sign/encrypt outbound. The result is that your Thunderbird will never get to see an encrypted email, decryption is handled transparently before it hit's your inbox. Obviously, if you don't trust your email provider, this is not an option.

This isn't simple and hence not for everyone, also comes with dependencies on your email provider, but it works flawless for me ever since I set it up. I run my own email server, hence adding in CipherMail wasn't a big deal.

Very helpful, thank you. I will absolutely watch these videos. And I am really glad that I seem to have found a forum where I can get some good input whenever I am stuck on something. It's been painful in the past :-) I know I am lacking the basics but still managed to get an app off the ground which appears to be useful for quite a few users globally. B

Ha, thank you. I didn't even realize that there is such granularity in dispatchers. Changed accordingly 👍 I assume the IO dispatcher is somehow more efficient when it comes to IO tasks?

Would you care to elaborate about the lifecycle scope? I somehow don't seem to be able to add the dependency and am not sure how this is going to improve things? Is this about making sure that the coroutine does or doesn't get canceled in case the user quits the activity before the import is complete?

//        LifecycleCoroutineScope(Dispatchers.IO).launch {
//        LifecycleScope(Dispatchers.IO).launch {
        CoroutineScope(Dispatchers.IO).launch {
            importLogic()
        }

I do agree, just couldn't figure out how to do it properly. Opening the ZIP and all subsequent actions are now outside of the composable import(). But I realized the UI didn't get updated until the "outside" function completed, so I ended up pushing the business logic to a coroutine:

Like this:

        setContent {
            ImportUI()
        }
        CoroutineScope(Dispatchers.Default).launch {
            importLogic()
        }
on *Permanently Deleted* · c/selfhosted · 21 pts · 3y

You would expose the port to your host which makes the db acessible by anything running on the host, docker or native. Something like

`port

  • 5432:5432 `

But I would recommend running a dedicated db for each service. At least that's what I do.

  • Simpler setup and therefore less error-prone
  • More secure because the db's don't need to be exposed
  • Easier to manage because I can independently upgrade, backup, move

Isn't the point about containers that you keep things which depend on each other together, eliminating dependencies? A single db would be a unecessary dependency in my view. What if one service requires a new version of MySQL, and another one does not yet support the new version?

I also run all my databases via a bind mount

`volume

  • ./data:/etc/postgres/data...`

and each service in it's own directory. E.g. /opt/docker/nextcloud

That way I have everything which makes up a service contained in one folder. Easy to backup/restore, easy to move, and not the least, clean.

on Docker-compose + Traefik · c/ntfy · 2 pts · 3y

I did indeed, and I have to say I am impressed from what I see so far! A really nice and complete tool you created. Thanks a lot for putting in the hours 👍

:-)

But seriously, I was wondering about the requirement to shutdown the VM's and couldn't come up with a solid reason? I mean, even if QEMU/KVM/Kernel get replaced during a version upgrade or a more common update, all of these kick in only after the reboot? And how's me shutting down VMs manually different from the OS shutting down during a reboot?

I know I am speculating and may not have the fill picture, probably a question for the Proxmox team, there may be some corner case where this is indeed important.

By the way, Mexican or US black strat? :-)

I have been looking into Mastodon a while back but found it way too complex for my single user use case. I ended up with Akkoma running on Docker which seems to be a much better fit for this requirement. I also set up Lemmy on Docker a week ago or so which seems to run fine as well. I noticed the comment here that the Lemmy documentation for Docker is incomplete, which I noticed as well. But I figured it out, so if you hit a road block I may be able to help.

Like you I have OPNsense in a VM on one of my PVEs. But I only made sure the nigthly VM back up ran and didnt even bother shutting down the VMs during the upgrade. The VMs got restarted during the final reboot, as the would with every other reboot, and I was back in business.

Well, depends on what your client OS is I guess. There's a cli tool called proxmox-backup-client which allows you to back up OS level, I use this to back up the host OS of my PVE server. I am not sure if this tool is available for Windows/Mac though.

I have 2 PVE servers and on one I have installed PBS in parallel, which works fine. Just a different port to get to the UI: PVE: https://pve2:8006 PBS: https://pve2:8007

You didn't say what you are using for your scheduled backups. If it's something like Borg backup you got a similar level of functionality, CLI instead of a nice UI though.

I have been using Borg for years and recently also installed PBS. What I do like about it is that the UI is similar to PVE and that it nicely integrates the backup prcess into the UI which makes handling easier and in the end less error prone when it comes to restores I guess. From where I stand right now I will likely keep PBS for things which run on PVE, Borg for the rest of the world.