Geddy app in production

[eMarek]

Hi!

I need an advice. I can not figure it out, how to use Geddy in production. I have my own server with installed Node.js and Geddy. There are two things I would like to achieve...

First, the node process should be restarted when I change one of the files. Let's say, I made some changes on one of the controllers (on the server). When I save the file, the changes should be immediatly visible on web app. There should be no need for manual restarting the app.

Second, when I log out from the server, my app just died. In other words I need to be loged in the server through the ssh otherwise my app does not work. Is the any options to use Geddy with Forever or can I somehow push the process in "background"?

I was trying with

geddy

and

geddy -e production

without success.

Thanks for help in advance.

[Joe Werle]

Have you tried creating a screen session and running it there? In a production environment it should watch the files and restart automatically

--
The official community discussion group.
website: geddyjs.org, source: https://github.com/mde/geddy, group: https://groups.google.com/d/forum/geddyjs?hl=en
 
 

--
werle

http://werle.io

@josephwerle

[Brent Westmoreland]

Can you give us an idea of what operating system your server is running as well as the version of node and geddy? 

[eMarek]

I am not familiar with screen session. I will check it out.

My configuration is:
- CentOS 6.3 server
- Node v0.8.12

- geddy @0.6.11

[Joe Werle]

I use it on my aws machine, but I use heroku for production. You should check that out too.

[eMarek]

I know Heroku, but I would like to have date on my own server.

I tried screen, it looks like it works. Thx!

Now I am looking a solution for automatic restarting the Geddy app. Any idea?

[Matthew Eernisse]

What you're describing, the code-reloading, is usually a feature you expect to see working only in development-mode. Usually in production you want to cache things, for performance reasons. Restarting the service after a deploy is pretty standard practice. Is there some special reason you need to do things differently?


M.

[Cliffano Subagio]

@eMarek , just curious, have you tried running geddy& so it runs as a background process?
  Re the code-reload, how do you push the code change? If you use git push, then you can set up receive hook which restarts your app.

@Matthew , I'm guessing it could be used as an auto-restart when a code change is pushed to prod, at the cost of losing the current state of the app. Not something I practice, but I've heard such setup.