GraphQL API and utilities for the rpdata project
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Gisle Aune 8a313b3bb2 More destruction. Utils too, since they cause weird go mod shenanigans. 5 years ago
cmd/rpdata-server More destruction. Utils too, since they cause weird go mod shenanigans. 5 years ago
database A lot of delete and failed scream tests. 5 years ago
graph2 A lot of delete and failed scream tests. 5 years ago
internal A lot of delete and failed scream tests. 5 years ago
models More destruction. Utils too, since they cause weird go mod shenanigans. 5 years ago
repositories A lot of delete and failed scream tests. 5 years ago
services A lot of delete and failed scream tests. 5 years ago
space Early work on file stuff. 5 years ago
.drone.yml Removed docker build on non-tag push from CI 6 years ago
.gitignore no idea 5 years ago
Dockerfile More destruction. Utils too, since they cause weird go mod shenanigans. 5 years ago
LICENSE.md Long overdue initial commit 7 years ago
README.md git: readme 6 years ago
config.example.json Long overdue initial commit 7 years ago
go.mod More destruction. Utils too, since they cause weird go mod shenanigans. 5 years ago
go.sum More destruction. Utils too, since they cause weird go mod shenanigans. 5 years ago
tools.go Added character service and such. 6 years ago

README.md

RPData API

Project RPData aims to centralize the AiteRP applications, and partially involve the wiki into a common API. This will allow for easy linking and inlining between them. The primary consumers of this API will be the Logbot and the upcoming RPData website.

There is some renovation going on, and the packages model and graphql are going to be superceded by models and graph2