How to Install

[jasonmaster]

does anyone know how to use this

[ghost]

+1 to that!

[1am]

+1 A short step-by-step instructions would be great.
I tried to do this but i keep getting errors like this all the time:

$ node app.js 
.---------------------------.
| * Starting Node service * |
'---------------------------'

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
Error: ENOENT, no such file or directory '/.../SandboxApp/public/app.js'
    at Object.unlinkSync (fs.js:453:18)
    at Object.<anonymous> (/.../apps/Space_Editor/app.js:97:6)
    at Module._compile (module.js:441:26)
    at Object..js (module.js:459:10)
    at Module.load (module.js:348:31)
    at Function._load (module.js:308:12)
    at Array.0 (module.js:479:10)
    at EventEmitter._tickCallback (node.js:192:40)

Where can i find the SandboxApp which seems necessary to launch the server?

[ghost]

i was getting the same error :/

[jasonmaster]

me too

[1am]

pretty please :)

[atroche]

Anyone?

[ggreer]

Here's how I got it working:

• On line 61 of app.js, I changed EDITABLE_APPS_DIR to a path that exists.
• On line 66, I changed REPLACE_SANDBOX_APP_DEMO_FILES to false.
• I installed socket.io, then changed the initialization to work with the latest version of Express. See https://github.com/visionmedia/express/wiki/Migrating-from-2.x-to-3.x for more info on how to do this.
• To work around some socket.io issues, I changed the socket.io config to try xhr and jsonp before websockets.
• I linked node_modules/now/lib/client/now.js to public/nowjs/now.js to fix a 404.

Since my changes were so extensive, I forked this project. You should be able to get my fork running with the normal npm install and npm start.

[atroche]

Thanks a lot! It's working for me. Keep up the good work.

On 20 September 2012 00:25, Geoff Greer [email protected] wrote:

Here's how I got it working:

• On line 61 of app.js, I changed EDITABLE_APPS_DIR to a path that
  exists.
• On line 66, I changed REPLACE_SANDBOX_APP_DEMO_FILES to false.
• I installed socket.io, then changed the initialization to work with
  the latest version of Express. See
  https://github.com/visionmedia/express/wiki/Migrating-from-2.x-to-3.xfor more info on how to do this.
• To work around some socket.io issueshttps://github.com/warn: client not handshaken client should reconnect socketio/socket.io#996,
  I changed the socket.io config to try xhr and jsonp before websockets.
• I linked node_modules/now/lib/client/now.js to public/nowjs/now.js
  to fix a 404.

Since my changes were so extensive, I forked this project. You should be
able to get my fork https://github.com/ggreer/Space_Editor running with
the normal npm install and npm start.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-8710738.

-- Alistair

[chaoscollective]

Thanks @ggreer for helping to turn our initial code dump of the Space editor into something more useable for others.

As you can tell, Space evolved over time as we were figuring out the best way to use different packages and structures. It could stand to be a lot more modular. We'll be sure to keep that in mind for future releases (ideally publishing to NPM with proper package.json and dependency accounting). :)

[bnkcrypt]

Hi ggreer I installed your forked version just wondering what port it uses and how to test it in the browser can someone please help ?

[ggreer]

I'd completely forgotten about this project. I ended up writing my own thing and starting a company related to it. See https://floobits.com/ and https://github.com/Floobits. Client code is open source, but the server code isn't. Sorry, gotta pay the bills. 😓