|
<< Click to Display Table of Contents >> Navigation: Telegram > 2020 > 05 > 26 > Telegram_2020-05-26T11 |
2020-05-26T11:41:48
Not till at least after 17.
2020-05-26T11:48:03
It's the blocker feature I need
2020-05-26T11:49:07
If I find a bug - and there are a thousand users taking lessons across the globe - there is no way to update without knocking people off
2020-05-26T11:49:46
This feature should have highest priority
2020-05-26T11:53:35
Every user has their own highest priorities. :) To do what you ask the way we want will take some time. You can implement it with a redirect page though... deploy 2 instances.. redirect all to one... then when you need to take it down redirect to the new instance.. all old users go to the old one
2020-05-26T11:54:17
for us its not a single feature but part of server manager and users will want it for all deployment methods which also takes time.. ISAPI very different than SA etc.
2020-05-26T11:54:34
Yeah, I didn't realize how critical it was in the past - because I never had more than 100 concurrent users
2020-05-26T11:55:51
it's the one killer feature of PHP - just replace a file and the next user that hits it gets the new version
2020-05-26T11:57:51
Now that I'll have thousands of concurrent users in 18 different time zones - it makes you deal with these issues on a much deeper level
2020-05-26T11:58:40
If you have one file... if you have mult PHP like most sites.. you get a mix of files as they are loaded.
2020-05-26T11:58:55
What you want you can do with a simple HTML file that redirects.
2020-05-26T11:59:16
This is why PHP packages like our forums even take themselves offline during upgrades.....
2020-05-26T11:59:43
because even during file copies you can get partial files... and very few PHP sites are a single file.. most are dozens if not hundreds.
2020-05-26T11:59:54
you've just been lucky if you think you can copy over and let users keep on old stuff....