You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 15, 2025. It is now read-only.
<imgsrc="https://cloud.bitfl0wer.de/apps/files_sharing/publicpreview/2qCxoXJ27yW7QNR?file=/&fileId=1143147&x=256&y=256&a=true"align="left"alt="a purple cog, split in the middle along the horizontal axis with a gap inbetween the two halves. three overlayed, offset sinus-like waves travel through that gap. each wave has a different shade of purple"width="128px"height="auto"></img>
Specification documents and API documentation for the polyproto federated messaging protocol.
18
-
19
-
Documentation built with mkdocs-material and python3.12
9
+
Specification documents and API documentation for polyproto.
20
10
21
11
API documentation built with [TypeSpec](https://typespec.io).
22
12
23
13
## Pre-compiled OpenAPI schema(s)
24
14
25
-
Find the pre-compiled OpenAPI schema file(s) in the [`/api/build`](https://github.com/polyphony-chat/docs/tree/main/api/build) directory. The schema is automatically built and deployed to the `main` branch on every push to the `main` branch.
26
-
27
-
## File structure
28
-
29
-
The `/docs` folder has the specification documents for the polyproto protocol.
30
-
31
-
The `/snippets` folder has snippets of text used in many places in the documentation. This is to ensure consistency across the documentation. Error messages appearing in many places are also stored in the `/snippets/errors` folder.
32
-
33
-
API documentation in form of [TypeSpec](https://typespec.io) files can be found in the `/api` directory.
34
-
TypeSpec can compile to OpenAPI3, JSON Schema and Protobuf. Our TypeSpec project is targeting OpenAPI3
35
-
output. Read the TypeSpec documentation for information on how to compile TypeSpec or use a pre-compiled
36
-
version of the OpenAPI schema if you'd like.
15
+
Find the pre-compiled OpenAPI schema file(s) in the [`/build`](https://github.com/polyphony-chat/docs/tree/main/build) directory. The schema is automatically built and deployed to the `main` branch on every push to the `main` branch.
37
16
38
17
## Contributing
39
18
@@ -43,33 +22,22 @@ You should also read our [Code of Conduct](https://github.com/polyphony-chat/.gi
43
22
44
23
## Setting up a development environment
45
24
46
-
### Documentation
47
-
48
-
You will need the following things installed on your computer:
49
-
50
-
-`python3.12`
51
-
-`pip`
52
-
- Any sort of python virtual environment manager - use `venv` if in doubt
53
-
-`git`
54
-
55
-
Optionally, you can install [`vale`](https://vale.sh/) for spell-/grammar checking.
56
-
57
-
Use `pip install -r requirements.txt` to install the required dependencies, and `mkdocs build` or
58
-
`mkdocs serve` to build the project or serve it on localhost.
59
-
60
-
### API documentation
61
-
62
25
You will need the following things installed on your computer:
63
26
64
27
-`Node.js >= 20`
65
-
-`npm`,`pnpm` or `yarn`
28
+
-`npm``pnpm` or `yarn`
66
29
-`git`
67
30
-`TypeSpec` - install it globally with `npm install -g @typespec/compiler`
68
31
69
-
1. Navigate to the `/api/src` directory.
32
+
1. Navigate to the `/src` directory.
70
33
2. Select the project you want to compile. In this example, we are compiling the `core` project.
71
34
Navigate to that directory.
72
35
3. Run `tsp install` to install the dependencies.
73
36
4. Run `tsp compile .` to compile the project or `tsp compile --watch .` to automatically recompile
74
37
the project when you save a file.
75
38
5. The compiled OpenAPI3 schema will be in the `$PROJECT/tsp-output/@typespec/openapi3` directory.
0 commit comments