Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support server-based apps #16

Open
mhkeller opened this issue Sep 14, 2015 · 0 comments
Open

Support server-based apps #16

mhkeller opened this issue Sep 14, 2015 · 0 comments

Comments

@mhkeller
Copy link
Contributor

The main issue here that needs working out is how to start and stop the sever. Let's say you have two Node-based server apps, they probably both use port 3000 so you couldn't start all servers on Aufbau launch — not to mention that wouldn't be terribly efficient to launch a bunch of server apps at once, that you might not use.

How it should work is when you click on an app, it looks to the app definition for a startCmd command, which will boot up the server. The indexPath should include the port so that should be okay. Similar to the external flag, the app should see if a startCmd field is defined and navigate to the full indexPath href instead of navigating to a file.

When you exit the app, it should kill that server process. I'm not sure about the best way to do this. Server apps don't often have an end command. Aufbau could detect the port and then kill the associated process perhaps. Open to suggestions.

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

No branches or pull requests

1 participant