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()
}
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
But I would recommend running a dedicated db for each service. At least that’s what I do.
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
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.
For me it’s Borg backup for Nextcloud an all the other servers
Turns out there are no more http websites out there, at least I couldn’t find any. Good for our security, bad for my demo :-)
I herewith grant you the official title of a real hacker :-)
That’s the tool I was looking for, thanks a lot!
Wireshark is my backup plan for a text based demo. Unless I am missing something pictures in Wireshark will just be binary stuff across multiple packets which won’t work for a demo. The tool I am looking for managed to identify which packets contains image data and showed them in a grid
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 👍
For a while it’s just data in, which it handles really well. But it really started to shine for me when I needed to find some of the documents. OCR and their search works very well for me.
There are also some interesting thoughts in here: https://skerritt.blog/how-i-store-physical-documents/
What’s the error?
Can you run docker-compose logs
Here’s mine: https://cloud.zell-mbc.com/s/Ac5KQTTxcWNYbNs
I tried to add file it to this post but formatting got completely messed up, hence a link.
Before you run docker-compose you need to change the paperless-app volumes to fit your requirements and set up the variables in .env
Device is a HP Pro 9010 Printer/Scanner with a local SMB folder set up as scan target. Paperless monitors the share and picks up everything someone (I) put in there. Scanner, PC, phone, anything which can connect to the SMB share. Dead easy and works reliably.
Let me throw in Paperless NGX, https://github.com/paperless-ngx/paperless-ngx
:-)
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? :-)
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.
KeePassXC and Nextloud to sync things between devices…
KeePassXC for me…
I used this guide when setting up my self hosted email: https://workaround.org/ispmail/buster/big-picture/
I also added in Ciphermail for email encryption and it’s been almost hands off ever since.
Granted, there were quite a few things to digest until things were working as I wanted.
I set mine up with the 0.17.4 and got it working, but like you wrote the the instructions have changed, all the detail is gone so I can only guess. Are there any volume statements in the new (v. 0.18) docker-compose.yml for the proxy container which would point to a local file? Mine has got this:
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf:ro
and I had to set up the local nginx.conf file.
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.