A tool for tribal decentralised organisations. Read more about the concept behind it here. Realities is a part of Plato project.
We have a forum where you can start and participate in discussions around Realities and other Plato project projects.
To report a bug or suggest a specific improvement or feature, create an issue right here on GitHub.
As the codebase grows, it's important that everyone contributing to it follow the same conventions. Keeping a codebase consistent and easy to work with is hard and requires diligence. Take some time to understand the way the codebase is organized before you make your first commit. If you have suggestions as to how structure or conventions can be improved, bring it up with the community so that we can make improvements throughout the whole codebase and maintain consistency.
We use ESLint with the Airbnb config for code formatting. Before you commit, make sure you've fixed all linting errors and warnings. Don't turn off the linting rule that is giving you problems unless you really, really, really know what you're doing.
When working on a new feature, create a new git branch and collaborate with others in that branch. When the feature is tested and finished, the feature branch can be merged into master. Anything pushed to master will automatically be deployed to production. Read more...
Realities is split into a single-page web app built in React (found under ui) and a Node.js back-end that exposes a GraphQL API (found under api). Each of these have their own conventions and required reading found in the README files in their respective directories.
GraphQL is a query language developed by Facebook to replace the REST API architecture. The Realities back-end exposes a GraphQL API that the front-end uses to fetch and mutate data. In a nutshell, there is only one single API endpoint (/graphql) and the front-end sends a query to the back-end using that endpoint that describes all the data that the front-end needs to render a particular view or state. The back-end creates a response based on the query and returns all the data the front-end needs in a single http response. This reduces overfetching and makes it easy for front-end developers to change the data they fetch without having to make changes to the back-end code. Learn more about GraphQL here...
We use various libraries on the back-end to set up our GraphQL API. On the front-end, we mainly use Apollo Client to help us manage fetching and mutating data through the API.
We use Keycloak for Authentication. When a user signs up or logs in on the front-end, they are taken through a flow where Keycloak creates a Jason Web Token (JWT) that is returned to the front-end and stored in the browser. The front-end sends the JWT to the back-end with every API call in an http header. The back-end validates the JWT, fetches the user's id from it and can then determine whether the user has permission to do whatever they are trying to do.
If you run into an issue with these instructions please open an issue so that we can update them.
Realities uses a Neo4j database. You need to run Neo4j on your machine or connect to a remote database (for example a free 1000 node sandbox at http://graphenedb.com). Running a local Neo4j database is very easy, just go to https://neo4j.com/download/ and follow the instructions.
Sidenote: neo4j-desktop is very easy to use locally, but note that it is equivalent to neo4j enterprise in features, so some features that it has cannot be used when you deploy neo4j community edition, using e.g. docker, to a server. The differences between neo4j community and enterprise editions are relatively well documented in the neo4j documentation.
Set up your connection variables to Neo4j in api/.env. With Neo4j running locally, these variables should work for default setups (set DB_PASSWORD to the password you entered when creating the Neo4j database):
DB_URL=bolt://127.0.0.1:7687
DB_USERNAME=neo4j
DB_PASSWORD=We use Keycloak for authentication. For production there are e.g. docker images for this but for simple testing you can use our server, just add the env vars below to api/.env. If you run your own server you also need to set new values for the vars in ui/.env
KEYCLOAK_SERVER_URL=https://auth.platoproject.org/auth/
KEYCLOAK_REALM=plato
KEYCLOAK_CLIENT=realitiesFor parts of the app that we share with other Plato projects (such as Dreams) you also need a running instance of MongoDB. Add something like the below to api/.env
MONGO_URL=mongodb://localhost/mydbnameThen with node and npm installed run
$ npm install
$ npm startYou can also cd into the ui and api directories separately and npm start them individually. That may be more practical during development since you'll get separate logs for the front-end and back-end.
Tests in CI should run automatically but if you want to run them on your local machine you can run:
npm run test:run:servers This will launch (using docker) neo4j, mongodb, the realities API, the realities UI. It'll use fresh and temporary databases that'll disappear once you ctrl-c this command.npm test This will run the e2e tests (pretending to be a user clicking around in the app) in the terminal. While developing/debugging tests it can also be useful to run npm run test:open to get a UI where you can see what the test runner is doing in the app.This software is licensed under the AGPL license, version 3 or later. See the license file for details.