Dockerfile : various updates

[pascalandy]

Hello folks,

I see the Dockerfile needs some love.

Before contributing and pushing a PR, I would like to know your feedbacks before to do so.
Should I use a daily branch or create mine?

EDIT: To update

• Node LTS is at v10
• Shadowsocks is at v3.2.3
• yarn is at v1.12.3
• user permissions

Aggregate RUN commands

I would suggest combining many bash commands under the same RUN to minimize the number of layers in the Docker image.

Question

I don't see a CICD setup like Travis around. Is there one?

[trevj]

@pascalandy Again, thanks for trying Outline. Yes, our Dockerfile could use some love. To answer your questions, and some random comments:

• For various reasons we've stalled at Node 8 - see Update from alpha-series Cloud Functions to beta #284. If it works with Node 10 then great but just beware you might run into weird, time-sucking issues.
• We recently moved the server off of shadowsocks-libev and will be removing it very soon so please don't spend effort here.
• Absolutely, fewer layers == better.
• We make extensive use of Travis. All our Docker images are built there:
  • https://github.com/Jigsaw-Code/outline-server/blob/master/.travis.yml
  • https://travis-ci.org/Jigsaw-Code/outline-server

As for PRs I think the easiest/best approach is just to fork off master. We don't both much with feature branches.

[pascalandy]

Thanks, with all these info, I'll give it a shoot :)

[fortuna]

FYI, we've made several updates to the Dockerfile since this issue was posted, including updating and removing some dependencies, and changing file permissions.