-
Notifications
You must be signed in to change notification settings - Fork 49
Purpose of rCTF
Aaron Esau edited this page Feb 19, 2020
·
13 revisions
We have designed rCTF with the following attributes in mind:
- scalability
- scoreboards should be cached using redis, and all analysis should be done on the backend
- the UI should be as lightweight as possible while still looking decent
- simplicity
- installations should be as easy as running a script
- deployments should be as simple as creating YAML files
- management should be made trivial using a CLI tool
- customizability
- everything about your event is configurable through a config file
- you can access data about your CTF through the CLI management tool.
- very low performance by default
- UI is not lightweight