boredazfcuk

``` 2024-03-22 13:31:01 INFO Bark server: https://api.day.app:443 ``` The `bark_server` variable should just be the server, nothing else. By setting it as you have, the notification URL becomes: ``` http://https://api.day.app:443/push...

This behaviour is by design. It is testing it has TCP connectivity to a DNS server. Without this, messaging functions within the container will fail. You need to either fix...

I've made some changes to this check. Please update and try again.

If you create the failsafe file using `sudo docker exec -it icloudpd touch /home/user1/iCloud/.mounted` or something similar, then you are creating that file inside the container. This defeats the purpose...

The script doesn't create the .mounted file. It has to be a manual process performed outside of the container. It's basically a marker so you can say "this is the...

> I would suggest it be added to the README or better yet, include it as part of the Initialization process - even if it's just a warning to the...

> Can you please elaborate on mapping the volume. I'm not clear on this. When working with containers, if you delete the container, or upgrade it, you will lose everything...

I'm not familiar with the Synology Container Manager, but try creating two volumes and attach them to the container. One called "config" and attach it to "/config" and a second...

The container does pretty much both of those on every launch as part of its initialisation. Just need to set the `directory_permissions` and `file_permissions` variables with the permissions you want....

Your download path is wrong. You've mounted `/volume1/homes/michael/Photos/icloud_M` to `/home/boredazfcuk/iCloud` inside the container, so your download path would need to be `/home/boredazfcuk/iCloud`. But for that to be valid, you'd need...