

If you know iptables, just stick with that. In my testing, docker containers seem to ignore ufw rules. Supposedly, iptable rules are respected but I haven’t learned iptables yet so I can’t verify.
If you know iptables, just stick with that. In my testing, docker containers seem to ignore ufw rules. Supposedly, iptable rules are respected but I haven’t learned iptables yet so I can’t verify.
I don’t know what the fuck is going on. The client app connects to all 4 servers it needs a connection to. I can create a user on the server and all clients can login using it, I just can’t get notes to sync.
Official docs here
I found this tutorial1 and this tutorial2
Tutorial2 makes this one port change to the official docker compose file but otherwise is seemingly the same as tutorial1:
notesnook-s3:
image: minio/minio:RELEASE.2024-07-29T22-14-52Z
ports:
- 9009:9000
- 9090:9090
With that change, and setting the port of the domain to 9090, I can access minio in the browser. But I don’t know if that’s necessary or not. I’m stumped.
Did you by chance self host the sync server using docker compose? Their instructions aren’t great and I was hoping you had some tips.
For anyone else interested, if I figure it out, I’ll post what I did here.
Edit 1: I finally got it all setup but syncing isn’t working so I guess I did something wrong 🙄 . Troubleshooting now
9 meals
I’m not familiar with that reference
The downward trend on the stock market is still in place 🤷♂️
“NPM” node package manager?
I don’t know how markdown works. that should be 1,3,4,5
Damn, I didn’t realize they had public logs like that. Thanks for the heads up
To go along with that, Telegram doesn’t make it easy to set up an encrypted chat. First, you have to set up a regular chat, then tap on the profile image of the person you are messaging, then tap the 3 dot menu, and finally tap “secret chat”. It’s there but they clearly don’t want people using it.