mirror of
https://github.com/logos-messaging/docs.waku.org.git
synced 2026-01-02 12:53:12 +00:00
Add git branching instructions (#238)
* docs: fix wakudev hostname * Add git branching instructions --------- Co-authored-by: Anton Iakimov <yakimant@gmail.com>
This commit is contained in:
parent
f83a184421
commit
bc618877de
@ -94,3 +94,11 @@ yarn clear
|
|||||||
The hosting is done using [Caddy server with Git plugin for handling GitHub webhooks](https://github.com/status-im/infra-misc/blob/master/ansible/roles/caddy-git).
|
The hosting is done using [Caddy server with Git plugin for handling GitHub webhooks](https://github.com/status-im/infra-misc/blob/master/ansible/roles/caddy-git).
|
||||||
|
|
||||||
Information about deployed build can be also found in `/build.json` available on the website.
|
Information about deployed build can be also found in `/build.json` available on the website.
|
||||||
|
|
||||||
|
## Change Process
|
||||||
|
|
||||||
|
1. Create a new working branch from develop: git checkout develop; git checkout -b my-changes.
|
||||||
|
2. Make your changes, push them to the origin, and open a Pull Request against the develop branch.
|
||||||
|
3. After approval, merge the pull request, and verify the changes on the staging server (e.g., https://dev.vac.dev).
|
||||||
|
4. When ready to promote changes to the live website, rebase the master branch on the staging changes: git checkout master; git pull origin master; git rebase origin/develop; git push.
|
||||||
|
|
||||||
|
|||||||
@ -109,7 +109,7 @@ Notice that the two `nwaku` nodes run the very same version, which is compiled l
|
|||||||
|
|
||||||
#### Comparing archive SQLite & Postgres performance in [nwaku-b6dd6899](https://github.com/waku-org/nwaku/tree/b6dd6899030ee628813dfd60ad1ad024345e7b41)
|
#### Comparing archive SQLite & Postgres performance in [nwaku-b6dd6899](https://github.com/waku-org/nwaku/tree/b6dd6899030ee628813dfd60ad1ad024345e7b41)
|
||||||
|
|
||||||
The next results were obtained by running the docker-compose-manual-binaries.yml from [test-waku-query-c078075](https://github.com/waku-org/test-waku-query/tree/c07807597faa781ae6c8c32eefdf48ecac03a7ba) in the sandbox machine (metal-01.he-eu-hel1.wakudev.misc.status.im.)
|
The next results were obtained by running the docker-compose-manual-binaries.yml from [test-waku-query-c078075](https://github.com/waku-org/test-waku-query/tree/c07807597faa781ae6c8c32eefdf48ecac03a7ba) in the sandbox machine (metal-01.he-eu-hel1.misc.wakudev.status.im.)
|
||||||
|
|
||||||
**Scenario 1**
|
**Scenario 1**
|
||||||
|
|
||||||
@ -155,7 +155,7 @@ In this case, the performance is similar regarding the timings. The store rate i
|
|||||||
|
|
||||||
This nwaku commit is after a few **Postgres** optimizations were applied.
|
This nwaku commit is after a few **Postgres** optimizations were applied.
|
||||||
|
|
||||||
The next results were obtained by running the docker-compose-manual-binaries.yml from [test-waku-query-c078075](https://github.com/waku-org/test-waku-query/tree/c07807597faa781ae6c8c32eefdf48ecac03a7ba) in the sandbox machine (metal-01.he-eu-hel1.wakudev.misc.status.im.)
|
The next results were obtained by running the docker-compose-manual-binaries.yml from [test-waku-query-c078075](https://github.com/waku-org/test-waku-query/tree/c07807597faa781ae6c8c32eefdf48ecac03a7ba) in the sandbox machine (metal-01.he-eu-hel1.misc.wakudev.status.im.)
|
||||||
|
|
||||||
**Scenario 1**
|
**Scenario 1**
|
||||||
|
|
||||||
@ -217,7 +217,7 @@ The `db-postgres-hammer` is aimed to stress the database from the `select` point
|
|||||||
|
|
||||||
#### Results
|
#### Results
|
||||||
|
|
||||||
The following results were obtained by using the sandbox machine (metal-01.he-eu-hel1.wakudev.misc) and running nim-waku nodes from https://github.com/waku-org/nwaku/tree/b452ed865466a33b7f5b87fa937a8471b28e466e and using the `test-waku-query` project from https://github.com/waku-org/test-waku-query/tree/fef29cea182cc744c7940abc6c96d38a68739356
|
The following results were obtained by using the sandbox machine (metal-01.he-eu-hel1.misc.wakudev) and running nim-waku nodes from https://github.com/waku-org/nwaku/tree/b452ed865466a33b7f5b87fa937a8471b28e466e and using the `test-waku-query` project from https://github.com/waku-org/test-waku-query/tree/fef29cea182cc744c7940abc6c96d38a68739356
|
||||||
|
|
||||||
The following shows the results
|
The following shows the results
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user