Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CH
Posts
1
Comments
105
Joined
2 yr. ago

  • How do you/did you delete your account? How can you make sure they don't just undelete your stuff again?

    I myself sent them a GDPR request to delete my accounts and all the associated data. Didn't hear anything yet, but they still got three weeks time before I hire an attorney (or make a formal complaint with my local DPA)

  • Make sure the docker containers are using the same network. If you didn't specify something, this should be the case for all three containers in the compose file.

    Alright, now give every container a name of your choosing using the container_name field.

    Lastly, change the nginx config to refer to the app container by name, but I think you already did that: upstream djangoapp { server container-name:port }

    No need to expose any ports except the 80 or 443 of the nginx container.

    If you have issues, spin up a temporary alpine container with a command like "tail -f /dev/null", and use it with "docker exec -it temp /bin/bash" to install debugging stuff to debug the connection (nc/netcat, curl, ...).

  • What about Microsoft 365? The tenant itself is free and per account and month you pay about 5-10$ (depending on sibscription level).

    With this you have the full MS Exchange experience, you get 1TB of OneDrive space and all the shebang.

  • Ahhhh.... alright, I misunderstood. So either depends_on is your friend or you could implement a rather dirty solution: Write a little script for the NPM healthcheck that also checks if searxng is online. Then use autoheal.

    But that would be my last solution and only if the searxng is very closely depending on the npm container.

  • This will do exactly what you want: You have to configure a healthcheck for searnxg that detects when it's down. Maybe something with curl or whatever.

    As soon as it's down autoheal will restart the container. Doesn't matter why it is down (update, dependency not running, ...) autoheal will just restart the container.