Isso commenting is an open source application that is a superior “in-place replacement” for Disqus and Facebook comments. Internally it is built with Python and SQLite. We will be running it inside a Docker container on the Google Compute Container Optimized OS. After completing the instructions in this guide, you’ll just include a snippet on your site to get Isso comments working on your site.
Let crack on to get tracking-free / ad-free commenting functionality on your site!
Set up the VM instance
Go to the Google Console for Instances and click create instance. The configuration should match the following screenshot, and the price should be free!
You should now have a free tier VM set up in the Google Cloud console. See the screenshot below, where you see instance-1 is fully set up and running.
Set up a reserved static IP address
Click here to set up a reserved static IP address for the VM instance you created. The IP that I have set up is 18.104.22.168 as displayed below.
Setting up firewall settings
Open up the Firewall rules in the Google Cloud console. You need to open the ingress port tcp:30000 for Isso use. See below for example.
Next, you will need to open up the egress port tcp:2525 for outbound mail notifications. See below for example.
Set up DNS records on your domains
Set up a subdomain A record comments.yourdomain.com that points to your new static IP address. Shown below are my settings set up on Google Domains.
Setting up email notifications for new comments
You will want notification when somebody comments on a post on your website. Google Cloud prohibits instances sending mail on SMTP ports 25, 587, and 465 making it quite difficult to use most SMTP services. We will, therefore, be using Mailgun on port 2525 instead.
The steps are as follows:
- Create a free Mailgun account
- Add a domain in Mailgun. Use the format: email.yourdomain.com
- Complete the Mailgun domain verification process. Add all the DNS A records, TXT records and other records that Mailgun requires. See the Mailgun verification settings1 and corrosponding Google Domain setup2.
- Add an authorized recipient for which email address you want to be sent comment notifications
- Keep a Mailgun open as you will use the details later on
Setting up your Isso.conf configuration file
Please familiarize yourself with the Isso configuration options by looking at the official documentation on this subject.
I have included the contents of an isso.conf configuration file, for you to use as a template. Once completed it will be set up for email notifications and logging to a file, outside of the Docker container. Please replace the values as mentioned in the inline comments.
Please leave the file paths alone as these will be defined later when you run container.
[general] dbpath = /db/comments.db # database location, do not change /db/ is a docker volume variable not a path # your website or blog (not the location of Isso!) # you can add multiple hosts for local development # or SSL connections. There is no wildcard to allow # any domain. host = http://yourdomain.com/ http://www.yourdomain.com/ https://yourdomain.com/ https://www.yourdomain.com/ http://localhost:8000 #your local website development web address notify = smtp log-file=/db/log.txt # the log file will be saved to your docker volume /db/, do not change path [server] listen = http://0.0.0.0:8080/ # inside the docker instance the commenting server will run on 8080, do not change [smtp] username = firstname.lastname@example.org # Your own Default SMTP Login in Mailgun here password = yourpassword # Your own Default Password in Mailgun here host = smtp.mailgun.org # SMTP Hostname in MailGun port = 2525 # SMTP Port in MailGun security = none # Authentication not required in MailGun to = email@example.com # The email you want to recieve the notification on from = firstname.lastname@example.org # Your own Default SMTP Login in Mailgun here timeout = 10 [guard] enabled = true ratelimit = 2 direct-reply = 30 reply-to-self = true require-author = false require-email = false
Deploying the Isso commenting software to the VM
Go back to the Google Console and start up an SSH session to the VM by clicking the SSH button. You should see a screen below.
Now you will need to upload the configuration file to the default home user folder and execute the following commands. This will create the folders that the container will use and move our configuration file to where it is going to be expected.
sudo mkdir /var/lib/docker/isso sudo mkdir /var/lib/docker/isso/db sudo mkdir /var/lib/docker/isso/conf mv isso.conf /var/lib/docker/isso/conf/isso.conf
Now pull the prebuilt Isso docker container into your VM instance.
docker pull wonderfall/isso
You should be able to run the docker container with the following command. It will be listening on port 30000.
docker run --name isso -p 30000:8080 \ --restart=always \ -e USERID=1000 -e GROUPID=1000 \ -v /var/lib/docker/isso/config:/config \ -v /var/lib/docker/isso/db:/db \ -d wonderfall/isso
You will never really have to look inside the Docker container, it will log errors to a file outside of the container. It can be treated like a black box.
Testing the ISSO server from the outside world
Test your Isso server is running and accessible with your subdomain. For example http://comments.paulness.com:30000
If you have followed all the instructions above, everything should be set up correctly. You should get a page that looks like the following.
Inserting comment snippet on your site
Now all you need to do is insert the following snippet on your own website. Just be sure to change ‘yourdomain’ to your actual domain.
<script data-isso="http://comments.yourdomain.com:30000/" data-isso-css="true" src="http://comments.yourdomain.com:30000/js/embed.min.js"></script> <section id="isso-thread"></section>
or if you are using React
Checking the log file for errors, such as if you are not receiving email notifications
# To exit the less command press either the "q" or "Q" keys. # To scroll down press the down key less /var/lib/docker/isso/db/log.txt
Restarting the docker container, after making configuration changes
# Check the currently running containers docker ps # Check the stopped containers docker ps -a # Example start of a container docker start <containerid> # Example stop of a container docker stop <containerid>
Manually backup/download comments database
Use the file download feature in SSH with the following file