Skip to content

Conversation

@martinbalfanz
Copy link

I really like the starting point, but I did not like opening 2 terminals. So I added a Procfile which runs the server, watch and test-watch tasks at the same time. In addition, I added a npm task which handles the file with either the foreman ruby gem or node-forman. In case you're interested... 😉

This way you can start both `watch` and `server` with a simple `npm run
dev` when you have foreman or node-forman installed.
@pheuter
Copy link
Owner

pheuter commented Mar 10, 2015

Nice, been thinking about the fact that you need to run two separate commands in separate windows during dev as well.

In the interest of keeping the skeleton minimal and not adding additional tools and requirements, I feel there may be a better way. I believe foreman depends on Ruby, and depending on Ruby just to manage a process is a bit heavy handed. There might be a more lightweight node module that supports just that.

@martinbalfanz
Copy link
Author

Yes! This is where node-foreman comes in. It's an npm module that is compatible to the ruby gem but does not rely on it. The way I added the task to the package.json it can use either the gem or the npm module, whatever is available on the system.

So it actually might be what you're looking for, but I agree on keeping things minimal.

@pheuter pheuter closed this in b910065 Mar 10, 2015
@pheuter
Copy link
Owner

pheuter commented Mar 10, 2015

Committed a simple solution using background processes, should address issue of running two separate commands during dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants