Currently using a db.t2.micro on eu-west, single zone.
Their pricing structure is as clear as mud, but once it was up and running it appears stable enough for our purposes and we could pretty much ignore the core db side of things (using workbench for schema management) ... until now! Trouble is their interface covers so many different types of systems and scenario that it is complex to navigate.
I started the lazy way and got an instant failure (not using the default parameter group). So I'm now creating a 5.7 instance and importing the data into that for testing (which is what I should have done in the first place
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
). I could leave the old system up in the meantime but taking it down means that I can know my dumps are still valid
As you say total luxury, being able to take the system down for a couple of weeks. In a normal year, it would be quite tricky to do so, as by the time the calendar is agreed, I need to initialise the competitions so that organisers can get the set up completed and by now we would be opening for entries. Even now most days there are a handful of people logging in.
I think the idea of listing Covid safe training facilities etc could be worth considering for the website at
www.canoeslalom.co.uk if someone gathered the information, but realistically it just doesn't make sense to add it on to the entry system.
www.canoeslalomentries.co.uk is primarily about entering and administrating entries for competitions whereas
www.canoeslalom.co.uk is the go to place for general information. I think keeping the two website roles distinct is quite important and both parts have a useful role to play.
Kit Washer, Entry Clerk, Chauffeur, Reluctant Organiser, Online Entry Advocate .....
Anything I post under this user is my personal opinion; I am not posting as a member of the Slalom Committee!