Point developers, managers, and client users to appropriate documentation for their use case

[vitonsky]

Build process too confused for me as end user. It is reason why it looks the project have low maintenance quality and why i will not use this on my server.

All i need to run any good VPN is only one command to start server like make start, but instead of it i have to install node and some garbage on my server.

I suggest you to improve deploy process and to do:

• add Dockerfile to build docker image with server
• add makefile with script to build docker image and to start server
• update readme with instruction what command should be started to run server

It's take 2 hour of your life to understand how docker works, but it significant improve usability and maintenance for users.

[maddyhof]

Thanks for reaching out. If I understand correctly, you're trying to install a shadowsocks server, right? If so, please refer to these instructions and reply with any specific steps that are confusing so that we can make sure to improve them.

As an alternative, you can use the Outline Manager to set up a manual server, which will prompt the same single command to install the server as the self-hosted installation instruction does.

[vitonsky]

Now i see, instructions are clear. However, my first reaction when i see the README.md is "How it works? How i can start my own server? I don't see nothing about it, so documentation are bad for long term use, thus i should not wast time on explore this repository - next".

Consider my feedback as way to improve documentation for developers like me, who trying to not wast a time on projects with bad documentation.

For me looks confused a section "Components" that have links on important documents, but not explain what "Components" is and that i should to go to links to read docs for each component. It would enough to just add this explanation, let's do it.