|
1 | | -# Graasp Backend |
| 1 | +# Graasp API |
2 | 2 |
|
3 | 3 | <!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section --> |
4 | 4 |
|
|
9 | 9 | [](https://github.com/graasp/graasp/releases/latest) |
10 | 10 |  |
11 | 11 |  |
12 | | -[](https://gitlocalize.com/repo/9284?utm_source=badge) |
| 12 | +[](https://gitlocalize.com/repo/10770?utm_source=badge) |
13 | 13 |
|
14 | | -This repository contains the source code and configurations for the Graasp backend. Visit the Graasp Platform at [graasp.org](https://graasp.org) |
| 14 | +This repository contains the source code and configurations for the Graasp API backend. Visit the Graasp Platform at [graasp.org](https://graasp.org) |
15 | 15 |
|
16 | 16 | ❓Looking for our client applications/front-ends ? |
17 | | -Head over to: [Client](https://github.com/graasp/client), [Library](https://github.com/graasp/graasp-library) |
| 17 | +Head over to: [Graasp Web](https://github.com/graasp/graasp-web), [Client](https://github.com/graasp/client), [Library](https://github.com/graasp/graasp-library) |
| 18 | + |
| 19 | +The Graasp API backend is a Node.js server (with fastify) allowing operations to be carried out in the client interface. It persists data to a PostgreSQL database. |
| 20 | + |
| 21 | +If you are interested to hosting Graasp yourself please have a look at the [self-hosting document](./docs/self-hosting.md) |
18 | 22 |
|
19 | 23 | ## Requirements |
20 | 24 |
|
21 | | -In order to run the Graasp backend, it requires: |
| 25 | +In order to run the Graasp backend, you will need: |
22 | 26 |
|
23 | 27 | - [Mise](https://mise.jdx.dev) (tool manager) |
24 | | -- [Docker](https://docs.docker.com/get-docker/) or [Podman](https://podman.io/): Docker is not necessary, it is possible to install everything locally. However it is strongly recommended to use the Docker installation guide. |
| 28 | +- [Docker](https://docs.docker.com/get-docker/) or [Podman](https://podman.io/): We recommend using docker as it makes setup of services much easier. It is however possible to setup all the services natively instead. We will provide guidance in this document for the docker installation. |
25 | 29 |
|
26 | 30 | Mise will automatically install the correct version of node and pnpm. You should only have to do: |
27 | 31 | `mise install`. You might have to trust the workspace with `mise trust` first. |
@@ -67,7 +71,7 @@ This will create 11 containers : |
67 | 71 |
|
68 | 72 | > **Troubleshoot** |
69 | 73 | > If during setup of the devcontainer you get an error like `nudenet Error pull access denied for public.ecr.aws/g...` |
70 | | -> This can occure if you previously logged in to the public ECR. When you want to pull from the public ECR, you should be unauthenticated. Simply run the following on you host: `docker logout public.ecr.aws`. It will log you out of the public ECR and you should be able to rebuild the containers without issue. If it persissts please [open an issue](https://github.com/graasp/graasp/issues/new?title=NudeNet%20DevContainer%20Docker%20Install%20Issue) |
| 74 | +> This can occur if you previously logged in to the public ECR. When you want to pull from the public ECR, you should be unauthenticated. Simply run the following on you host: `docker logout public.ecr.aws`. It will log you out of the public ECR and you should be able to rebuild the containers without issue. If it persissts please [open an issue](https://github.com/graasp/graasp/issues/new?title=NudeNet%20DevContainer%20Docker%20Install%20Issue) |
71 | 75 |
|
72 | 76 | Then install the required npm packages with `yarn install`. You should run this command in the docker's terminal, because some packages are built depending on the operating system (eg. `bcrypt`). |
73 | 77 |
|
|
0 commit comments