Skip to content

Commit eeb4ef3

Browse files
committed
update README
1 parent d01c1c1 commit eeb4ef3

File tree

1 file changed

+11
-7
lines changed

1 file changed

+11
-7
lines changed

README.rst

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -77,13 +77,15 @@ File structure
7777
├── db_connector
7878
├── docker
7979
├── frontend
80+
├── tun
8081
└── wg-webclient
8182

8283

8384
- ``backend`` The http backend server and relay server between the charger and the users browser
8485
- ``db_connector`` A crate containing the types needed to interface with the database server
8586
- ``docker`` Files to run and build the docker containers
8687
- ``frontend`` Website that is served by the webserver
88+
- ``tun`` A cli tool able to create a WireGuard tunnel on linux platforms to a WARP Device
8789
- ``wg-webclient`` The Wireguard implementation containing also a network stack and Http and Websocket client.
8890

8991
Build
@@ -103,15 +105,17 @@ Developement build
103105
~~~~~~~~~~~~~~~~~~
104106

105107
1. Create a ``certs`` directory in ``docker/nginx`` and place a X.509 certificate and key in pem format named ``cert.pem`` and ``key.pem`` inside.
106-
2. Fill in the needed variables in the env variables. All needed variables are listed inside the .env.example files.
107-
3. build the wg-package by running ``wasm-pack build`` inside ``wg-webclient``.
108-
4. build the website by running ``npm install && npm run build`` inside ``remote-access-page``.
109-
5. start the webserver + database by running ``docker compose -f docker-compose-dev.yml up --build`` inside ``docker``.
110-
6. start the backend server by running ``cargo run`` inside ``backend``.
108+
2. Clone the warp-charger ropository
109+
3. Fill in the needed variables in the env variables. All needed variables are listed inside the .env.example files.
110+
4. build the wg-package by running ``wasm-pack build`` inside ``wg-webclient``.
111+
5. build the website by running ``npm install && npm run build`` inside ``remote-access-page``.
112+
6. start the webserver + database by running ``docker compose -f docker-compose-dev.yml up --build`` inside ``docker``.
113+
7. start the backend server by running ``cargo run`` inside ``backend``.
111114

112115
Production build
113116
~~~~~~~~~~~~~~~~
114117

115118
1. Ensure that the host is accessible via a Fully Qualified Domain Name, otherwise creating a Lets Encrypt Certificate will fail.
116-
2. Fill in the needed variables in the env file. All needed variables are listed inside the .env.example files.
117-
3. Start everything with ``docker compose up`` inside the ``docker`` directory.
119+
2. Clone the warp-charger repository to the same parent directory as this repository.
120+
3. Fill in the needed variables in the env file. All needed variables are listed inside the .env.example files.
121+
4. Start everything with ``docker compose up`` inside the ``docker`` directory.

0 commit comments

Comments
 (0)