-mCan be passed if you want an app that does not contain the chat demo app code.
-cCan be passed if you want an app with CoffeeScript files in place of JS files.
-jCan be passed if you want an app with Jade templates instead of HTML templates.
To pass these flags, specify them after the app name:
socketstream new my_other_app -m -c -j
After you have created your app, make sure to
cd into your socketstream app, and run
npm install. Once that is done, you can then run
If you take a look at the files and folders inside a new socketstream app, they look like this:
SocketStream uses a small initial folder structure, structuring code based on whether it's client-side or server-side code. There is a node_modules folder and package.json file for module dependencies, and an app.js file which boots the SocketStream app.
Let's look at the client folder in a bit more detail:
Client-side files are organised into 5 folders:
Within the code folder, you will notice that there are two folders, app and libs:
These folder structures are flexible, and the same goes for folders inside of the static folder:
Files stores in this folder will be accessible in the web app from the root path, so an image file at
static/images/logo.png will be accessible at
Compared to the client folder structure, server-side files have a much more streamlined file structure:
Client-side files are organised into 2 folders:
It's been a long time coming, but the new version of the SocketStream site has arrived.
SocketStream has a range of plugins that you can use to build your web applications. They range from code formatters, to client-side framework extensions, and behaviour-driven development plugins.
If you've created a SocketStream plugin and would like to have it listed here, contact Paul Jensen and he will add it to the list.
TODO - provide links to all of the presentations about SocketStream
TODO - write tutorials for the following topics