how to prevent access during upgrade

how to prevent access during upgrade

How do you prevent user access when you require sole access to the webERP app or the database server for some reason. E.g. upgrade, patch, restore database backup, etc.

Is there any built-in facility for dealing with "temporarily out of order, please come back later." Can anyone share a procedure that works for them? Is anyone bringing up a new server, synchronizing databases, and cutting over live? Not that I want to, but I'd like to know in case I need to some day.

Re: how to prevent access during upgrade

hi. see manual docs, source and you will see that weberp alreary have flags that controls when update (soon after login) and if is setup in config panel for automatic update.

in my installs i use .htaccess file for setup a message with aditional locale messages for restricted access (only users that have user/password created for apache2 .htaccess) can reach on weberp login screen.

How do you prevent user access when you require sole access to the webERP app or the database server for some reason. E.g. upgrade, patch, restore database backup, etc.

Is there any built-in facility for dealing with "temporarily out of order, please come back later." Can anyone share a procedure that works for them? Is anyone bringing up a new server, synchronizing databases, and cutting over live? Not that I want to, but I'd like to know in case I need to some day.

How do you prevent user access when you require sole access
to the webERP app or the database server for some reason. E.g.
upgrade, patch, restore database backup, etc.

Is there any built-in facility for dealing with
"temporarily out of order, please come back later." Can anyone
share a procedure that works for them? Is anyone bringing up a
new server, synchronizing databases, and cutting over live?
Not that I want to, but I'd like to know in case I need to
some day.

Cheers!

Dale

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

If anyone is wondering about the persistently nasty comments made by Tim Schofield and wants the full story please see:
http://timschofield.blogspot.com/
Hell hath no fury like a woman (or Tim) scorned

Re: how to prevent access during upgrade

Can you say anything about how big a deal it is to run OPTIMIZE TABLE periodically? How “bad” does it get if you don’t OPTIMIZE TABLE periodically, and in what sort of context? (e.g. number of users/items/orders). How long can it take OPTMIZE TABLES take to run? I’m aware I’m asking a loaded question and “it depends”, but any generalities? Fwiw, my server is an old dual-core desktop with 8GB RAM. I just forced DB_Maintenance to run now and the delay until “fully logged in” was long enough I might have appreciated a “sorry for the delay” notice.

Also, the manual recommends scheduling DB_Maintenance as a cron job, but doesn’t say how. I can use wget and a URL to execute a *.php file, but how do you execute just one function from within an *.inc file? Or would you put a mysql command directly into the cron table (with the query given as an argument to the mysql command)?

How do you prevent user access when you require sole access to the webERP app or the database server for some reason. E.g. upgrade, patch, restore database backup, etc.

Is there any built-in facility for dealing with "temporarily out of order, please come back later." Can anyone share a procedure that works for them? Is anyone bringing up a new server, synchronizing databases, and cutting over live? Not that I want to, but I'd like to know in case I need to some day.

Re: how to prevent access during upgrade

hi. global providers already take care for this kind of infra-estructure. hostgator.com are very ok with shared hosts only about US 7,00 by month.

Any way, you do not need run any concerns about performance related about mysql 5.5 or 5.6 or 5.7. for local pc or intranet pc allways pain is pc or server that run this main if are running all this on windows. triple checks.

Can you say anything about how big a deal it is to run OPTIMIZE TABLE periodically? How “bad” does it get if you don’t OPTIMIZE TABLE periodically, and in what sort of context? (e.g. number of users/items/orders). How long can it take OPTMIZE TABLES take to run? I’m aware I’m asking a loaded question and “it depends”, but any generalities? Fwiw, my server is an old dual-core desktop with 8GB RAM. I just forced DB_Maintenance to run now and the delay until “fully logged in” was long enough I might have appreciated a “sorry for the delay” notice.

Also, the manual recommends scheduling DB_Maintenance as a cron job, but doesn’t say how. I can use wget and a URL to execute a *.php file, but how do you execute just one function from within an *.inc file? Or would you put a mysql command directly into the cron table (with the query given as an argument to the mysql command)?

How do you prevent user access when you require sole access to the webERP app or the database server for some reason. E.g. upgrade, patch, restore database backup, etc.

Is there any built-in facility for dealing with "temporarily out of order, please come back later." Can anyone share a procedure that works for them? Is anyone bringing up a new server, synchronizing databases, and cutting over live? Not that I want to, but I'd like to know in case I need to some day.

Re: how to prevent access during upgrade

I am not sure it makes a big difference with innodb tables to be
brutal. Given the delay I've stopped using it. Adding the commands
to a cron job directly on the server at some off peak time seems
more sensible.

Can
you say anything about how big a deal it is to run OPTIMIZE
TABLE periodically? How “bad” does it get if you don’t
OPTIMIZE TABLE periodically, and in what sort of context?
(e.g. number of users/items/orders). How long can it take
OPTMIZE TABLES take to run? I’m aware I’m asking a loaded
question and “it depends”, but any generalities? Fwiw, my
server is an old dual-core desktop with 8GB RAM. I just
forced DB_Maintenance to run now and the delay until “fully
logged in” was long enough I might have appreciated a “sorry
for the delay” notice.

Also,
the manual recommends scheduling DB_Maintenance as a cron
job, but doesn’t say how. I can use wget and a URL to
execute a *.php file, but how do you execute just one
function from within an *.inc file? Or would you put a mysql
command directly into the cron table (with the query given
as an argument to the mysql command)?

How
do you prevent user access when you require sole
access to the webERP app or the database server for
some reason. E.g. upgrade, patch, restore database
backup, etc.

Is
there any built-in facility for dealing with
"temporarily out of order, please come back later."
Can anyone share a procedure that works for them? Is
anyone bringing up a new server, synchronizing
databases, and cutting over live? Not that I want
to, but I'd like to know in case I need to some day.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

If anyone is wondering about the persistently nasty comments made by Tim Schofield and wants the full story please see:
http://timschofield.blogspot.com/
Hell hath no fury like a woman (or Tim) scorned