One deployment for multiple competitions

[kirs]

From email conversation with @takluyver:

I saw that the code is meant to support multiple competitions in one deployment. I'd love to be able to set up tracking.roboticsailing.org so future competitions can use it too.

[takluyver]

Just to record the other bit of that: the challenge is logistical/financial. It's a different group of people each year finding sponsorship and organising the competition, so there's no-one to commit to maintaining a deployment for several years.

One of the things we want to organise is a kind of committee that can provide some continuity for the competition & conference organisation. If that works out, it might be able to run a deployment of the site.

[kirs]

We already have the "editions" table in the database. "WRSC 2016" is an example of an edition. Each "mission" belongs to an edition.

To reflect editions in the URL structure, do you think it makes sense to prefix URLs with the edition?

Here's how it will look like:

/wrcs-2016/teams
/wrcs-2016/missions
/wrcs-2018-spring/missions
/wrcs-2018-summer/missions

[takluyver]

That URL structure makes sense, but I wouldn't spend much time on implementing code for this unless we can figure out a way to host a deployment for several years.