Overview
When a new hub needs to be launched, there are various processes that must be completed across the platforms used by FKL. Some of these are for the Development Team and some are for the Deployment Team.Processes linking to a SOP marked (draft) have a page in place, but the content is still to be written.
Prerequisites
Before any Development Team or Deployment Team processes can begin, a new seller must be requested from Vivenu. This is not a Development Team responsibility, but it is a prerequisite for both teams.The Request New Seller SOP is still to be completed by Matt.
Development Team
All Development Team SOPs below apply to the production environment only. The DEV environment is configured separately in the isolated DEV sellers.
The Development Team is allotted 16 hours in total to complete the tasks in this section, replicate them in DEV, and test. This budget covers only the Development Team tasks above. It does not include the new seller request prerequisite or any of the Deployment Team tasks below. The configuration tasks above account for roughly 6 hours of that (excluding DNS propagation), leaving the majority of the window for DEV replication, verification, and testing.The SOPs above are the definite processes that must be completed, but the budget also allows buffer for the discussions that often arise: clarifying specific configuration values with the Deployment Team or Sales Team, or waiting for something to be configured. Above all, protect enough time for testing, which is the most vital part of the window.The majority of the time in a hub deployment is spent verifying the setup and testing the new hub. It is not possible to give a full list of tests, as these are done naturally with experience of the platform. The whole setup (except DNS) should be replicated in the DEV environments first, then in PROD.Once everything is configured, the main PROD test on the Vivenu / GKL side is to set up a test event in Vivenu, buy a free ticket, then buy a paid £1 ticket, and invalidate both (the paid one via a refund). The payment gateway must be set up for this test. This is not the only test on the Vivenu / GKL side, and there are also separate tests to carry out on the TalentID and telemetry sides.