Thanks! I followed you, until the proxy_pass. What is backend1, and where is it 
defined? I know it's something you made up, but how does it know about Apache, 
or Apache about it?
> On May 12, 2016, at 17:56, Yuriy Medvedev <[email protected]> wrote:
> 
> Hi, you can use vhost in Apache and configure proxy_pass in nginx 
> configuration
> For apache2 somthing like that
> <VirtualHost *:8080>
>   ServerName foo.bar
> 
>   DocumentRoot /home/sites/
>   <Directory /home/sites/>
>       Order deny,allow
>       Allow from all
>   </Directory>
> 
>   ErrorLog  /home/sites/logs/apache_error.log
>   CustomLog /home/sites/logs/apache_access.log combined
> 
> etc.......
> </VirtualHost>
> For nginx
> server {
>     listen   80;
>     server_name foo.bar;
> 
>     access_log /home/sites/logs/nginx_access.log;
>     error_log /home/sites/logs/nginx_error.log;
> 
>     location / {
>         proxy_pass  http://backend1 <http://backend1/>;
>  etc.....
>      }
> }
> 
> 2016-05-13 0:34 GMT+03:00 Alex Hall <[email protected] 
> <mailto:[email protected]>>:
> Hello all,
> Here's what I'm trying to do. I have two sites, sd1.mysite.com 
> <http://sd1.mysite.com/> and sd2.mysite.com <http://sd2.mysite.com/>. The fun 
> part is that sd1 is a Flask app, served by Nginx. However, sd2 is OSTicket, 
> which must be served by Apache, it seems. Of course, Apache and Nginx can't 
> listen to port 80 at the same time, and as this is a subdomain on a local, 
> Windows DNS, I can't make sd2.mysite.com <http://sd2.mysite.com/> point to 
> myip:8080 or anything like that.
> 
> Thus, my best option appears to be this: Nginx listens to all incoming 
> traffic on 80. If the request is for anything to do with sd1, it handles it 
> just like it does now. However, if the request is for sd2, Nginx somehow 
> hands off the request to Apache, then returns what Apache gives it back to 
> the user.
> 
> I've heard that people use Apache and Nginx together, but I haven't found 
> anyone who uses them to serve two subdomains, with Nginx as the "gateway" and 
> handler of one subdomain, and Apache as the handler for the other subdomain. 
> Is there any way to do this? Am I even making sense? Thanks for any ideas 
> anyone has.
> 
> -- 
> Alex Hall
> Automatic Distributors, IT department
> [email protected] <mailto:[email protected]>
> 
> _______________________________________________
> nginx mailing list
> [email protected] <mailto:[email protected]>
> http://mailman.nginx.org/mailman/listinfo/nginx 
> <http://mailman.nginx.org/mailman/listinfo/nginx>
> 
> _______________________________________________
> nginx mailing list
> [email protected]
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

Reply via email to