Want more timely Centmin Mod News Updates?
Become a Member

Install Centmin Mod LEMP stack via Gitlab.com Mirror

Discussion in 'Centmin Mod News' started by eva2000, Mar 9, 2016.

Thread Status:
Not open for further replies.
  1. eva2000

    eva2000 Administrator Staff Member

    May 24, 2014
    Brisbane, Australia
    Local Time:
    11:09 AM
    Nginx 1.13.x
    MariaDB 5.5

    China Great Firewall Blocks Github.com

    Centmin Mod LEMP stack's official code is hosted on it's Github Repo at https://github.com/centminmod/centminmod. However, for some folks in China, Github.com is blocked by the Chinese governments firewall and inaccessible [wikipedia]. So alternatively you can use Centmin Mod's Gitlab.com Repo at https://gitlab.com/centminmod/centminmod which is outlined at Centmin Mod Git Repository Online Status.

    Not 100% Perfect

    Unfortunately, while Chinese folks can download Centmin Mod LEMP code itself from alternative Gitlab.com mirror repo. The actual centmin.sh install script still relies on downloading and calling 3rd party source tarball files from various Github.com repositories which don't have an alternative mirror. So for Chinese folks running centmin.sh initial install will break as they won't be able to download the github.com components.

    On my to do list is to work on a solution for this in the future. For now the below instructions are for folks who can access Github.com and Gitlab.com if they want to test out initial installs using the Gitlab.com mirror instead of Github.com official repo.

    Update: I've started the enormous task of creating a Gitlab based Git mirror repository for every Github.com repository that Centmin Mod relies on to install it's LEMP stack environment. I've created all the Gitlab Git mirrors under a Gitlab group at https://gitlab.com/groups/centminmod-github-mirror. Currently, I have mirrored around 61+ Github repos to the Gitlab Group. These Gitlab mirrors are auto updated from the Github original repo every 60 minutes. Once I have all Github repositories mirrored to Gitlab Group, I'll have to look into how to best utilise these mirrors in Centmin Mod.

    Chinese firewall test for Github.com vs Gitlab.com

    You can read up on more details at DNS Cache Poisoning in the People's Republic of China - Research - ViewDNS.info

    Centmin Mod Gitlab.com Mirror

    The Centmin Mod Gitlab.com Repo mirror https://gitlab.com/centminmod/centminmod is an exact mirror of the Github.com official Centmin Mod Repo down to the install instructions which assume Github.com usage not Gitlab.com usage. So is using Gitlab.com mirror fully requires slightly different command steps for install. These steps are outlined below.

    I've also started a Gitlab Group to mirror all the 3rd party Github repos that Centmin Mod downloads from. So far 61+ Github repos have been mirrored under the Gitlab Group at https://gitlab.com/groups/centminmod-github-mirror. There maybe more Github repos I have yet to mirror.

    Initial Install of Centmin Mod 123.09beta01

    I will use Centmin Mod 123.09beta01 branch as an example as it's soon to be stable so best to test with the beta for newer improved features. The initial install for Centmin Mod LEMP stack using Gitlab.com mirror is best done using the curl one liner installer-gitlab.sh which can be accessed directly:
    Code (Text):
    curl -O https://gitlab.com/centminmod/centminmod/raw/123.09beta01/installer-gitlab.sh && chmod 0700 installer-gitlab.sh && bash installer-gitlab.sh

    or via version on centminmod.com site
    Code (Text):
    curl -O https://centminmod.com/betainstaller-gitlab.sh && chmod 0700 betainstaller-gitlab.sh && bash betainstaller-gitlab.sh

    CentminMod.com Mirrors

    Looks like centminmod.com and centminmod.net are blocked from China too ! Possibly due to Route53 GeoDNS and that test site reporting unexpected DNS A record IP. So problemn is with viewdns.info tool itself falsely detects it as DNS poisoning. But I have a 3rd mirror domain for centmin.sh which is not blocked :)
    Last edited: Mar 12, 2016
Thread Status:
Not open for further replies.