-
Notifications
You must be signed in to change notification settings - Fork 44
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
have you seen naught? #3
Comments
Yes, I've seen it. Its an excellent and well thought-out solution, but I don't think we could merge the projects right now, since I can't have recluster handling logging. This is because I use nac to handle logging, configuration and deployment. I made this separation because I wanted nac to be able to handle all kinds of processes. Clustering needs are different in different situations: there is socket.io-compatible clustering using a proxy with up, there is simple clustering without any socket sharing for worker processes (e.g. stuff that uses rabbitmq), and then there are non-node processes which can't communicate using However I like that naught allows you to change environment variables on the fly. Have you considered not handling logging in naught? |
naught does not force its logging handling upon you. Simply avoid writing to stdout and stderr and no logs will be generated. Thanks for explaining the difference. I'll put a link to this project in naught's readme and explain the use cases when you would want to use recluster instead of naught. |
Yes, but I do want to handle stdout and stderr (e.g. in cases of uncaught exceptions), and I do handle them both with nac. So recluster simply pipes worker stdout/stderr to its own stdout/stderr, which are then captured by nac. Basically what I meant was, is it possible to add something like ... which would make naught run in non-daemon node and make stdout/stderr pass through allowing another process to handle them? If you did that, then there would be absolutely no need for recluster (except wanting to avoid IPC files, which is not much of a reason...) |
Yes I think it makes sense for naught to support those options. |
the stdout and stderr can be resolved like this: andrewrk/naught#18 --nodaemon is already an issue worth solving: andrewrk/naught#27 |
oh, nvm about stdout and stderr. I understood what you said but then immediately forgot. sorry, bad short term memory. I think we can do what you said. |
For the record, I also liked a lot of what I saw in naught, but want to keep control over stdout, because I am already handling logging and log rotation. |
just a heads up - naught now supports |
https://github.com/superjoe30/naught
looks like we should merge projects, yes?
The text was updated successfully, but these errors were encountered: