How CloudFlare helps to painless migrate your WordPress website to HTTPS?

facebooktwittergoogle_pluslinkedinmailby feather


Google recently announced that, Chrome will alert “NOT SECURE” for the websites not running under HTTPS:
Starting October 2017, Chrome (version 62) will show a “NOT SECURE” warning when users enter text in a form on an HTTP page, and for all HTTP pages in Incognito mode.
In case you have a WordPress site, there are 2 main ways to do that:
1- Converting WordPress to HTTPS mode:
1-a: Change the site URL: The siteurl can only be changed by command line. Find the wp-config.php and update it.
1-b: Change the existing http links: Go to DB and update the links. Beside in case there are plugins which inject their code seperately, you need find all. This is very painful!
1-c: Create a SSL certificate and verify it on a certificate authority.
2- Keeping WordPress a usual and use CloudFlare:
2-a Force HTTPS
2-b Enable HTTPS Rewrite: This is the crucial point. By that, you do not need to edit WordPress http links, as CloudFlare will be replacing them on the fly! (In case you are not under HSTS, it will not replace image links)


2-c Now you should see that links except images are not converted on the fly. Go to and register your domain for HSTS.

**** Be careful! All subdomains and subsubdomains from now on should work under https! ****

So check all your DNS records. With Coudflare, you are lucky, if traffic passes via CloudFlare, it will a common SSL certificate



Rancher on Google Cloud with Cloud SQL as DB

facebooktwittergoogle_pluslinkedinmailby feather

Here is my latest kloia blog post:

Kubernetes on Rancher with Weave

facebooktwittergoogle_pluslinkedinmailby feather

Here is my post on kloia blog:

Docker Routing Mesh

facebooktwittergoogle_pluslinkedinmailby feather

Routing Mesh is not magic, it just uses ha-proxy inside to route the traffic to the related container.

What is the use-case of Routing Mesh? 

You have plenty of services/apps working on HTTP/HTTPS and you do not want to deal with ports. Routing Mesh simply, manages the "Virtual Hosting" 

1. In case you have Docker Datacenter UCP: 

Step1: Enable Routing Mesh

UCP –> Admin Settings –> Routing Mesh –> Enable HTTP Routing Mesh –> Update (I used port 8090 just for test, normally it should be 80)


Step2: Create a service

UCP –> Resources –> Services –> Create a Service 

Service Name: meshtest

Image Name: nginx:latest

Next –> Rosources –> Networks

Choose the network "ucp-hrm"

Next –> Environment

Create a Service Label "com.docker.ucp.mesh.http.80" with label "external_route=http://meshtest,internal_port=80"


2. In case you just have Docker 1.12+:

Add the following to you docker-compose YAML under the necessary service:

#    labels:
#      com.docker.ucp.mesh.http.80=external_route=http://meshtest,internal_port=80




Save Settings and it works!



Docker overlay or bridge networks overlapping with the corporate networks problem

facebooktwittergoogle_pluslinkedinmailby feather

During the installation of Docker Engine and UCP(Universal Control Plane), there is a risk that the networks it chooses by default like,,, may overlap with your existing LANs in your organization. Although there are some related posts:

IMHO they do not provide a practical solution for that particular case…

Beside, there are the following open issues under github:

Here is a workaround we have founded and applied and working:

  • Before the installtion of Docker Engine/UCP, create a virtual interface or extend the netmask of the current interface covering all corporate networks:
ifconfig eth0:0 <yourinternalcorporateIPAddress> netmask <netmask> up
  • After you finalize the Docker Engine, swarm or UCP, you will notice that it uses A Class(10.x.x.x/x) or C Class(192.168.x.x/x) rather than 172.x.x.x !!!! Docker installation is smart that it jumps to other network classes.
  • Revert back your network interface you the initial state ad that's all!! 


“Your engine version 1.12.3 OSS is too old. UCP requires at least version 1.12.1 CS or 1.13.0 OSS” error while installing Docker Datacenter UCP

