You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2018. It is now read-only.
Nick is looking to rename "server/express/bin/server". Is there a problem with that name? The name "sfw-express" seems to encode information already present in the path to the file.
Seems to me, following typical web server naming idioms, the server should be named "#{thing-it-serves}d". So sfwd would be the name.
Or perhaps since there are two servers, it should be called one of:
sfwd-express
sfw-expressd
???
I think I like that first one. When the day comes when there is a single reference server, we can rename whichever that is to sfwd
For global commands I do like the "d" at the end to denote a daemon, it helps to make sense of the commands.
I've been waiting on finishing up the package.json with a bin entry and real package versions ranges, etc. until the server/express code stops changing so much. I'm hoping it will have calmed down some in 2 weeks or so.
In the comments for pull request 98, Ward mentioned:
Seems to me, following typical web server naming idioms, the server should be named
"#{thing-it-serves}d"
. Sosfwd
would be the name.Or perhaps since there are two servers, it should be called one of:
sfwd-express
sfw-expressd
I think I like that first one. When the day comes when there is a single reference server, we can rename whichever that is to
sfwd
Also, we should look at adding a
bin
entry to thepackage.json
, so that when folks do annpm -g
install, it will install the binary in a nice place. See, for example, https://github.com/jashkenas/coffee-script/blob/master/package.jsonThe text was updated successfully, but these errors were encountered: