Thanks for your reply Hassan, yeah i kinda forgot about the front end server as its just under development. That would do indeed, i just thought there would be a more graceful way to handle this from the app side :)
On Sunday, October 11, 2015 at 2:56:53 PM UTC+1, Hassan Schroeder wrote: > > On Sun, Oct 11, 2015 at 4:19 AM, Renato Serra <[email protected] > <javascript:>> wrote: > > > I got an app that uses a remote SQL server database, this remote server > is > > sometimes unavailable and i have no control over it. > > The app only uses the database to do stuff after login in with devise. > But > > if the database is is down i cant even start the server as it just tried > to > > start the connection pool. > > Is there anyway i can get the static pages to still work when the > database > > is not working? I cant seem to find anything about this which is odd as > > servers and networks are often unstable. > > Expecting a web *application* to start normally while it's missing a > significant component seems odd to me :-) > > In any case, while you could probably do some hideous hackery to > ignore the initialization failure, why not just configure your front-end > server (nginx, httpd, whatever) to serve the static pages directly? > > FWIW, > -- > Hassan Schroeder ------------------------ [email protected] > <javascript:> > http://about.me/hassanschroeder > twitter: @hassan > Consulting Availability : Silicon Valley or remote > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/2db1ea24-526b-4315-8b6d-c50c0fa3efc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
