Consider splitting the demo in two

[josecelano]

Relates to: #72 (comment)

I'm considering splitting the demo into two, separate Tracker and Index configurations:

• To make them independently deployable.
• To make it easier for users who are only interested in the tracker.

Proposal 1

Keep this repo and create two folders, one per service (tracker, index)

Proposal 2

Create two new repos:

• torrust-tracker-demo
• torrust-index-demo

Even if they continue sharing the same domain.

I prefer proposal two, even if there is a small amount of configuration duplication.

If we deploy them using two different virtual machines, we can also evaluate the performance separately. Since we are planning to migrate to a new hosting, maybe it's a good time to do it.

cc @da2ce7 @cgbosse

[josecelano]

Subtasks

• Create repo torrust-tracker-demo
• Create repo torrust-index-demo

[josecelano]

I've forked this repo: https://github.com/torrust/torrust-tracker-demo. I will remove parts related to the Index.

[josecelano]

I have created the new server in Hetzner for the tracker using the deployer.

• Repo to track the new demo: https://github.com/torrust/torrust-tracker-demo (still empty)
• Documented deployment process: Deploy Hetzner demo tracker and document the process torrust-tracker-deployer#405

The new two trackers have been added to newtrackon

cc @da2ce7

[josecelano]

The new tracker uses MySQL (instead of SQLite) and IPv6 and IPv4.

[josecelano]

I will wait a few weeks before migrating the Index to Hetzner as well, since it's my first time using that provider and I want to check its performance/cost/UX/features/support/etc.