Community
Participate
Working Groups
Now that the builds are promoted so frequently (YEA!) to orion.eclipse.org, it's pretty common that a site I was running yesterday is not up when I go to use it today. But what happens, is that everything is redirected back to the original orion instance. The redirection is great when the site is running, but I found it confusing when the site was down. In my case I had been running a site Monday to test changes I made. On Tuesday I made some more changes, refreshed my inner site page, and the changes didn't show. So I thought my changes were bogus, and after a bit of double checking, I realized the site was down and that I was running the page from the real server. After starting my site, I got the expected results. Can we tell the user something like "The site is not running, do you want me to start it?" when a request is received for a site that has been stopped?
Agree, this would be really nice to have. One approach would be to examine the wildcard subdomains (eg. *.orion.eclipse.org) that are set in the server hosting config. If the hostname being accessed resembles a subdomain, but is not actually a running site, we report an error rather than forward the request to the real Orion server. This will at least handle the subdomain case.
Implemented the change described in Comment 2: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=f87d5377bb56162820376c678c8d4383a2996dcb Adding a prompt to start the site would also be nice, but is more complex. For now, you'll get an error message telling you the site is stopped.
Marking as fixed, see Comment 2 Opened bug 360282 for the prompt message.