facebooktwittergoogle_pluslinkedinmailby feather

You need to install 1.21.1 CS(Commercial Support) version of the Docker Engine specific commercial version, in case Ubuntu, here is the way to do that:

sudo rpm –import ""

curl -s '' | sudo apt-key add –import

sudo apt-get update && sudo apt-get install apt-transport-https

sudo apt-get install -y linux-image-extra-$(uname -r) linux-image-extra-virtual

echo "deb ubuntu-trusty main" | sudo tee /etc/apt/sources.list.d/docker.list

sudo apt-get update && sudo apt-get install docker-engine=1.12.1~cs1-0~trusty

docker info

service docker restart

Jenkins quick install guide on CentOS to be used for automated provisioning

facebooktwittergoogle_pluslinkedinmailby feather

You can use the following for Ansible, Docker, ebextensions or any automated provisioning you need. The first command especially saves time otherwise you have to click on "Accept license" on browser in order to download from Oracle…

# wget –no-check-certificate –no-cookies –header "Cookie: oraclelicense=accept-securebackup-cookie"
# rpm -Uvh jdk-8u102-linux-x64.rpm
# alternatives –install /usr/bin/java java /usr/java/latest/bin/java 200000
# alternatives –install /usr/bin/javac javac /usr/java/latest/bin/javac 200000
# alternatives –install /usr/bin/jar jar /usr/java/latest/bin/jar 200000
export JAVA_HOME="/usr/java/latest/"
# wget -O /etc/yum.repos.d/jenkins.repo
# rpm –import
# yum update -y
# yum install jenkins -y
# systemctl enable jenkins.service
systemctl restart jenkins.service

How Docker helped me to overcome with the development environment headaches

facebooktwittergoogle_pluslinkedinmailby feather

Another typical error happened during i tried to install a new Python module:

Deryas-MacBook-Pro:etugra dsezen$ sudo pip install zeep

The directory '/Users/dsezen/Library/Caches/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

You are using pip version 7.1.0, however version 8.1.2 is available.

You should consider upgrading via the 'pip install --upgrade pip' command.

The directory '/Users/dsezen/Library/Caches/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

Collecting zeep

  Downloading zeep-0.14.0-py2.py3-none-any.whl (65kB)

    100% |████████████████████████████████| 65kB 245kB/s 

Requirement already satisfied (use --upgrade to upgrade): lxml>=3.0.0 in /Library/Python/2.7/site-packages (from zeep)

Requirement already satisfied (use --upgrade to upgrade): pytz in /System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python (from zeep)

Requirement already satisfied (use --upgrade to upgrade): appdirs>=1.4.0 in /Library/Python/2.7/site-packages (from zeep)

Requirement already satisfied (use --upgrade to upgrade): cached-property>=1.0.0 in /Library/Python/2.7/site-packages (from zeep)

Requirement already satisfied (use --upgrade to upgrade): defusedxml>=0.4.1 in /Library/Python/2.7/site-packages (from zeep)

Collecting six>=1.9.0 (from zeep)

  Downloading six-1.10.0-py2.py3-none-any.whl

Collecting isodate>=0.5.4 (from zeep)

Collecting requests>=2.7.0 (from zeep)

  Downloading requests-2.11.1-py2.py3-none-any.whl (514kB)

    100% |████████████████████████████████| 516kB 283kB/s 

Installing collected packages: six, isodate, requests, zeep

  Found existing installation: six 1.4.1

    DEPRECATION: Uninstalling a distutils installed project (six) has been deprecated and will be removed in a future version. This is due to the fact that uninstalling a distutils project will only partially uninstall the project.
    Uninstalling six-1.4.1:
OSError: [Errno 1] Operation not permitted: '/tmp/pip-zeJjMk-uninstall/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/six-1.4.1-py2.7.egg-info'

Just i didn't want to digout whatever the hell reason regarding with access rights, Python 2.7 vs 3.x awesomeness and directly injected a Dockerfile a solved the problem right away!

