-
Notifications
You must be signed in to change notification settings - Fork 700
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
fcgi support doesn't work on shared hosting services #30
Comments
I believe web.go doesn't work with unix sockets, which is a common configuration for fastcgi in hosted environments. I investigated some potential problems in the unix socket package, but that didn't lead to anything. Ill try to take another look. Thanks for reporting |
Looking into it now... |
The reason it doesn't work is that Apache expects the Go program to have a traditional After today's commit, which gives web.go the ability to control logging, this shouldn't |
Why doesn't that work? Is there an error message? |
I've been trying to switch my default Apache+PHP configuration to Apache+web.go but without any success so far. My FCGI starter script looks like this
I'm not sure how the communication works in such a configuration as there's no port specified anywhere. I just know that this would work with PHP. The only thing I get when I send a request to Apache is the status code 500 along with the following entry in my log file:
Any ideas on this? |
Many shared hosting services (ie. dreamhost for me) don't allow you to specify an external fcgi by address:port and instead using fd 0 as the listen socket for the FastCGI. It would be cool if web.go supported this mode of operation unlocking relatively cheap hosting of go applications.
The text was updated successfully, but these errors were encountered: