Server-side components

[xen0n]

This is blocking several important features down the road:

• Proxied package uploads
• ACL for repo maintainers
• Server-side analytics
• Various non-trivial automation for e.g. auto syncing of news items from repo to website

We need to:

• decide on an API domain e.g. api.ruyisdk.org,
• decide on a tech stack for the server-side component (e.g. still bound to Python?),
• decide where the component would live (making this repo a monorepo, or create a separate repo for that),
• provision compute nodes, and
• (optional) have a DevOps platform for CI/CD of said component.

This is gonna take a while.

[xen0n]

• Tech stack: ✅ Python web frameworks e.g. Django or Flask
• DevOps: ✅ Ansible

[xen0n]

Points suggested by @lazyparser:

• Threat model
• How to sense an attack/infiltration
• How to notify users and recover in case of the above

[xen0n]

https://github.com/ruyisdk/ruyi-backend has been created.