-
Notifications
You must be signed in to change notification settings - Fork 332
Update docs.wire.com #3284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docs.wire.com #3284
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,17 +15,14 @@ Terminal 1: | |
| * Set up backing services: `./deploy/dockerephemeral/run.sh` | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Local testings shows that it still needs the backing databases. Maybe this line should be left in, or something to the effect of having DBs accessible.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah that's still needed no?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. oops, you're right. |
||
|
|
||
| Terminal 2: | ||
| * Compile all services: `make c` | ||
| * Run services including nginz: `./services/start-services-only.sh`. | ||
| * Build and start wire-server services: ` make c && ./services/run-services` | ||
|
|
||
| Open your browser at: | ||
| [http://localhost:8080/api/swagger-ui](http://localhost:8080/api/swagger-ui) for | ||
| the Swagger 2.0 endpoints of the latest version. This endpoint is versioned; | ||
| i.e. the Swagger docs refer to the API version. Refer to the [Swagger API | ||
| documentation](../../understand/api-client-perspective/swagger.md) regarding | ||
| Swagger and API versioning. | ||
| [http://localhost:8080/api/swagger-ui](http://localhost:8080/api/swagger-ui) for a list of API verions. | ||
|
|
||
| Swagger json is available under [http://localhost:8080/api/swagger.json](http://localhost:8080/api/swagger.json) | ||
| Also check out the docs for swagger in our staging environment: | ||
| {ref}`swagger-api-docs`. Replace the staging domain by | ||
| `localhost:8080` to get to your local build. | ||
|
|
||
|
|
||
| ## How to run federation tests across two backends | ||
|
|
@@ -211,6 +208,6 @@ Note: Simply deleting the namespaces is insufficient, because it leaves some res | |
|
|
||
| ## How to manage RabbitMQ | ||
|
|
||
| We support two different ways of managing the docker-compose instance of rabbitmq: | ||
| * A web console interface is available [here](http://localhost:15672) | ||
| We support two different ways of managing the docker-compose instance of rabbitmq: | ||
| * A web console interface is available [here](http://localhost:15672) | ||
| * `rabbitmqadmin` CLI is made available in the dev environment | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,5 @@ | ||
| (swagger-api-docs)= | ||
|
|
||
| # Swagger API documentation | ||
|
|
||
| Our staging system provides [Swagger / | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,5 @@ | ||
| #!/usr/bin/env bash | ||
|
|
||
| # Run all haskell services without immediately starting a test executable. | ||
| # Can be useful for manually poking at the API. | ||
| set -eo pipefail | ||
|
|
||
| SERVICES_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" | ||
|
|
||
| # call run-services, show a message, then sleep (instead of executing a test executable) | ||
| exec "$SERVICES_DIR/run-services" | ||
| echo -e "\n\n\n*** $0 is deprecated. please run '$SERVICES_DIR/run-services' instead.\n\n\n" | ||
| exit 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that start-services-only.sh is only calling out to run-services, should that script be removed too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, i'm worried somebody will still use it and stumble over the fact that it's gone. the way i changed it it doesn't do anything, but it'll point everybody who uses it in the right direction.