If you’re using docker compose, it will create a default bridge network with a CIDR that could overlap with a real network routable to the host, which messes up network egress from the container.
If this is the case it’s useful to specify the bridge network CIDR in the compose file as something you don’t use.
It’s really useful too. You can either pipe in text or for example Get-ChildItem a directory of files and it will parse them all. As usual it returns a helpful object with properties like line number.
What is 'end-to-end encrypted' about dumbdrop?
I ran a quick test by running
docker run -p 3000:3000 -c /private/tmp/dumbdrop:/app/uploads dumbwareio/dumbdrop:latest
Opened localhost:3000 and uploaded a file.
A copy of that file is now sitting, unencrypted in /tmp/dumbdrop. Searched the documentation for the work encrypt and found nothing.
If you’re using docker compose, it will create a default bridge network with a CIDR that could overlap with a real network routable to the host, which messes up network egress from the container.
If this is the case it’s useful to specify the bridge network CIDR in the compose file as something you don’t use.
Sysinternals handle is lightweight unitasker for this too, better option for servers.
It’s really useful too. You can either pipe in text or for example Get-ChildItem a directory of files and it will parse them all. As usual it returns a helpful object with properties like line number.
What is 'end-to-end encrypted' about dumbdrop? I ran a quick test by running
docker run -p 3000:3000 -c /private/tmp/dumbdrop:/app/uploads dumbwareio/dumbdrop:latestOpened localhost:3000 and uploaded a file.
A copy of that file is now sitting, unencrypted in
/tmp/dumbdrop. Searched the documentation for the work encrypt and found nothing.