BOOTHPLORER status

Unfortunately due to issues on the web server very shortly before being ready to release the rewrite (Specifically, upgrading server software which basically has rendered it impossible to interact directly with the web server. We have pointed to a back-up directory using the web panel of our deployment software we use which should have the code as-is prior to throwing it into maintenance) we are unable to, once again, release the rewrite (albeit because outside of our control, this time).

To be able to actually finally release the rewrite we will be getting a new web server and point our DNS to the new IP of that web server when the rewrite is set up there. This will ideally be somewhere this week but free time is rather tight and it was specifically attempted on Monday because that is the easiest for us.

With that in mind, we will be getting to work once again. Apologies.

Very soon.

Performance of the new back-end code seems to be good to very acceptable. However, there have been a few consistency and speed issues with initially migrating our old database into the new database structure using our planned method of running scripts. We are assuming it is because of the sheer size (and more or less junk) from all the items we have indexed up to this point.

Because we are required to carry over all of this data into the new database structure as the data held also acts as an 'archive' of our indexing and scraping, this unfortunately means that the technical steps we need to perform to release the rewrite has to be changed to accommodate for this problem and will cause a delay that includes making some adjustments to deployment scripts.

It is worth noting that after the release of 2.0 downtimes with maintenances for future updates will be very low, as all technical debt which has caused the initial delay when 2.0 was first attempted to be released will simply not exist anymore. We apologise for the inconvinience and want to assure that it will be worth the wait.

The website will be reachable later tonight or tomorrow morning to ensure consistent stability of the website after deploying all the new code. This includes monitoring all new background jobs, all new back-end logic and migrations performed on the old database to ensure no last-minute fixes on productions are needed prior to taking the website off maintenance.

The website will be unreachable while the site is down for maintenance. This will take around a whole day.