diff --git a/docs/user-guide/contribution/rule-node-development.md b/docs/user-guide/contribution/rule-node-development.md index 932c175940..ce05a6fd7b 100644 --- a/docs/user-guide/contribution/rule-node-development.md +++ b/docs/user-guide/contribution/rule-node-development.md @@ -336,11 +336,11 @@ sudo service thingsboard restart ### UI configuration -The UI for the ThingsBoard rule nodes was configured with the help of the project that is also hosted on the official [github repo](https://github.com/thingsboard/rule-node-examples-ui). Please, refer to the following [link](https://github.com/thingsboard/rule-node-examples-ui#rule-node-examples-ui) to view how to build the project. +The ThingsBoard rule nodes UI is configured with another project in the official [github repo](https://github.com/thingsboard/rule-node-examples-ui). Please, refer to the following [link](https://github.com/thingsboard/thingsboard-rule-config-ui#thingsboard-rule-config-ui) to see build instructions. #### Running Rule Node UI container in hot redeploy mode -To running Rule Node UI container in hot redeploy mode: +To run Rule Node UI container in hot redeploy mode: - first you need to change constant **ruleNodeUiforwardPort** from **8080** to **5000** in file **server.js** that should be here: diff --git a/docs/user-guide/install/aws-marketplace-pe-upgrade-haproxy.md b/docs/user-guide/install/aws-marketplace-pe-upgrade-haproxy.md new file mode 100644 index 0000000000..be775a71a0 --- /dev/null +++ b/docs/user-guide/install/aws-marketplace-pe-upgrade-haproxy.md @@ -0,0 +1,272 @@ +--- +layout: docwithnav +title: Upgrading HAProxy Load Balancer for ThingsBoard PE from AWS Marketplace +description: Upgrading HAProxy Load Balancer for ThingsBoard PE from AWS Marketplace +hidetoc: "true" +--- + +This guide describes how to remove dockerized version of HAProxy Load Balancer and install HAProxy with Let's Encrypt +as ubuntu service for ThingsBoard Professional Edition from AWS Marketplace. + +* TOC +{:toc} + +#### Connect to your ThingsBoard PE AWS instance over SSH + +Below is example command as a reference: + +```bash +$ ssh -i ubuntu@ +``` + +or goto EC2 instances and locate your ThingsBoard PE instance. +Then select **Actions -> Connect** and follow instructions provided in **Connect To Your Instance** dialog. + +#### Remove dockerized version of HAProxy Load Balancer + +Execute the following commands to remove HAProxy docker containers and docker services: + +```bash +$ cd /usr/share/tb-haproxy && docker-compose down -v && cd ~ +$ sudo apt-get purge -y docker-engine docker docker.io docker-ce +$ sudo apt-get autoremove -y --purge docker-engine docker docker.io docker-ce +$ sudo rm -rf /var/lib/docker && sudo groupdel docker && sudo rm -rf /var/run/docker.sock +``` + +#### Install HAProxy Load Balancer package + +Execute the following commands to install HAProxy package: + +```bash +$ sudo add-apt-repository ppa:vbernat/haproxy-1.7 +$ sudo apt-get update +$ sudo apt-get install haproxy openssl +``` + +#### Install Certbot package + +Execute the following commands to install Certbot package: + +```bash +$ sudo apt-get install ca-certificates certbot +``` + +#### Install default self-signed certificate + +Execute the following commands to install default self-signed certificate: + +```bash +$ cat < /dev/null + sleep 1 + openssl req -new -key \${KEY} -passin pass:\${PASSWORD} -out \${CSR} -subj \${SUBJ} &> /dev/null + sleep 1 + cp \${KEY} \${KEY}.org &> /dev/null + openssl rsa -in \${KEY}.org -passin pass:\${PASSWORD} -out \${KEY} &> /dev/null + sleep 1 + openssl x509 -req -days 3650 -in \${CSR} -signkey \${KEY} -out \${CERT} &> /dev/null + sleep 1 + cat \${CERT} \${KEY} > \${DEFAULT_PEM} + echo \${PASSWORD} > \${HA_PROXY_DIR}/password.txt +fi +EOT +``` + +```bash +$ sudo chmod +x /usr/bin/haproxy-default-cert +$ sudo haproxy-default-cert +``` + +#### Configure HAProxy Load Balancer + +Execute the following command to create HAProxy Load Balancer configuration file: + +```bash +$ cat < \${HA_PROXY_DIR}/certs.d/\${DOMAIN}.pem +done + +# restart haproxy +exec service haproxy restart +EOT +``` + +```bash +$ cat < -

