-
Notifications
You must be signed in to change notification settings - Fork 829
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
FYI: proposed FreeBSD port of h2o #145
Comments
|
Submitted to |
|
Thank you for the work! It would be OK not to install the libraries / websocket support as the library considering the fact that the API is still unstable. |
|
closing this as it's been committed as |
|
+1 having a pidfile is a good idea, yes please! It needs to handle deleting and creating the pidfile securely, though, and support dropping privileges on startup. https://github.com/freebsd/freebsd/blob/master/usr.sbin/daemon/daemon.c should be a useful reference. The other thing one can use |
|
@dch Thank you for the response and the suggestion. #152 went in before the release of 1.0.0; it is possible to use the configuration directive to let H2O emit the pid file. However, I have not designed it to create / remove the file securely in the sense that the file is created by a superuser / deleted even if the worker process exitted abnormally, as I believe such management is not kind of task every server should handle by itself. My understanding (and tendency) goes to relying on tools like With that in mind I would appreciate if you could update the ports, if necessary. Thank you in advance. |
Greetings, I have prepared a port of h2o:
https://github.com/skunkwerks/freebsd-ports/tree/master/h2o
Comments & feedback welcomed, & I will keep this ticket updated as the port goes through submission to the official ports tree.
I have not set it up to install the libraries yet, nor include websocket support. If there is interest in this I welcome contributions to the port!
The text was updated successfully, but these errors were encountered: