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
Copy file name to clipboardExpand all lines: README.md
+18-11Lines changed: 18 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,46 +8,52 @@ Official docker images are available at [Docker Hub](https://hub.docker.com/r/tr
8
8
9
9
For a successful startup, Wannabe requires the configuration and SSL certificate files.
10
10
11
-
For information on configuration see the [Configuration](#configuration) section. You must generate and use the self-signed SSL certificate for Wannabe to securely proxy HTTPS requests to other servers. It's crucial to ensure that the client's operating system, whether on a local machine or within a containerized environment, trusts the SSL certificate for secure communication with Wannabe. For guidance on adding the SSL certificate to your operating system and configuring trust settings, please refer to the relevant documentation.
11
+
For information on configuration, see the [Configuration](#configuration) section. Wannabe comes with a built-in self-signed SSL certificate that can be used out of the box for securely proxying HTTPS requests to other servers. It's crucial to ensure that the client's operating system, whether on a local machine or within a containerized environment, trusts the SSL certificate for secure communication with Wannabe. You can find the built-in certificate and its key in the `certs` folder of this repository. For guidance on adding the SSL certificate to your operating system and configuring trust settings, please refer to the relevant documentation.
12
+
13
+
However, if you prefer to use your own custom SSL certificate, you have the option to generate and use a self-signed certificate. See the [Running as a standalone server](#running-as-a-standalone-server) or [Running in docker](#running-in-docker) sections for details on how to use your own custom SSL certificate.
Like any Go program, Wannabe can be launched by simply cloning the repository, adding a `config.json`, `wannabe.crt` and `wannabe.key` to the root of the cloned repository, compiling the source code into an executable binary file using the `go build` command, and then running the program with the `go run` command.
29
+
Like any Go program, Wannabe can be launched by following these steps:
30
+
1. Clone the repository.
31
+
2. Add a `config.json` file to the root of the cloned repository.
32
+
3. Use either the built-in certificate `wannabe.crt` and its key `wannabe.key` in the `certs` folder of the repository, or overwrite both certificate files with your own custom certificate and key.
33
+
4. Compile the source code into an executable binary file using the `go build` command, then run the program with the `./wannabe` command (or `wannabe.exe` on Windows).
28
34
29
35
### Running in Docker
30
36
31
37
Wannabe provides official [Docker images](https://hub.docker.com/r/trco/.wannabe) for running the application within a container.
32
38
33
-
To ensure a successful launch of the application, the configuration `.json` file and SSL certificate `.crt` and `.key` files should be mounted from the host operating system to the `/usr/src/app` directory of the Wannabe container. The environment variables `CONFIG_PATH`, `CERT_PATH`, and `CERT_KEY_PATH`should be set to the paths where the relevant files are mounted. Inside the container, the Wannabe server operates on port 6789, and the API is accessible through port 6790.
39
+
To ensure a successful launch of the application, the configuration `.json` file should be present at the defined `CONFIG_PATH` environment variable. In case of using your own custom SSL certificate, the certificate `.crt` and key `.key` files should be present at the defined `CERT_PATH` and `CERT_KEY_PATH` environment variables. Inside the container, the Wannabe server operates on port 6789, and the API is accessible through port 6790.
34
40
35
41
```
36
42
// pull the latest Wannabe image from Docker Hub
37
43
docker pull trco/wannabe
38
44
```
39
45
40
46
```
41
-
// run Wannabe container using config.json and SSL certificate files wannabe.crt and wannabe.key
47
+
// example of running Wannabe container using config.json and custom SSL certificate files
@@ -630,4 +636,5 @@ Your pull request will be reviewed, and you may be asked to make further changes
630
636
If you're eager to contribute to Wannabe but aren't sure where to begin, we've got you covered! You can dive right in by exploring our open issues or checking out our existing "next step" ideas. Simply head over to the Issues tab to get started!
631
637
632
638
## Author
633
-
Uroš Trstenjak (Trčo), [github.com/trco](https://github.com/trco), [Connect on LinkedIn](https://www.linkedin.com/in/uros-trstenjak/).
639
+
Uroš Trstenjak (Trčo), [github.com/trco](https://github.com/trco), [Connect on LinkedIn](https://www.linkedin.com/in/uros-trstenjak/).
0 commit comments