I have had to do an install of pumpi.io a couple of times now and decided to write a script which I have put on GitHub since I only ever return after I have forgotten everything I learnt last time. The repo is,

  1. https://github.com/dfl1955/pumpiotools

The plan is that the scripts can be used to install the product, with a simple git clone and bash command. It’s not yet ready as I ran into a problem with docker.


This is my test O/S of choice. Once done let’s see if the author will take it as user contributed code. This is now working.

$ sudo bash
# apt-get update && apt-get upgrade
# apt-get install -y git
# git clone http://github.com/dfl1955/pumpiotools
# cd pumpiotools
# sudo bash ./build.me

Now I need a configure program.


The install now works fine. There is an ifaws file to perform the aws specific functions. I still need a test so we can self discover if on the amazon services. I also couldn’t get the browser to work. The server was binding to the internal host name despite using an address parameter in the config file. I stoped and returned to the bare metal install (on virtual box).

These were useful,

  1. https://stackoverflow.com/questions/20941704/ec2-instance-has-no-public-dns, this was embarassing
  2. http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
  3. https://serverfault.com/questions/462903/how-to-know-if-a-machine-is-an-ec2-instance
  4. https://stackoverflow.com/questions/22815080/get-public-dns-name-of-a-ec2-instance-using-ec2-command-line-tools-in-bash

I still have not fixed this, the jetty server is binding to the internal DNS address and thus cannot be browsed from the internet.


I wanted to install the database and application in the same container, mainly because I wanted to change as little as possible from what I know, but docker doesn’t like this. I am using mongod which recommend the use of systemd with Ubuntu. Docker, without some buggering around really prefers you to use two containers. So I plan to use AWS to test the script and then write a Docker variant which I will then place in dockerhub. The repo as at 6th June fails. I plan to finish the scripts aimed at either AWS images or virtual box VMs. I’ll then return to docker.

These links refer to the Docker issue.

  1. https://stackoverflow.com/questions/39169403/systemd-and-systemctl-within-ubuntu-docker-images
  2. https://rhatdan.wordpress.com/2014/04/30/running-systemd-within-a-docker-container/


I plan to write an ansible playbook for this. Why? Who knows? Here are some links I hope will help.

  1. https://www.ansible.com/get-started
  2. https://serversforhackers.com/an-ansible-tutorial
  3. https://valdhaus.co/writings/ansible-vs-shell-scripts/



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.