mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00

* Reorganized docs * Fixed internal links in basic usage * fixed the docker-compose command and volume for docs * fixed docs tests * fix travis docs test * tox ini file * fixed readme localhost links * edited tox and test docs to previous state * Fix tests errors related to docs reorganization Signed-off-by: David Dashyan <mail@davie.li> * Added ansible script installation option Signed-off-by: Lana Ivina <lana@ipdb.io> * Added ansible script to network setup guide Signed-off-by: Lana Ivina <lana@ipdb.io> * Hid the non-working button for now. Signed-off: Lana Ivina <lana@ipdb.io> * Try now button Co-authored-by: David Dashyan <mail@davie.li>
1.4 KiB
1.4 KiB
Set Up NGINX
If you don't want HTTPS (for communications between the external world and your node), then you can skip all the NGINX steps on this page.
Note: This simple deployment template uses NGINX for more than just HTTPS. For example, it also does basic rate limiting.
Install NGINX
SSH into your machine and install NGINX:
sudo apt update
sudo apt install nginx
Configure & Reload NGINX
Get an SSL certificate for your node's subdomain (such as bnode.example.com
).
- Copy the SSL private key into
/etc/nginx/ssl/cert.key
- Create a "PEM file" (text file) by concatenating your SSL certificate with all intermediate certificates (in that order, with the intermediate certs last).
- Copy that PEM file into
/etc/nginx/ssl/cert.pem
- In the
bigchaindb/bigchaindb repository on GitHub,
find the file
nginx/nginx.conf
and copy its contents to/etc/nginx/nginx.conf
on your machine (i.e. replace the existing file there). - Edit that file (
/etc/nginx/nginx.conf
): replace the two instances of the stringexample.testnet2.com
with your chosen subdomain (such asbnode.example.com
). - Reload NGINX by doing:
sudo service nginx reload