Backend/server setup

[endorpersand]

Enable the movement away from localStorage and local data and to a server-based backend

Benefits:

• Allows multiple devices to access the same committee, which would be good for logistics
• Chairs don't have to manually configure their own files
• Centralized management for a single conference

Harms:

• Server uptime would now be required to run CouchMUN (unless we could also pair with a local setup)
• Increased maintenance
• May require a move off of GitHub pages
• Server costs

[endorpersand]

@Zanger67

If you do decide to work on this, do look at seeing if you can bind IndexedDB alongside a cloud solution, cause the goal is to be able to run CouchMUN locally, storing all of the data through IndexedDB, but having a cloud sync system.
(Switch to IDB is #11)

Specific wrapper library for IDB used in #11 is https://dexie.org, and they have their own proprietary cloud service https://dexie.org/cloud/.
I don't think we have to use it though and there are probably other ways of doing sync besides that service.

[Zanger67]

@endorpersand @iiisong
Random thought: what if we offered storing data on Google Drive. Not sure how easy TS allows for this but had the thought while doing GCollab work.

Could reduce dependency on our end but also could act as a login process which would give auth in the process and then their records would be stored somewhere more accessible to them?

Tackles some harms: Server costs; increased maintenance; server uptime.

[endorpersand]

I don't know how much sense that makes, since the data being stored is in a database

[Zanger67]

Fair. Depends on storage method but it could be doable with import/export jsons or csvs.