>backups and such and other critical stuff.
>
>Would it be a smart to put a line of code on all my pages that reads
>something like
>
><cfif #accessibility# is "stop">
>Sorry, the site is down for critical updates. It will be up again shortly.
>(or i could have an include file).
><cfabort>
></cfif>
>
>To trigger this I could just have a variable in my application.cfm that
>states.
>
><cfset accessibility = "start">
>
>and when i want to stop access to the site i can go in and change it to:
>
><cfset accessibility = "stop">
>
>Does that seem like a smart move?
>
Why not just have a simple HTML page that gets called if CF needs to be
taken down? Unless your site is very light in its use of databases, does it
make sense for your application to be up and running if you can't access the
database? If not, the HTML page might be a better way to go. Your web server
would still be able to serve it even though CF is down, I think.
Also remember that if you're using client variables to store in the
database, then you would need your cfabort above your cfapplication tag
because that tag includes the logic to retrieve the user's vars from the
database.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