Turning the Rotating System to the left or to the right is based on which way is better and faster so that the difference between the direction of the wind and the wind turbine has to be not more than 5 degrees.

+

Turning the Rotating System to the left or to the right is based on which way is better and faster so that the angle between the direction of the wind and the wind turbine has to be no more than 5 degrees.

diff --git a/images/customers/bertil.png b/images/customers/bertil.png new file mode 100644 index 0000000000..99afdcb405 Binary files /dev/null and b/images/customers/bertil.png differ diff --git a/images/customers/iioote.png b/images/customers/iioote.png new file mode 100644 index 0000000000..88fbdbfedb Binary files /dev/null and b/images/customers/iioote.png differ diff --git a/industries/smart-city.md b/industries/smart-city.md index dd87346e33..aeb85d0b1c 100644 --- a/industries/smart-city.md +++ b/industries/smart-city.md @@ -93,3 +93,32 @@ description: + +
+ + + +
+

+ iiOOTE AB +

+

+ iiOOTE is an independent systems integrator with deep knowledge and broad international network in the IoT LPWAN ecosystem. +

+

+ During our evaluation of several different IoT platforms we decided using ThingsBoard Community Edition to quickly get started with testing of our concept solutions. Since it offers an easy way to get access to data from all our sensors and supports building dashboards for visualization. +

+

+ However, we soon discovered that ThingsBoard also fulfilled our need to build commercial services. With increasing number of sensors, customers and requirements we have migrated to ThingsBoard Professional Edition with a lot more functionality for larger deployments and multiple customers. And we will add additional servers as our customers grow. +

+
+ +
+ Bertil Moberg
+ Co-Founder & Head of IoT Solutions +
+
+
+
\ No newline at end of file diff --git a/products/thingsboard-pe/aws.md b/products/thingsboard-pe/aws.md index 62e90c9e97..166aa280a1 100644 --- a/products/thingsboard-pe/aws.md +++ b/products/thingsboard-pe/aws.md @@ -228,8 +228,8 @@ description: Step 2. Assign valid domain name system (DNS) record to your external IP address for first step.
Step 3. Connect to your instance using SSH or PuTTY using instructions from the previous questions above.
Step 4. Execute the following commands:

-     docker exec haproxy-certbot certbot-certonly --domain smth.yourcompany.com --email support@yourcompany.com
-     docker exec haproxy-certbot haproxy-refresh

+     sudo certbot-certonly --domain smth.yourcompany.com --email support@yourcompany.com
+     sudo haproxy-refresh

where smth.yourcompany.com is your DNS name from the second step
and support@yourcompany.com is your email to get notifications from certbot.

@@ -268,14 +268,14 @@ description:

Let's assume your number of devices is constantly growing and you decide to upgrade to new instance type. It is relatively easy to upgrade while you plan to use the same database type. Just execute the following steps:

-     1) stop your isntance and backup your database
-     2) start new subscription with new instance type
-     3) restore the databacse backup on the instance with new subscription
+     1) stop your instance and backup your database
+     2) start a new subscription with a new instance type
+     3) restore the database backup on the instance with a new subscription
    4) ensure everything is working as expected
    5) cancel old subscription if needed

- However, if you plan to upgrade from PostgreSQL to Cassandra this may become a chellange. - ThingsBoard team is planning to have a tool for this purpose but the release is schedule for the end of 2019. - So, we recommend to maintain the same database type or consider hybrid database approach. + However, if you plan to upgrade from PostgreSQL to Cassandra this may become a challenge. + ThingsBoard team is planning to have a tool for this purpose but the release is scheduled for the end of 2019. + So, we recommend to maintain the same database type or consider a hybrid database approach.