Before you start, make sure to have Docker and Nginx installed, here’s how to do that:

To install Docker follow the steps here:
https://www.digitalocean.com/community/questions/how-to-install-and-run-docker-on-digitalocean-dorplet

To install Nginx follow the steps here:
https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-18-04

Once you have both installed, you can continue with the steps:

Step 1 - run your Docker containers

For the same of simplicity, I will run a simple and I’ll run 2 small httpd containers.

Run your first container and map port 8080 on your host:

docker run -dit --name container-1 -p 8080:80 httpd:2.4  

Now if you visit http://your-dropets-ip:8080, you should be able to see a message saying

It Works!.  

Just so that we could differentiate the two containers, let’s update the It works! message with Container 1 for example:

First get your container ID

docker ps  

Then run the following sed command to update the message:

docker exec CONTAINER_ID sed -i 's/It works!/Container 1/' /usr/local/apache2/htdocs/index.html  

This would basically run a search and replace for the It works! string and update it with Container 1 in the default index.html file in the container itself.

If you visit your Droplet's IP again in your browser the message should change from It works! to Container 1.

Let's do the same thing for container 2, but map it to port 8081 instead:

docker run -dit --name container-2 -p 8081:80 httpd:2.4  

Then agian get your container ID

docker ps  

Then run the sed command again to update the It works! message to Container 2:

docker exec CONTAINER_ID sed -i 's/It works!/Container 2/' /usr/local/apache2/htdocs/index.html  

Now if you visit http://your-dropets-ip:8081, you should be able to see a message saying Container 2.

Step 2 - Configure Nginx

Now that we have our containers up and running we can go ahead and configure our Nginx server blocks, I will go ahead and use the following two subdomain names for this example:

• container1.bobbyiliev.com
• container2.bobbyiliev.com

To keep things as simple as possible, I will create 2 server blocks with the following content:

• Server block #1:

Create a new file called container1.bobbyiliev.com.conf in the /etc/nginx/sites-available/ directory and add the following content:

server { listen 80; server_name container1.bobbyiliev.com;

location / { proxy_pass http://localhost:8080; } }  

• Server block #2:

Create a new file called container2.bobbyiliev.com.conf in the /etc/nginx/sites-available/ directory and add the following content:

server { listen 80; server_name container2.bobbyiliev.com;

location / { proxy_pass http://localhost:8081; } }  

Then once you have the two config files ready cd to the /etc/nginx/sites-enabled directory, and run the following commands:

ln -s …/sites-available/container1.bobbyiliev.com.conf .  

ln -s …/sites-available/container2.bobbyiliev.com.conf .  

Run a config test to make sure that there are no errors:

nginx -t  

And if you get Syntax OK message, restart Nginx:

systemctl restart nginx  

Note, for more information about Nginx server blocks, I would recommend taking a look at this tutorial here:
https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-server-blocks-virtual-hosts-on-ubuntu-16-04

Step 3 - Test the setup

That is pretty much it, now if I visit container1.bobbyiliev.com I should be able to see the Container 1 message and the same for container2.bobbyiliev.com.

To test that I could run a simple curl request:

curl container1.bobbyiliev.com  

You should see the following output

<h1>Container 1</h1>  

Then run the same request for container2.bobbyiliev.com:

curl container2.bobbyiliev.com  

And agian you should see the following output

<h1>Container 2</h1>  

taken from https://www.digitalocean.com/community/questions/how-to-host-multiple-docker-containers-on-a-single-droplet-with-nginx-reverse-proxy

I've also installed the netdata docker/podman. It shows me the actual fan speeds and temps in a graph. It helped me a lot to solve this issue.

podman run --privileged -d --name=netdata --restart always \
 --net="host" \
 --pid="host" \
 -v netdatalib:/var/lib/netdata \
 -v netdatacache:/var/cache/netdata \
 -v /etc/passwd:/host/etc/passwd:ro \
 -v /etc/group:/host/etc/group:ro \
 -v /proc:/host/proc:ro \
 -v /sys:/host/sys:ro \
 -v /etc/os-release:/host/etc/os-release:ro \
 --cap-add SYS_PTRACE \
 --security-opt apparmor=unconfined \
 netdata/netdata

Fan1 = CPU fan = pwm2
Fan2 = Disk 40mm fan = pwm1
The CPU fan can't be fully stopped. It wil always run minimal at ~800 rpm.
The disk fan can be fully stopped. It wil obviously show 0 rpm when stopped.

The CPU fan minimum start offset is "77" and is ~800 rpm .
The disk fan minimum start offset is "35" and is ~800 rpm (if you would like to keep it running for airflow).

CPU fan:
echo 77 >/sys/class/hwmon/hwmon0/device/pwm2

Disk fan:
echo 35 >/sys/class/hwmon/hwmon0/device/pwm1

Making this survive a reboot does indeed need the on-boot-script. I've made a simple script which surives a reboot:

Install on-boot-script
Make a file with VI called "11-set-fan-speed.sh" in /mnt/data/onboot.d/
Make the boot script executable chmod +x /mnt/data/onboot.d/11-set-fan-speed.sh
Reboot and enjoy the silence
11-set-fan-speed.sh:

!/bin/sh

echo 77 >/sys/class/hwmon/hwmon0/device/pwm2
echo 35 >/sys/class/hwmon/hwmon0/device/pwm1
I can confirm that it DOES survive a reboot. Got it working on 1.8.5. Display also shows correct values. Running stable at 44 degrees Celsius on CPU and 41 degrees Celsius board-temp.

$ netstat -nlt Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3737 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN

As we can see above port 5432 is bound to 127.0.0.1. It means any attempt to connect to the postgresql server from outside the machine will be refused. We can try hitting the port 5432 by using telnet.

Getting Started

Ghost uses something called Markdown for writing. Essentially, it's a shorthand way to manage your post formatting as you write!

Writing in Markdown is really easy. In the left hand panel of Ghost, you simply write as you normally would. Where appropriate, you can use shortcuts to style your content. For example, a list:

• Item number one
• Item number two
  • A nested item
• A final item

or with numbers!

1. Remember to buy some milk
2. Drink the milk
3. Tweet that I remembered to buy the milk, and drank it

Links

Want to link to a source? No problem. If you paste in a URL, like http://ghost.org - it'll automatically be linked up. But if you want to customise your anchor text, you can do that too! Here's a link to the Ghost website. Neat.

What about Images?

Images work too! Already know the URL of the image you want to include in your article? Simply paste it in like this to make it show up:

Not sure which image you want to use yet? That's ok too. Leave yourself a descriptive placeholder and keep writing. Come back later and drag and drop the image in to upload:

Quoting

Sometimes a link isn't enough, you want to quote someone on what they've said. Perhaps you've started using a new blogging platform and feel the sudden urge to share their slogan? A quote might be just the way to do it!

Ghost - Just a blogging platform

Working with Code

Got a streak of geek? We've got you covered there, too. You can write inline <code> blocks really easily with back ticks. Want to show off something more comprehensive? 4 spaces of indentation gets you there.

.awesome-thing {
    display: block;
    width: 100%;
}

Ready for a Break?

Throw 3 or more dashes down on any new line and you've got yourself a fancy new divider. Aw yeah.

Advanced Usage

There's one fantastic secret about Markdown. If you want, you can write plain old HTML and it'll still work! Very flexible.

That should be enough to get you started. Have fun - and let us know what you think :)