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
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ To run `Blockchain-based-IoT-Server` effectively, the following system specifica
22
22
-**Storage:** 30 GB SSD minimum
23
23
-**CPU:** Dual-core processor (x86_64 or ARM64)
24
24
25
-
- Consider a URL for your IoT Server. All your users will access the IoT server web dashboard using this URL. We call it NODE_URL in this ReadMe.
25
+
- Consider a URL for your IoT Server. All your users will access the IoT server web dashboard using this URL. We call it PANEL_URL in this ReadMe.
26
26
- Consider a URL for your IoT Server's administrators. All your administrators will access the IoT server admin dashboard using this URL. We call it ADMIN_URL in the ReadMe.
27
27
28
28
_These requirements are suitable for typical IoT workloads. Actual needs may vary based on deployment scale and data volume._
- Make sure to create the certificate for domain and all subdomains
134
134
After running the command, enter your web app and admin web app domains separated by a space, like this:
135
135
```
136
-
NODE_URL ADMIN_URL
136
+
PANEL_URL ADMIN_URL
137
137
```
138
138
- The 'certbot' command generates `fullchain.pem` and `privkey.pem` in either `/etc/letsencrypt/admin.YOURDOMAIN.COM` or `/etc/letsencrypt/panel.YOURDOMAIN.COM`.
139
139
- Create the `ssl` folder inside `/etc/nginx`
@@ -142,8 +142,8 @@ sudo mkdir /etc/nginx/ssl
142
142
```
143
143
- Copy both `fullchain.pem` and `privkey.pem` into `/etc/nginx/ssl`.
0 commit comments