Closed kettanaito closed 7 years ago
I would rather follow the KSS rule. We wan't to have this project easily maintainable. We will not cover all issues, we want to cover the most problematic parts.
What we definitely need to have is better documentation with "install/usage" section, with point for changing project’s :port
number.
@janpanschab a good point. Working on the documentation right now. I will cover this aspect.
This question is no longer discussable, so I will close the issue. Required information about changing the default port will be added in the documentation.
This is rather a minor issue, but maybe you find it useful.
I would like to suggest to add a certain setup process for each new project. For example, when you just cloned the development stack and run
npm install
, guide the developer through a similar process as when creating a newpackage.json
(a list of entries awaiting for your input). This way we can allow to set a certain host alias for the project:We may take use of shell commands and this (or similar) packages: Hostile. Script will run the following when any custom input is received:
What do you think about it?