Runcloud.io Review

If you are looking painless server management. I would like to recommend RunCloud.io. The main reason, of course, it is Made in Malaysia!

First Class Interface

It has beautiful and easy to use User Interface.

Compatible Price

It only cost USD$10 per month. It is considered good price for the unlimited server!

Have a look now! RunCloud.io.

Windows 10 Vagrant Virtualbox with Docker Setup

I am using Windows 10. The problem once you had enable the Hype-V for Docker installation. You can’t use virtualbox for other images. It will prompt out error message if you run any images.

So I come out the solution.

  1. Install Vagrant
  2. Use Vagrant Ubuntu 16.04 Image (bento/ubuntu – which allow access vagrant via SSH)
  3. After installed ubuntu, then  I install docker. (https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-16-04)

I had reference the bridge network from virtualbox to docker and my host machine able to access to docker

https://coderwall.com/p/2rpbba/docker-create-a-bridge-and-shared-network

I share my windows folder with vagrant ubuntu image via below line:

config.vm.synced_folder "C:/www", "/vagrant_data"

Below is my Vagrantfile:-

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "bento/ubuntu-16.04"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
   config.vm.synced_folder "C:/www", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
   config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
    vb.memory = "1024"
     
     
    # Change the network adapter type and promiscuous mode
    vb.customize ['modifyvm', :id, '--nictype1', 'Am79C973']
    vb.customize ['modifyvm', :id, '--nicpromisc1', 'allow-all']
    vb.customize ['modifyvm', :id, '--nictype2', 'Am79C973']
    vb.customize ['modifyvm', :id, '--nicpromisc2', 'allow-all']
   end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
   config.vm.provision "shell", inline: <<-SHELL
     apt-get update
     apt-get install -y bridge-utils
   SHELL
end

After update my Vagrantfile, I need to run

vagrant provission && vagrant reload to update the vagrant image.

After that SSH into the vagrant image.

Creating a bridge docker1 and shared network shared_nw

# Log in to the VM
$ vagrant ssh

# Run ifconfig to check your adaptor name, normally eth0
$ ifconfig

# Delete the IP address from eth1
$ sudo ip addr del 192.168.33.10/24 dev enp0s8

# Create "shared_nw" with a bridge name "docker1"
$ sudo docker network create \
    --driver bridge \
    --subnet=192.168.33.0/24 \
    --gateway=192.168.33.10 \
    --opt "com.docker.network.bridge.name"="docker1" \
    shared_nw

# Add docker1 to eth1/enp0s8
$ sudo brctl addif docker1 enp0s8

 

Next I can run docker image attached with the new IP Address. I run with an image which is running in php 5.4 with apache.

Then I run with -v volume parameter match /vagrant_data/ with /var/www/html

docker run --rm -it -v /vagrant_data/:/var/www/html --net shared_nw --ip 192.168.33.11 php54apache

via bash access

docker run --rm -it -v /vagrant_data/:/var/www/html --net shared_nw --ip 192.168.33.11 php54apachemysqldev /bin/bash

When I go to my Windows Browser – I enter http://192.168.33.11 tata~ I able to see 403 Forbidden error means it is working fine.

 

Making the network setting permanent even after restart

The network bridge will be detached from eth1 if you
reboot the virtual machine. So here are two more things to make the setting
permanent.

Update /etc/network/interfaces like this:

auto eth1
iface eth1 inet manual
   pre-up ifconfig $IFACE up
   post-down ifconfig $IFACE down

This is how my /etc/network/interfaces look like:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback
   pre-up ifconfig $IFACE up
   post-down ifconfig $IFACE down

# The primary network interface
auto enp0s3
iface enp0s3 inet dhcp
pre-up sleep 2
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
auto enp0s8
iface enp0s8 inet static
      address 192.168.33.10
      netmask 255.255.255.0
#VAGRANT-END

 

And add the following command on /etc/rc.local(before exit 0):

brctl addif docker1 eth1

This is how the /etc/rc.local look like

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

sleep 15

brctl addif docker1 eth1

exit 0

Ubuntu is now turned into using systemd since started in Ubuntu 15.04 beta version and rc.local is “off” by default in 16.04.

You can enable rc.local by the following command and reboot your Ubuntu.

sudo systemctl enable rc-local.service

You would like to check the active status by the following command:

sudo systemctl status rc-local

 

Apache Virtual Host Setup

Next what you need to do is allow docker read from your host apache file.

You can follow the stackoverflow solution: https://stackoverflow.com/questions/31480556/edit-apache-configuration-in-docker

Thanks for reading, I hope this can help you have better environment for your coding setup

macOS Sierra install PHP7 ext-intl extension

I need to run with ext-intl with my PHP7.
However, I can’t really find a proper tutorial about this.

It actually simply to do with `brew` install.
if you already install php70 with brew first you have to remove it. In my case, I had install with ext-mcrypt. So I have removed it first

brew remove php70-mcrypt
brew remove php70

Then start my installation, with the extra parameter, it allowed me to install ext-intl

brew install php70 --with-pear

But it seem like got error…

These open issues may also help:
php70-ast 0.1.4 https://github.com/Homebrew/homebrew-php/pull/4221

Then I followed what it told.

brew install -s php70-intl

Then install back my php mycrypt extension again

brew install -s php70-mcrypt

Tata~ I have my latest php70 install with ext-intl installed. I hope this will help those need ext-intl extension installed with your php.

Happy Coding!