Server configuration on server start

[petersandor]

This is an improved version of #35

• User is prompted for settings on npm start instead of during build process
• ServerConfig wrapper class added to access settings functionality (currently extended with the initial setup function only)
• No replacing is occuring, all settings are loaded on-demand
• Includes a fix in tracking src/lib and src/spec folders

[timkurvers]

Is there an issue with these on Windows?

[petersandor]

I think this is not Windows specific, see docs

A leading slash matches the beginning of the pathname.
For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c".

See for similar scenario http://stackoverflow.com/questions/24139478/when-to-use-leading-slash-in-gitignore

[timkurvers]

Ah, it ended up ignoring src/lib and src/spec? If so, yikes! 😮

[petersandor]

Yep, I found out once after I've added new files in src/lib

[timkurvers]

Fantastic find, have adjusted blizzardry and some other repos accordingly! 👍

Could you prefix the other directories, too?

[petersandor]

Done in 55363d0

[timkurvers]

Woo, superb! 👍