No description
0572321b5d
Reframes the feature as an identity bridge: these emulators do not and will not speak OIDC, each ships its own login against its own auth DB, so the value is tying one SSO identity to one native account per server. That makes two former open questions answers rather than choices - one account per user per server IS the feature, and no authorization gate beyond a Drop session, since Drop access and game access already imply each other and a third check could only disagree with them. Retail TrinityCore on hold. |
||
|---|---|---|
| .github/workflows | ||
| backend | ||
| cli | ||
| desktop | ||
| docs | ||
| libraries | ||
| server | ||
| sites | ||
| torrential | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| Dockerfile | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| SECURITY.md | ||
| server.code-workspace | ||
Drop
Drop is an open-source game distribution platform, similar to GameVault or Steam. It's designed to distribute and share DRM-free games quickly, all while being incredibly flexible, beautiful, and fast.
Philosophy
- Drop is flexible. While abstractions and interfaces can complicate the codebase, the flexibility is worth it.
- Drop is secure. The nature of Drop means an instance can never be accessible without authentication. In line with #1, Drop also supports a huge variety of authentication mechanisms, from username/password to SSO.
- Drop is user-friendly. The interface is designed to be clean and simple to use, with advanced features available to users who want them.
Deployment
See our documentation on how to deploy Drop for more information.
Contributing
Please see the in-depth contributing guide. The guide includes information on how to set up the project, how to contribute code, how to report issues, and even how to effectively translate Drop.
