WardCunningham/Smallest-Federated-Wiki — Issue #113: Express: Cleaning up and packaging.
Author: nrn
Created: 2012-01-31 23:10:45+00:00
State: open

I'm working on a round of cleaning up and package management stuff for the express server now that I think it's to sort of an alpha usability level. I'm making it available for global install, and i'm thinking about the best way to publish it to the npm repository, which means I new two new single word names. I'd like to propose sfw-noded for the command that goes in path, and sfwiki for the npm/node require name. This would mean that the entire process of getting a server up and running on a computer with node installed would be two commands:
npm install -g sfwiki
sfw-noded

Is this something we want to do? If so I've got to solve the problem that npm expects the package.json to be at the top level of the thing to be installed, which doesn't lend itself well to how we are organized. One possible way to solve that is by using symbolic links out from the servers to all of the shared files they include. I believe git supports this, but it may be a problem for developers on old (widows xp?) platforms. The git repo would stay organized in the same way, but the servers would access the files as if they were inside their own server/servername folder, so any server could be packaged up as it's own thing with the client for deployment.