Re: [Savannah-hackers-public] Old frontend apache web server

2017-02-17 Thread Bob Proulx
Bob Proulx wrote:
> I am going to do a simple shutdown of the apache server on the old
> system.  That will prevent people accessing it and then any problems
> such as that will be found.
> 
> Should we instead put up a simple top level catchall page with a
> return of 503?  That would be simple enough to do.  I am inclined to
> do this.
> 
> Assaf, what do you think?

I went ahead and both shutdown the old Apache on the old frontend and
started up an Nginx on it with a configuration to load a simple Site
Moved page returning 503.  This can be easily changed.  But it should
at least alert people that they are at the wrong place now.

Bob

server {
root /var/www/site-moved;
location / {
return 503;
}
location /floating.png {
# Allow this path.
}
error_page 503 @moved;
location @moved {
rewrite .* /sitemoved.html break;
}
}



[Savannah-hackers-public] Old frontend apache web server

2017-02-17 Thread Bob Proulx
I think the new web server is working out very well.  I see no
indicators that we would return to the previous one by this point in
time.  I think it is time to stop access to the old one in order to
prevent confusion from people that are still hitting the old one.
Looking at the access logs there from mostly web crawlers on the old
one.  But there are a few other unaccounted for hits there.

I am going to do a simple shutdown of the apache server on the old
system.  That will prevent people accessing it and then any problems
such as that will be found.

Should we instead put up a simple top level catchall page with a
return of 503?  That would be simple enough to do.  I am inclined to
do this.

Assaf, what do you think?

Bob