FROM python:3-onbuild
MAINTAINER funkydorian

RUN mkdir /etugra
VOLUME /etugra
WORKDIR /etugra

CMD python -m pip install zeep
ENV  PYTHONPATH .:/usr/local/lib/python3.5

CMD ["python","./","secinitd.log"]

Build the image with:

docker build -t etugra .

Run the code whenever i make a change simply by:

docker run -it --rm --name etugra -v $PWD:/etugra etugra

How to bulk remove unused Docker images

facebooktwittergoogle_pluslinkedinmailby feather

I had many unused images appeared because of my fault:

Deryas-MacBook-Pro:etugra dsezen$ docker images

REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE

etugra                      latest              0e0485e9abbf        5 minutes ago       704.1 MB

<none>                      <none>              8a2ffaa937f3        8 minutes ago       704.1 MB

<none>                      <none>              d13dd077234c        9 minutes ago       704.1 MB

<none>                      <none>              017cb8b846b7        17 minutes ago      704.1 MB

<none>                      <none>              f671aaefbeb8        18 minutes ago      704.1 MB

<none>                      <none>              280ea3ac4ae5        44 minutes ago      704.1 MB

<none>                      <none>              97dcf929d414        45 minutes ago      704.1 MB

<none>                      <none>              019bcd4d779e        53 minutes ago      704.1 MB

<none>                      <none>              053a969a5a22        55 minutes ago      704.1 MB

<none>                      <none>              94be3db991db        58 minutes ago      704.1 MB

<none>                      <none>              cd284b979277        59 minutes ago      704.1 MB

<none>                      <none>              56181d2f6edf        59 minutes ago      704.1 MB

<none>                      <none>              a55ec92c3137        About an hour ago   704.1 MB

<none>                      <none>              7e9afad720aa        About an hour ago   704.1 MB

<none>                      <none>              907bbba168bf        About an hour ago   704.1 MB

<none>                      <none>              f42d87e744f6        About an hour ago   704.1 MB

<none>                      <none>              804aa0feedf2        About an hour ago   704.1 MB

<none>                      <none>              1036b6db0f20        About an hour ago   704.1 MB

<none>                      <none>              4868a31676cb        About an hour ago   704.1 MB

<none>                      <none>              7ade30482774        About an hour ago   704.1 MB

<none>                      <none>              353b07a482be        About an hour ago   704.1 MB

<none>                      <none>              d827f90112d1        About an hour ago   704.1 MB

<none>                      <none>              efb1e94f2c4f        About an hour ago   704.1 MB

<none>                      <none>              9e1210fd7d8f        2 hours ago         684.3 MB

<none>                      <none>              63eaa30ce706        2 hours ago         684.3 MB

<none>                      <none>              b89d5acf03e5        2 hours ago         684.3 MB

<none>                      <none>              c9905abf50b8        2 hours ago         709.6 MB

<none>                      <none>              af6393bc4b96        2 hours ago         696.2 MB

<none>                      <none>              4bb0534b3bd0        21 hours ago        675.1 MB

python                      3-onbuild           61bd1f884054        11 days ago         684.3 MB

Seems docker rmi does not accept standard input, so here is the way i found so that you can overcome this:

docker images|grep none|awk {'print $3'} > /tmp/dockertmp

for i in `cat /tmp/dockertmp`; do docker rmi $i; done

Howto trigger Visual Studio Code from OSX command line

facebooktwittergoogle_pluslinkedinmailby feather

If you also need to trigger Visual Studio Code for creating a new file into the codebase, in my case Dockerfile, he is the way to do that:

1. Open Visual Studio Code

2. Type ⇧⌘P

3. Type 'Shell command' and choose 'Install code command in PATH'

This simply adds 'code' binary link to the PATH

4. Type the following to initiate a new file:

Deryas-MacBook-Pro:DIGOUT dsezen$ code Dockerfile

© 2017 Derya Sezen

Theme by Anders NorenUp ↑

visited 27 states (12%)
Create your own visited map of The World