It’s an SQLite database. Corruption is very unlikely. So, that’s not something I am worried about.
It’s an SQLite database. Corruption is very unlikely. So, that’s not something I am worried about.
You have to actually add the middleware into the (default) chain for your https
entrypoint (I think in most tutorials it’s called websecure
) - in my static conf I have this:
entryPoints:
https:
address: :443
http:
middlewares:
- crowdsec-bouncer@file
- secure-headers@file
And in my dynamic conf I have this:
http:
middlewares:
crowdsec-bouncer:
plugin:
crowdsec-bouncer-traefik-plugin:
CrowdsecLapiKey: "### Enter your LAPI Key here ###"
Enabled: true
I’ve recently introduced CrowdSec and crowdsec-bouncer-traefik-plugin into my setup and it’s really great to see it block all those spam bots and brute force attempts.
Some food for thought:
When I was looking to get my photos under control, in the end I decided to go all-in with Apple Photos. As I’m also using a Mac, the convenience can’t be beaten. Also, I can easily pull up any photo using Apple’s smart filters and can easily select photos from within apps without having to “share” them to the photos library first.
But this was only decided after I found out that Apple Photos keeps all photos in separate files in original quality and all metadata in a local SQLite database. Using the osxphotos tool, you can query this database and easily pull out any photo incl. metadata - even when running on other OSes, no need for Apple Photos. This also makes it easy to move everything to another system, if needed.
I’ve set my Mac to always keep original copies on disk and run a backup to my NAS every night. (Using CCC at the moment, but looking to switch to restic.) This way, all my photos are always off-site in iCloud, on my Mac and on my NAS.
You’d just need a tool to upload your Android photos to iCloud. From a quick search it seems Sync for iCloud might do the trick - albeit manually … if I read the reviews correctly.
How did you mount it outside the cluster? Did you have a look at the mtab and used the exact same options in the compose file?
There’s no difference between using a volume in Compose to mount a share or your server’s fstab file. Both do the same kind of mount.
I’d suggest /opt/docker/_compose/ for all the compose files. Or, if you keep all the config files for your containers on your NAS, maybe create a share there and put all yml files in it, then mount it on the host. This way everything is on your NAS and nothing is lost if the host freaks out.
And I’d add the NFS mounts to the compose files as well. When specifying volumes, you can use anything the host OS has a mount.xxx command for. Docker will take care of mounting everything.
Put that mount point into the compose file(s). You can define volumes with type nfs and basically have Docker-Compose manage the mounts.
That probably doesn’t work unless you power-cycle the picture frame after changing the photos.
I had this with some offline Samsung picture frame and a Transcend WiFi SD card. The SD card runs a small Linux and can be unlocked to add own scripts. I had a script that would rsync files from my storage to the SD. However, while the new files were written to the SD just fine, the picture frame never re-read the list of files from the SD. And after power-cycling, my specific model needed to be turned on manually again. So, that wasn’t a satisfactory solution.
Following a profile logged-out is impossible now
What do you mean? I can just open an Incognito tab and go to x.com/<username> and see all posts (without replies, though).
because they don’t run alts
I think you underestimate the dedication of some of those trolls. Also, most apps allow to easily switch between profiles with like 2 taps.
Of course, not. But closing and locking the door doesn’t prevent the person on the other side to still listen in on your conversations…
And it’s exactly like this now, if I understand the change correctly. They only removed the “you can’t see this post because the owner limits who can see it” thing. Blocked people still can’t reply.
Yep, that’s why I don’t get all this panicking about the Twitter change…
In closed systems like messengers, where you don’t see any content unless logged in, yes. There, it works brilliantly. But on Twitter, this is like cutting out something from a newspaper when there’s a news stand right next door.
Having a public (i.e. not locked) Twit𝕏 account and believing you can block single people is a bit stupid to begin with.
When screaming on a market square, you can’t demand for single people to “please not listen” to what you’re screaming.
Rather people have no idea how blocking on 𝕏 worked/works. You were ALWAYS able to see tweets from people that blocked you by simply logging out or using an alt account.
I don’t understand all this fuss about this simple change. He only removes a useless feature that was never more than a minor inconvenience for those that got blocked.
If you don’t want people to see your tweets, lock your profile. This worked before and this still works just fine.
There was a discussion about this topic on Hacker News a few months ago:
https://news.ycombinator.com/item?id=40133976
One ex-Googler pointed out that due to the machine learning stuff and every new employee trying out the latest “AI” stuff on top of it, no human can understand and thus debug the search engine properly anymore.
I’m using UberSpace for 5€/month for a few small web projects and for emails. Unlimited mailboxes, unlimited aliases. However, you have to configure it using console commands via SSH. But it’s all explained in their documentation.
I’ve only subscribed to the “Free proxies” blocklist. But these are only additional blocklists. The main attraction of CrowdSec is their “CAPI” (Central API) which has all the current malicious actors detected in the network of CrowdSec instances and is used automatically.