Remove traces of build.sh

This commit is contained in:
Till Faelligen 2023-01-26 13:08:46 +01:00
parent c7143176c1
commit fc02cb0d0e
No known key found for this signature in database
GPG key ID: ACCDC9606D472758
3 changed files with 3 additions and 3 deletions

View file

@ -61,7 +61,7 @@ The following instructions are enough to get Dendrite started as a non-federatin
```bash ```bash
$ git clone https://github.com/matrix-org/dendrite $ git clone https://github.com/matrix-org/dendrite
$ cd dendrite $ cd dendrite
$ ./build.sh $ go build -o bin/ ./cmd/...
# Generate a Matrix signing key for federation (required) # Generate a Matrix signing key for federation (required)
$ ./bin/generate-keys --private-key matrix_key.pem $ ./bin/generate-keys --private-key matrix_key.pem

View file

@ -24,7 +24,7 @@ After running the tests, a script will print the tests you need to add to
You should proceed after you see no build problems for dendrite after running: You should proceed after you see no build problems for dendrite after running:
```sh ```sh
./build.sh go build -o bin/ ./cmd/...
``` ```
If you are fixing an issue marked with If you are fixing an issue marked with

View file

@ -12,7 +12,7 @@ All Matrix homeservers require a signing private key, which will be used to auth
federation requests and events. federation requests and events.
The `generate-keys` utility can be used to generate a private key. Assuming that Dendrite was The `generate-keys` utility can be used to generate a private key. Assuming that Dendrite was
built using `build.sh`, you should find the `generate-keys` utility in the `bin` folder. built using `go build -o bin/ ./cmd/...`, you should find the `generate-keys` utility in the `bin` folder.
To generate a Matrix signing private key: To generate a Matrix signing private key: