Docker version

[Thirawyn91]

Hi,
thanks for your software,
A Docker version would be a good idea and would allow for rapid deployment.

Regards
Glenn

[KeepCoolCH]

Hi Glenn

I created a docker image like you requested. You find all the information in the new readme.

You can pull the image via:

docker pull keepcoolch/dropzonefilesharing:latest

Start the container:

docker run -d \
  --name dropzonefilesharing \
  --restart=unless-stopped \
  -p 8080:80 \
  --dns 1.1.1.1 \
  --dns 8.8.8.8 \
  keepcoolch/dropzonefilesharing:latest

Then open: http://localhost:8080/

Uploads, settings, JSON files etc. are stored inside the container.

You can change the settings via http://localhost:8080/admin.php directly in the browser. The dns values in the container are needed to use the email functions.

Have fun with it. :)

Regards
Kevin

[Thirawyn91]

Hi Kevin,

Thank you for your quick response. I tested the application (via the Docker Compose file) and here are a few observations:

1- No need to specify a DNS server.
2- I'm having a problem with emails. Some emails never arrive or are marked as spam (no email receiveid after verification to gmx, gmail mailboxes).
3- It should be possible to specify a path to store the uploads that are mounted in the Docker Compose file (not in the image).
4- It should also be possible to choose the sending email address (not just the SNMP authentication). For example, I have aliases for my system emails: print, root, share...

Regards
Glenn

[KeepCoolCH]

Hi Glenn

I updated the image. Now you can define the upload folder in docker run:

  -e DROPZONE_UPLOAD_DIR=/data/uploads \
  -v ~/dropzone-uploads:/data/uploads \

or in the docker-compose.yml:

services:
  dropzonefilesharing:
    image: keepcoolch/dropzonefilesharing:latest
    container_name: dropzonefilesharing
    restart: unless-stopped
    ports:
      - "8080:80"
    environment:
      DROPZONE_UPLOAD_DIR: "/data/uploads"
    volumes:
      - ~/dropzone-uploads:/data/uploads
    dns:
      - 1.1.1.1
      - 8.8.8.8

I tried it without dns and it only works on linux machines. On my Mac setup it doesn't work without, because it can't handle native networks or macvlans.

I think the it depends on your email service what is marked as spam or not. Maybe your email service blocks external access sometimes?

Regards
Kevin

[Thirawyn91]

Thank you Kevin

I tried the new version of Docker, and here are the results of my tests:
1- The uploads directory remains /var/www/html/uploads and not /data/uploads
2- After a restart or an update of the container, I have to recreate the admin account (maybe add an option for each admin property or a configuration file stored in a mount point) like:
environment:
- TZ=Europe/Paris
- Language=DE
- AdminEmail=
...
3- Regarding emails, I confirm that the mail is rejected by SMTP for these spam reasons:

X-SPAM-STATUS: YES
X-SPAM-SCORE: 8.7
X-SPAM-RESULT: MIME_HEADER_CTYPE_ONLY=2, MISSING_MID=2.5, SUBJECT_NEEDS_ENCODING=1, MIME_HTML_ONLY=0.2, MISSING_DATE=1, MISSING_MIME_VERSION=2

Best regards,
Glenn

[savagekylo]

If you are having issues with emails being reported to spam for Gmail, make a free account on Google Postmaster Tools and follow the instructions to add the proper records to your domain's DNS records and once it's verified, it will stop auto sending your emails to the spam folder when sending to @gmail.com

I recently had to do this for two of my websites for a project I was working on. This you can use in addition to SPF, DMARC and DKIM records.

[KeepCoolCH]

Hi Glenn

I put up the new version 2.8. I reworked the SMTP configuration and added a FROM ADRESS field and also new explicit headers. Now it should work without any spam errors.

I also made shure that now you can use the DROPZONE_UPLOAD_DIR correctly. Now you can mount the uploads and inc folder in your host:

docker run -d \
  --name dropzonefilesharing \
  --restart unless-stopped \
  -p 8080:80 \
  --dns 1.1.1.1 \
  --dns 8.8.8.8 \
  -e DROPZONE_UPLOAD_DIR=/data/uploads \
  -v ~/dropzone/uploads:/data/uploads \
  -v ~/dropzone/inc:/var/www/html/inc \
  keepcoolch/dropzonefilesharing:latest

or via docker-compose.yml:

services:
  dropzonefilesharing:
    image: keepcoolch/dropzonefilesharing:latest
    container_name: dropzonefilesharing
    restart: unless-stopped
    ports:
      - "8080:80"
    environment:
      DROPZONE_UPLOAD_DIR: "/data/uploads"
    volumes:
      - ~/dropzone/uploads:/data/uploads
      - ~/dropzone/inc:/var/www/html/inc
    dns:
      - 1.1.1.1
      - 8.8.8.8

I hope this will work with your setup. Let me know. :)

Regards
Kevin

[Thirawyn91]

Kevin,
Thanks a lot, It works the score of email is now 0.9 and all datas are store in the host.
X-SPAM-STATUS: No
X-SPAM-SCORE: 0.899994
X-SPAM-RESULT: MIME_GOOD=-0.1, RPATH_DIFF_FROM=1, BAYES_HAM=-5e-06

To improve email content configuration, the HTTP protocol is hardcoded, and if we use a reverse proxy (like Nginx), the site will use HTTPS. Is it possible to hardcode the site's URL in the configuration page? This would also affect the behavior if the external domain is different from the local domain.

Otherwise, in the admin.php page, every time we save the configuration, the web page reloads continuously (unless we select "stop" in the popup).

Regards
Glenn

[KeepCoolCH]

Thanks for your inputs, that helps a lot. 👍🏻
I changed the reload method in the admin.php now it should as expected. :)
The nginx reverse proxy should now be recognized.

I hope this helps. 💯

[Thirawyn91]

It 's Ok now for the reload but not for the https discover.

You can test https://keepcoolch.lauer.fr/

;)

[KeepCoolCH]

Ah now i think i know what you mean: the link generation for the download/verification doesn't match with the http/https scheme? i already fixed it so that it recognizes the https scheme from the proxy. i tested it with nginx proxy manager and it worked. let me know if it works for you now. :)

[Thirawyn91]

Thank you Kevin, the email was successfully sent with an HTTPS link.

[KeepCoolCH]

Great 😎👍🏻