porchetta's Introduction

Porchetta Server

A bad-ass socket server for activecell. Use porchetta-client to work with on client side.

Start Server

It's so easy to start server npm start. Server accepts 2 additional params:

PORT - [default: 4000] server's port
LOG_LEVEL - [default: 1] socket.io log level: 1 - warn, 2 - info, 3 - debug

LOG_LEVEL=3 PORT=5000 npm start

Development

Use History.md and versions to log your actions.

One minute setup

npm install - to install dependencies
npm test - to run tests and ensure that all pass.
npm run watch - to start development server locally on http://localhost:4000. It restarts on every change.

Deploy

In order to deploy you need install jitsu locally (npm install -g jitsu) and login as activecell user (ask @adamrneary for password).

$ ./script/deploy-production
$ ./script/deploy-staging

This scripts helps to manage ugly nodejitsu restrictions: rewrite of package.json, and not ability to deploy staging. More control can be found on https://webops.nodejitsu.com/apps/porchetta. Available domains:

As a production server we use: https://porchetta.activecell.com/
As a staging/development server we use: https://porchetta-staging.nodejitsu.com/ (it also can be available at porchetta.activecell.net, but I didn't find valid ssl keys.)

porchetta's People

Contributors

Watchers

porchetta's Issues

Add refresh event `POST /refresh/:roomId`

[ ] use similar authentication process: #4
[ ] add refresh event to client
[ ] on activecell: post request to porchetta after data reload

Real handshake with activecell

Uncomment https://github.com/activecell/porchetta/blob/master/lib/index.js#L7

it seems, cookie authentication does not work through domains. I have another example, inspired by intercom:

On the client:

hash  = $('meta [name="user_hash"]').attr("content")
email = app.user.get('email')
query = "email=#{email}&hash_email=#{hash}"
new Porchetta(http://localhost:4000, app.company.id, { query: query })