├── .env.example ├── .gitignore ├── .gitlab-ci.yml.example.yaml ├── Envoy.blade.php.example ├── Gitlab-CI.png ├── Gitlab-Runner-Register-Success.png ├── Gitlab-Runner-Register.png ├── LICENSE ├── README.md ├── Usage-Docker.png ├── assets ├── image-20191030161106282.png ├── image-20191030165624205.png ├── image-20191030165643847.png └── image-20191030172638128.png ├── docker-compose.yml ├── gitlab-ci ├── .ssh │ └── .gitignore ├── Dockerfile └── config │ └── .gitignore ├── gitlab ├── data │ └── .gitignore └── logs │ └── .gitignore ├── laravel-gitlab-runner.md ├── postgresql └── data │ └── .gitignore └── redis └── .gitignore /.env.example: -------------------------------------------------------------------------------- 1 | DEBUG=false 2 | 3 | DB_ADAPTER=postgresql 4 | DB_HOST=postgresql 5 | DB_PORT=5432 6 | DB_USER=gitlab 7 | DB_PASS=password 8 | DB_NAME=gitlabhq_production 9 | 10 | REDIS_HOST=redis 11 | REDIS_PORT=6379 12 | 13 | TZ=Asia/Shanghai 14 | GITLAB_TIMEZONE=Beijing 15 | 16 | GITLAB_HTTPS=false 17 | SSL_SELF_SIGNED=false 18 | 19 | GITLAB_HOST=localhost 20 | GITLAB_PORT=10080 21 | GITLAB_SSH_PORT=10022 22 | GITLAB_RELATIVE_URL_ROOT= 23 | GITLAB_SECRETS_DB_KEY_BASE=base64:wJrklh4TJAwSUIxOAPagkPWzQgLSoZ+lekE3ClUkfg0= 24 | GITLAB_SECRETS_SECRET_KEY_BASE=base64:vSHULhdG2YK7ZU33iepRHKmxYxbxxgNPCRQaotGG5YE= 25 | GITLAB_SECRETS_OTP_KEY_BASE=base64:dg2lVNcO84EtV+Cjy9wZIie9OSjQLR6hPqJqRp/E/e4= 26 | 27 | GITLAB_ROOT_PASSWORD= 28 | GITLAB_ROOT_EMAIL= 29 | 30 | GITLAB_NOTIFY_ON_BROKEN_BUILDS=true 31 | GITLAB_NOTIFY_PUSHER=false 32 | 33 | GITLAB_EMAIL=notifications@example.com 34 | GITLAB_EMAIL_REPLY_TO=noreply@example.com 35 | GITLAB_INCOMING_EMAIL_ADDRESS=reply@example.com 36 | 37 | GITLAB_BACKUP_SCHEDULE=daily 38 | GITLAB_BACKUP_TIME=01:00 39 | 40 | SMTP_ENABLED=false 41 | SMTP_DOMAIN=www.example.com 42 | SMTP_HOST=smtp.gmail.com 43 | SMTP_PORT=587 44 | SMTP_USER=mailer@example.com 45 | SMTP_PASS=password 46 | SMTP_STARTTLS=true 47 | SMTP_AUTHENTICATION=login 48 | 49 | IMAP_ENABLED=false 50 | IMAP_HOST=imap.gmail.com 51 | IMAP_PORT=993 52 | IMAP_USER=mailer@example.com 53 | IMAP_PASS=password 54 | IMAP_SSL=true 55 | IMAP_STARTTLS=false 56 | 57 | OAUTH_ENABLED=false 58 | OAUTH_AUTO_SIGN_IN_WITH_PROVIDER= 59 | OAUTH_ALLOW_SSO= 60 | OAUTH_BLOCK_AUTO_CREATED_USERS=true 61 | OAUTH_AUTO_LINK_LDAP_USER=false 62 | OAUTH_AUTO_LINK_SAML_USER=false 63 | OAUTH_EXTERNAL_PROVIDERS= 64 | 65 | OAUTH_CAS3_LABEL=cas3 66 | OAUTH_CAS3_SERVER= 67 | OAUTH_CAS3_DISABLE_SSL_VERIFICATION=false 68 | OAUTH_CAS3_LOGIN_URL=/cas/login 69 | OAUTH_CAS3_VALIDATE_URL=/cas/p3/serviceValidate 70 | OAUTH_CAS3_LOGOUT_URL=/cas/logout 71 | 72 | OAUTH_GOOGLE_API_KEY= 73 | OAUTH_GOOGLE_APP_SECRET= 74 | OAUTH_GOOGLE_RESTRICT_DOMAIN= 75 | 76 | OAUTH_FACEBOOK_API_KEY= 77 | OAUTH_FACEBOOK_APP_SECRET= 78 | 79 | OAUTH_TWITTER_API_KEY= 80 | OAUTH_TWITTER_APP_SECRET= 81 | 82 | OAUTH_GITHUB_API_KEY= 83 | OAUTH_GITHUB_APP_SECRET= 84 | OAUTH_GITHUB_URL= 85 | OAUTH_GITHUB_VERIFY_SSL= 86 | 87 | OAUTH_GITLAB_API_KEY= 88 | OAUTH_GITLAB_APP_SECRET= 89 | 90 | OAUTH_BITBUCKET_API_KEY= 91 | OAUTH_BITBUCKET_APP_SECRET= 92 | 93 | OAUTH_SAML_ASSERTION_CONSUMER_SERVICE_URL= 94 | OAUTH_SAML_IDP_CERT_FINGERPRINT= 95 | OAUTH_SAML_IDP_SSO_TARGET_URL= 96 | OAUTH_SAML_ISSUER= 97 | OAUTH_SAML_LABEL="Our SAML Provider" 98 | OAUTH_SAML_NAME_IDENTIFIER_FORMAT=urn:oasis:names:tc:SAML:2.0:nameid-format:transient 99 | OAUTH_SAML_GROUPS_ATTRIBUTE= 100 | OAUTH_SAML_EXTERNAL_GROUPS= 101 | OAUTH_SAML_ATTRIBUTE_STATEMENTS_EMAIL= 102 | OAUTH_SAML_ATTRIBUTE_STATEMENTS_NAME= 103 | OAUTH_SAML_ATTRIBUTE_STATEMENTS_FIRST_NAME= 104 | OAUTH_SAML_ATTRIBUTE_STATEMENTS_LAST_NAME= 105 | 106 | OAUTH_CROWD_SERVER_URL= 107 | OAUTH_CROWD_APP_NAME= 108 | OAUTH_CROWD_APP_PASSWORD= 109 | 110 | OAUTH_AUTH0_CLIENT_ID= 111 | OAUTH_AUTH0_CLIENT_SECRET= 112 | OAUTH_AUTH0_DOMAIN= 113 | 114 | OAUTH_AZURE_API_KEY= 115 | OAUTH_AZURE_API_SECRET= 116 | OAUTH_AZURE_TENANT_ID= -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | *.gem 2 | *.rbc 3 | .env 4 | /.config 5 | /coverage/ 6 | /InstalledFiles 7 | /pkg/ 8 | /spec/reports/ 9 | /spec/examples.txt 10 | /test/tmp/ 11 | /test/version_tmp/ 12 | /tmp/ 13 | 14 | # Used by dotenv library to load environment variables. 15 | # .env 16 | 17 | ## Specific to RubyMotion: 18 | .dat* 19 | .repl_history 20 | build/ 21 | *.bridgesupport 22 | build-iPhoneOS/ 23 | build-iPhoneSimulator/ 24 | 25 | ## Specific to RubyMotion (use of CocoaPods): 26 | # 27 | # We recommend against adding the Pods directory to your .gitignore. However 28 | # you should judge for yourself, the pros and cons are mentioned at: 29 | # https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control 30 | # 31 | # vendor/Pods/ 32 | 33 | ## Documentation cache and generated files: 34 | /.yardoc/ 35 | /_yardoc/ 36 | /doc/ 37 | /rdoc/ 38 | 39 | ## Environment normalization: 40 | /.bundle/ 41 | /vendor/bundle 42 | /lib/bundler/man/ 43 | 44 | # for a library or gem, you might want to ignore these files since the code is 45 | # intended to run in multiple environments; otherwise, check them in: 46 | # Gemfile.lock 47 | # .ruby-version 48 | # .ruby-gemset 49 | 50 | # unless supporting rvm < 1.11.0 or doing something fancy, ignore this: 51 | .rvmrc 52 | .php_cs.cache -------------------------------------------------------------------------------- /.gitlab-ci.yml.example.yaml: -------------------------------------------------------------------------------- 1 | stages: 2 | - pull_code_test 3 | - pull_code_production 4 | - install_deps 5 | - test 6 | - build 7 | - deploy_test 8 | - deploy_production 9 | variables: 10 | PHP_FPM_CONTAINER: lnmp-php-fpm 11 | WORK_DIR: /usr/share/nginx/html/ 12 | PROJECT: laravel-demo 13 | GIT_DIR: /mnt/lnmp-docker 14 | # 拉取代码 15 | pull_code_test: 16 | stage: pull_code_test 17 | only: 18 | - develop 19 | script: 20 | - cd ${GIT_DIR}/${PROJECT} 21 | - git pull origin develop 22 | pull_code_production: 23 | stage: pull_code_production 24 | only: 25 | - master 26 | script: 27 | - cd ${GIT_DIR}/${PROJECT} 28 | - git pull origin master 29 | # 安装依赖 30 | install_deps: 31 | stage: install_deps 32 | script: 33 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} composer install 34 | build: 35 | stage: build 36 | script: 37 | # Run migrations 38 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan migrate 39 | # Cache clearing 40 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan cache:clear 41 | # Create a cache file for faster configuration loading 42 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan config:cache 43 | # Create a route cache file for faster route registration 44 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan route:clear 45 | deploy_test: 46 | stage: deploy_test 47 | script: 48 | - cd ${GIT_DIR} 49 | - docker-compose down && docker-compose build && docker-compose up -d 50 | deploy_production: 51 | stage: deploy_production 52 | script: 53 | - cd ${GIT_DIR} 54 | - docker-compose restart -------------------------------------------------------------------------------- /Envoy.blade.php.example: -------------------------------------------------------------------------------- 1 | {{-- 2 | # envoy run deploy --env=staging --branch=develop 3 | # 1. 克隆远程仓库 4 | # 2. 安装Composer依赖 5 | # 3. 创建符号链接 6 | # 4. 删除历史部署目录(适用DEV环境) 7 | --}} 8 | @servers(['ecs' => ['root@106.11.248.144']]) 9 | 10 | @setup 11 | $repository = 'git@gitlab.chenghuyiong.com:project/mp.git'; 12 | $staging_repository = 'git@127.0.0.1:project/mp.git'; 13 | $releases_dir = '/var/www/project/releases'; 14 | $app_dir = '/var/www/project'; 15 | $release = date('YmdHis'); 16 | $new_release_dir = $releases_dir .'/'. $release; 17 | $branch = isset($branch) ? $branch : "develop"; 18 | $env = isset($env) ? $env : "staging"; 19 | $user = 'apache'; 20 | $current = $app_dir . '/current'; 21 | $runtime = $app_dir . '/runtime'; 22 | $link_rumtime = $new_release_dir . '/runtime'; 23 | @endsetup 24 | 25 | @story('deploy') 26 | clone_repository 27 | run_composer 28 | update_symlinks 29 | clear_cache 30 | change_permission 31 | @endstory 32 | 33 | @task('clone_repository', ['on' => ['ecs'], 'parallel' => true]) 34 | echo 'Cloning repository' 35 | git config --global user.email "deployer@chenghuiyong.com" 36 | git config --global user.name "Deployer" 37 | [ -d {{ $releases_dir }} ] || mkdir {{ $releases_dir }} 38 | @if ($env == 'staging') 39 | git clone -b {{ $branch }} {{ $staging_repository }} {{ $new_release_dir }} 40 | @else 41 | git clone --depth 1 {{ $repository }} {{ $new_release_dir }} 42 | cd {{ $new_release_dir }} 43 | git reset --hard {{ $commit }} 44 | @endif 45 | @endtask 46 | 47 | @task('run_composer', ['on' => ['ecs'], 'parallel' => true]) 48 | echo "Starting deployment ({{ $release }})" 49 | cd {{ $new_release_dir }} 50 | composer install --prefer-dist --no-scripts -q -o 51 | @endtask 52 | 53 | @task('update_symlinks', ['on' => ['ecs'], 'parallel' => true]) 54 | echo "Linking runtime directory" 55 | cd {{ $new_release_dir }} 56 | rm -rf {{ $link_rumtime }} 57 | [ -d {{ $runtime }} ] || mkdir {{ $runtime }} 58 | ln -nfs {{ $runtime }} {{ $link_rumtime }} 59 | echo 'Linking .env file' 60 | @if ($env == 'staging') 61 | cp .env.sandbox .env 62 | @endif 63 | @if ($env == 'production') 64 | cp .env.production .env 65 | @endif 66 | echo 'Linking current release' 67 | ln -nfs {{ $new_release_dir }} {{ $current }} 68 | @endtask 69 | 70 | @task('clear_cache', ['on' => ['ecs'], 'parallel' => true]) 71 | echo 'Clearing cache' 72 | cd {{ $new_release_dir }} 73 | php think clear 74 | php think migrate:run 75 | php think optimize:autoload 76 | php think optimize:config 77 | php think optimize:route 78 | @if ($env == 'staging') 79 | echo 'Removing earlier app' 80 | cd {{ $releases_dir }} 81 | shopt -s extglob 82 | rm -rf !({{ $release }}) 83 | @endif 84 | @endtask 85 | 86 | @task('change_permission', ['on' => ['ecs'], 'parallel' => true]) 87 | echo 'Changing permission' 88 | chown -R {{ $user }}:{{ $user }} {{ $new_release_dir }} 89 | chown -R {{ $user }}:{{ $user }} {{ $current }} 90 | chown -R {{ $user }}:{{ $user }} {{ $runtime }} 91 | chmod -R 777 {{ $runtime }} 92 | @endtask -------------------------------------------------------------------------------- /Gitlab-CI.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/Gitlab-CI.png -------------------------------------------------------------------------------- /Gitlab-Runner-Register-Success.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/Gitlab-Runner-Register-Success.png -------------------------------------------------------------------------------- /Gitlab-Runner-Register.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/Gitlab-Runner-Register.png -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | {one line to give the program's name and a brief idea of what it does.} 635 | Copyright (C) {year} {name of author} 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | {project} Copyright (C) {year} {fullname} 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # 基于Docker快速搭建Gitlab与Gitlab CI/CD服务 2 | 3 | `更新推荐` [使用Gitlab Runner 部署Laravel 项目](https://segmentfault.com/a/1190000020868208) 4 | 5 | 此文档基于现有项目运行实践整理，其中包含了许多Gitlab、CI/CD相关概念，阅读需要有一定的Gitlab、Docker、CI/CD基础知识。 6 | 7 | ## 目录 8 | - [此项目能做什么](#此项目能做什么) 9 | - [Git-Flow/Github-Flow/Gitlab-Flow工作流](#Git-Flow/Github-Flow/Gitlab-Flow工作流) 10 | - [快速运行Gitlab](#快速运行Gitlab) 11 | - [持续集成/持续交互](#持续集成/持续交互) 12 | - [Gitlab-Runner自动构建与部署的执行](#Gitlab-Runner自动构建与部署的执行) 13 | - [获取注册参数 ](#获取注册参数 ) 14 | - [注册Gitlab-Runner](#注册Gitlab-Runner) 15 | - [CI/CD运行流程](#CI/CD运行流程) 16 | - [CI/CD分布式](#CI/CD分布式) 17 | 18 | 19 | 此项目能做什么 20 | ------ 21 | 22 | 1. 分享一些关于团队Git版本控制使用心得。 23 | 2. 提供一份Docker版本的Gtilab私有化仓库应用实现，让你在开发团队内部快速构建一套Git托管仓库系统。 24 | 3. 提供一份Gitlab Docker容器编排实现参考，分离Gitlab/Redis/PostgreSQL/Gitlab-CI和运行时数据。 25 | 4. 提供一份Gitlab Runner Docker版本实现，在Runner容器内部增加了对PHP的支持，利用[Laravel Envoy](https://github.com/laravel/envoy)实现远程操作多台主机，实现分布式自动构建与交付。 26 | 5. 加深对软件从编码 =》 构建 =》 测试 =》 部署的整个生命周期的认知， 27 | 6. 为Web/Web API类型互联网产品自动化提供参考，适合中小型创业研发团队快速迭代版本。 28 | 29 | Git-Flow/Github-Flow/Gitlab-Flow工作流 30 | ------ 31 | 32 | 33 | 34 | Git团队开发中，大家都在向仓库中提交功能代码，时间久了，分支与版本就逐渐增多而变得复杂，因此，一个合理的版本管理流程在项目初期就非常重要。 35 | 36 | 使用Git，多数时候推荐流行的git-flow工作流程 [git-flow 备忘清单](https://danielkummer.github.io/git-flow-cheatsheet/index.zh_CN.html)。通常，develop分支作为测试版本使用，所有开发者都能够向该分支合并代码，以保证代码经过评审和功能验证。master分支作为线上版本使用，只有仓库管理员才能向该分支合并代码，以确保线上版本稳定。 37 | 38 | ![](https://docs.gitlab.com/ce/workflow/gitdashflow.png) 39 | 40 | + **feature branches** 功能特性分支，基于develop分支开发，在功能开发完成后，代码会被合并到develop分支，此分支也自动删除。 41 | + **develop** 测试分支，一般基于该分支构建应用的测试环境。 42 | + **release branches** 发布分支。新功能开发完成，经过了代码评审和功能验证后，仓库管理员使用`git flow release start 1.0.0` 命令方式合并develop分支到master分支。使用该命令，需要确保master分支与develop分支基础版本一致。 43 | + **hotfixes** 修复分支，一般而言，在线上环境出现问题，需要紧急修复时，需创建hotfix修复补丁分支，它基于master分支开发，补丁修复代码会被合并至master与develop分支。 44 | + **master** 生产分支，一般基于该分支中构建应用的生产环境。 45 | 46 | ![](https://danielkummer.github.io/git-flow-cheatsheet/img/git-flow-commands.png) 47 | 48 | 49 | 50 | 在单人Git开发场景下，此流程足以满足需求，但是在多人的开发团队中，有时候稍显"[无力](https://about.gitlab.com/2014/09/29/gitlab-flow/)"，而Gitlab/Github推荐使用PR/MR的方式，开发者需要主动发起分支合并申请，在得到确认后，分支开发才算完成。 51 | 52 | 开发者基于主干分支先创建新的功能性分支，在功能开发完成后，需要作Merge Request申请，也即是主动请求合并功能分支代码到主干分支。仓库管理员会评审每一次MR，只有评审通过，新功能才被提交上线。 53 | 54 | ![](https://about.gitlab.com/images/git_flow/github_flow.png) 55 | 56 | 快速运行Gitlab 57 | ----------- 58 | 59 | 60 | 61 | 62 | Gitlab提供社区与企业版本，[官网](https://about.gitlab.com/installation/)提供多种Gitlab安装方式。此项目是基于Docker版本的Gitlab实现，开发者无需更多关心Gitlab安装过程，Docker镜像已做好了环境和依赖。 63 | 64 | 该项目基于[Docker GitLab](http://www.damagehead.com/docker-gitlab/) 镜像构建，它将Gitlab/PostgreSQL/Redis容器拆分，分离了运行时数据。同时，提供一套容器编排配置参考，支持Docker Compose快速构建与维护。 65 | 66 | 确保你的主机已经安装好了Docker与Docke-Compose，按照下面的方式快速运行Gitlab。 67 | 68 | 1. 克隆仓库 69 | 70 | ```sh 71 | $ git clone https://github.com/bravist/gitlab-docker 72 | $ cd ~/gitlab-docker 73 | ``` 74 | 75 | 2. 配置环境变量，推荐使用默认配置 76 | 77 | ```sh 78 | $ cp .env.example .env 79 | ``` 80 | 81 | 3. 使用`docker-compose`构建镜像和启动容器 82 | 83 | ```sh 84 | $ docker-compose build && docker-compose up -d 85 | ``` 86 | 87 | 4. 确认容器构建成功，Gitlab Web控制台访问：[http://localhost:10080/](http://localhost:10080/)，如果出现502错误，请稍后再次访问，容器构建Gitlab需要等待依赖安装完成。 88 | 89 | ```bash 90 | CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 91 | 8827363f45d8 sameersbn/gitlab:10.3.3 "/sbin/entrypoint.sh…" 4 seconds ago Up 4 seconds 443/tcp, 0.0.0.0:10022->22/tcp, 0.0.0.0:10080->80/tcp gitlabdocker_gitlab_1 92 | db0dd3b3d23f bravist/gitlab-ci-php-envoy:1.0 "/usr/bin/dumb-init …" 7 seconds ago Up 6 seconds gitlab-ci-php-envoy-runner 93 | f598844c561c sameersbn/redis:latest "/sbin/entrypoint.sh…" 7 seconds ago Up 6 seconds 6379/tcp gitlab-redis 94 | 73d93b7cd110 sameersbn/postgresql:9.6-2 "/sbin/entrypoint.sh" 7 seconds ago Up 5 seconds 0.0.0.0:5432->5432/tcp gitlab-postgresql 95 | ``` 96 | 项目内置了Gitlab Runner镜像，默认会启动一台Gitlab Runner容器，让你在本地可以快速搭建CI/CD服务。 97 | 98 | 持续集成/持续交互 99 | ------ 100 | 101 | 102 | CI/CD 的全称是 Continuous Integration & Deployment (持续集成/部署)，是 extreme programming (极限编程) 的一部分。我们常用 CI 来做一些自动化工作，这种自动化工作会运行在一台集中的机器上，比如程序的打包，单元测试，部署等。 [维基百科 - 持续集成](https://zh.wikipedia.org/wiki/%E6%8C%81%E7%BA%8C%E6%95%B4%E5%90%88) 103 | 104 | ![Gitlab CI](https://images-cdn.shimo.im/I2kB4mczcgYkeQSB/cicd_pipeline_infograph.png!thumbnail) 105 | 106 | Gitlab 从 8.* 版本后支持CI/CD，要使用CI/CD，先理解一些概念 107 | 108 | **Pipeline** 109 | 110 | 一次[Pipeline](https://docs.gitlab.com/ce/ci/pipelines.html)就是一次完整的构建任务，里面可以包含多个阶段（[stages](https://docs.gitlab.com/ce/ci/yaml/README.html#stages)）。 111 | 112 | **Stage** 113 | 114 | Stages表示任务构建的阶段。一次Pipeline中允许定义多个 Stages，这些 Stages 会有以下特点： 115 | 116 | - 所有 Stages 会按照顺序运行，即当一个 Stage 完成后，下一个 Stage 才会开始 117 | - 只有当所有 Stages 完成后，该构建任务 (Pipeline) 才会成功 118 | - 如果任何一个 Stage 失败，那么后面的 Stages 不会执行，该构建任务 (Pipeline) 失败 119 | 120 | **Job** 121 | 122 | Jobs 表示构建工作，表示某个 Stage 里面执行的工作。 123 | 我们可以在 Stages 里面定义多个 Jobs，这些 Jobs 会有以下特点： 124 | 125 | - 相同Stage中的Jobs会并行执行 126 | - 相同Stage中的Jobs都执行成功时，该 Stage 才会成功 127 | - 如果任何一个Job失败，那么该 Stage 失败，即该构建任务 (Pipeline) 失败 128 | 129 | 我把[Pipelines](https://docs.gitlab.com/ce/ci/pipelines.html)理解为流水线，流水线包含有多个阶段（[stages](https://docs.gitlab.com/ce/ci/yaml/README.html#stages)），每个阶段包含有一个或多个工序（[jobs](https://docs.gitlab.com/ce/ci/yaml/README.html#jobs)），比如先购料、组装、测试、包装再上线销售，每一次Push或者MR都要经过流水线之后才可以合格出厂。 130 | 131 | ![Gitlab-CI](Gitlab-CI.png) 132 | 133 | Gilab中，仓库的.gitlab.ci.yml文件负责定义项目具体工作任务和流水线，Gitlab Runner基于配置好的流水线逐步执行任务，直到任务完成，如果中途错误，它会立即停止后续的任务。如果项目使用Gitlab CI，需要提前添加该文件。 134 | 135 | ```shell 136 | stages: 137 | - pull_code_test 138 | - pull_code_production 139 | - install_deps 140 | - test 141 | - build 142 | - deploy_test 143 | - deploy_production 144 | variables: 145 | PHP_FPM_CONTAINER: lnmp-php-fpm 146 | WORK_DIR: /usr/share/nginx/html/ 147 | PROJECT: laravel-demo 148 | GIT_DIR: /mnt/lnmp-docker 149 | # 拉取代码 150 | pull_code_test: 151 | stage: pull_code_test 152 | only: 153 | - develop 154 | script: 155 | - cd ${GIT_DIR}/${PROJECT} 156 | - git pull origin develop 157 | pull_code_production: 158 | stage: pull_code_production 159 | only: 160 | - master 161 | script: 162 | - cd ${GIT_DIR}/${PROJECT} 163 | - git pull origin master 164 | # 安装依赖 165 | install_deps: 166 | stage: install_deps 167 | script: 168 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} composer install 169 | build: 170 | stage: build 171 | script: 172 | # Run migrations 173 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan migrate 174 | # Cache clearing 175 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan cache:clear 176 | # Create a cache file for faster configuration loading 177 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan config:cache 178 | # Create a route cache file for faster route registration 179 | - docker exec -w ${WORK_DIR}/${PROJECT} ${PHP_FPM_CONTAINER} php artisan route:clear 180 | deploy_test: 181 | stage: deploy_test 182 | script: 183 | - cd ${GIT_DIR} 184 | - docker-compose down && docker-compose build && docker-compose up -d 185 | deploy_production: 186 | stage: deploy_production 187 | script: 188 | - cd ${GIT_DIR} 189 | - docker-compose restart 190 | ``` 191 | 192 | 193 | 194 | Gitlab-Runner自动构建与部署的执行 195 | ------ 196 | 197 | 198 | GitLab Runner 是一个开源项目， 它用来运行你定制的任务（jobs）并把结果返回给 GitLab。 GitLab Runner 配合[GitLab CI](https://about.gitlab.com/gitlab-ci)（GitLab 内置的持续集成服务） 协调完成任务。 [GitLab Runner](https://docs.gitlab.com.cn/runner/) 199 | 200 | 简单的说，Gitlab Runner是独立运行配置好了Gitlab CI/CD项目的机器，它负责Gitlab项目的自动构建和部署的运行。 201 | 202 | Gitlab Runner安装有多种方式，具体可以参考[官方文档](https://docs.gitlab.com.cn/runner/install/index.html)，这里推荐使用基于Docker的版本 [bravist/gitlab-ci-php-envoy](https://hub.docker.com/r/bravist/gitlab-ci-php-envoy/)，镜像源码已同步在此项目中，上面的章节也能看到运行的容器。 203 | 204 | Gitlab Runner安装运行之后，需要[注册到Gitlab项目中去](https://docs.gitlab.com.cn/runner/register/index.html)，才能使用其“功效”。 205 | 206 | 获取注册参数 207 | ------ 208 | 209 | 210 | 登录Gitlab控制台，选择一个Gitlab仓库，进入 Settings =》CI / CD =》Runners settings =》Expand，获取Runners相关参数。 211 | 212 | ![Gitlab Runner Register Parameters](./Gitlab-Runner-Register.png) 213 | 214 | 注册Gitlab-Runner 215 | ------ 216 | 217 | 218 | ```shell 219 | $ docker exec -it gitlab-ci-php-envoy-runner gitlab-ci-multi-runner register 220 | 221 | Running in system-mode. 222 | 223 | #输入CI URL 224 | Please enter the gitlab-ci coordinator URL (e.g. https://gitlab.com/): 225 | http://gitlab.weipeiapp.com:10080/ 226 | 227 | #输入CI Token 228 | Please enter the gitlab-ci token for this runner: 229 | eU9zcqjReSozw6a1RLL8 230 | 231 | #输入描述信息 232 | Please enter the gitlab-ci description for this runner: 233 | [f6c7de92c743]: Gitlab CI usage 234 | 235 | #输入标签信息 236 | Please enter the gitlab-ci tags for this runner (comma separated): 237 | v1.0 238 | 239 | #是否运行未标记的版本 240 | Whether to run untagged builds [true/false]: 241 | [false]: true 242 | 243 | #是否运行当前项目 244 | Whether to lock the Runner to current project [true/false]: 245 | [true]: true 246 | 247 | Registering runner... succeeded                     runner=eU9zcqjR 248 | 249 | #输入Runner的类型 250 | Please enter the executor: shell, virtualbox, docker-ssh+machine, kubernetes, docker, docker-ssh, parallels, ssh, docker+machine: 251 | shell 252 | 253 | Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded! 254 | ``` 255 | 256 | 注册成功后，页面会多出一个正在运行的Runner绿色标志。 257 | 258 | CI/CD运行流程 259 | ------ 260 | 261 | 262 | 如果你了解[bravist/lnmp-docker](https://github.com/bravist/lnmp-docker)，对于下面的图不会陌生，主要提供了一套Web应用自动构建与交付流程架构。 263 | 264 | 通常情况下Gitlab Runner与Gitlab无需运行在同一台服务器，他们之间通信基于授信TOKEN，整个运行流程是： 265 | 266 | 1. 基于Gitlab Flow 完成功能开发 267 | 2. 提交Merge Request，等待功能发布申请 268 | 3. 评审Merge Request，允许合并分支请求 269 | 4. 触发Gitlab Runner运行 270 | 5. 执行项目 .gitlab.ci.yml 配置好的流水线任务 271 | 6. 完成CI/CD流水线工作，工作结束 272 | 273 | 以一个前端项目为例，构建过程会做以下任务 274 | 275 | + 拉取Git代码 276 | + 安装前端依赖 277 | + 打包、编译 278 | 279 | ![Usage-Docker](./Usage-Docker.png) 280 | 281 | CI/CD分布式 282 | ------ 283 | 284 | 285 | 本项目Gitlab Runner默认采用Shell方式执行部署任务，也即是Runner使用SSH登录到应用主机。你可以在Runner容器中生成新的ssh秘钥对（或者使用能够登录到应用主机的其他ssh秘钥对），确保能成功SSH到应用主机。 286 | 287 | 进入到Runner容器 288 | 289 | ```shell 290 | docker exec -it gitlab-ci-php-envoy-runner sh 291 | ``` 292 | 293 | 使用ssh登录远程应用主机 294 | 295 | ```shell 296 | ssh root@47.*.*.69 297 | ``` 298 | 299 | 如果成功登录，表示自动部署链接工作没有问题。如果你的应用部署了多台服务器，推荐使用[Larave Envoy](https://laravel.com/docs/5.6/envoy)部署任务。Laravel Envoy 基于PHP实现，提供了灵活的配置方便在应用主机构建任务。 [bravist/gitlab-ci-php-envoy](https://hub.docker.com/r/bravist/gitlab-ci-php-envoy/) Runner基于gitlab/gitlab-runner镜像，又增加了对PHP的支持，完全支持Laravel Envoy部署。 300 | 301 | 要使用Laravel Envoy，需要在仓库中增加Envoy.blade.php文件，定义好所有主机需要做的事情。 302 | 303 | ```shell 304 | @servers(['sandbox' => 'root@47.*.*.45', 'production' => 'root@47.*.*.69']) 305 | 306 | @story('sandbox_deploy', ['on' => ['sandbox']]) 307 | git 308 | logistics-debt 309 | @endstory 310 | 311 | @story('production_deploy', ['on' => ['production']]) 312 | git 313 | logistics-debt 314 | @endstory 315 | 316 | 317 | @task('git') 318 | cd /mnt/lnmp-docker/www/{{ $project }}/ 319 | git config --global user.email "chenghuiyong1987@gmail.com" 320 | git config --global user.name "Gitlab Runner" 321 | git pull origin {{ $branch }} 322 | @endtask 323 | 324 | @task('logistics-debt') 325 | cd /mnt/lnmp-docker/www/{{ $project }}/logistics-debt 326 | cnpm install 327 | npm run build 328 | @endtask 329 | 330 | ``` 331 | 332 | 同时，在仓库的.gitlab-ci.yml文件中定义使用Envoy执行构建任务。 333 | 334 | ```shell 335 | stages: 336 | - sandbox 337 | - production 338 | 339 | variables: 340 | ENVOY: /root/.composer/vendor/bin/envoy 341 | 342 | sandbox: 343 | stage: sandbox 344 | script: 345 | - cd $CI_PROJECT_DIR 346 | - $ENVOY run sandbox_deploy --branch=develop --project=$CI_PROJECT_NAME 347 | only: 348 | - develop 349 | production: 350 | stage: production 351 | script: 352 | - cd $CI_PROJECT_DIR 353 | - $ENVOY run production_deploy --branch=master --project=$CI_PROJECT_NAME 354 | only: 355 | - master 356 | ``` 357 | -------------------------------------------------------------------------------- /Usage-Docker.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/Usage-Docker.png -------------------------------------------------------------------------------- /assets/image-20191030161106282.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/assets/image-20191030161106282.png -------------------------------------------------------------------------------- /assets/image-20191030165624205.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/assets/image-20191030165624205.png -------------------------------------------------------------------------------- /assets/image-20191030165643847.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/assets/image-20191030165643847.png -------------------------------------------------------------------------------- /assets/image-20191030172638128.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/huiyonghkw/gitlab-ci-docker/29bbe9fcaae4a8007cd334cff764e8aee039e20d/assets/image-20191030172638128.png -------------------------------------------------------------------------------- /docker-compose.yml: -------------------------------------------------------------------------------- 1 | version: '2' 2 | services: 3 | redis: 4 | restart: always 5 | image: sameersbn/redis:latest 6 | container_name: gitlab-redis 7 | command: 8 | - --loglevel warning 9 | volumes: 10 | - ./redis:/var/lib/redis:Z 11 | 12 | # Gitlab - GitLab is open source software to collaborate on code 13 | postgresql: 14 | restart: always 15 | image: sameersbn/postgresql:9.6-2 16 | container_name: gitlab-postgresql 17 | ports: 18 | - "5432:5432" 19 | volumes: 20 | - ./postgresql/data:/var/lib/postgresql:Z 21 | environment: 22 | - DB_USER=gitlab 23 | - DB_PASS=password 24 | - DB_NAME=gitlabhq_production 25 | - DB_EXTENSION=pg_trgm 26 | gitlab: 27 | image: sameersbn/gitlab:10.3.3 28 | ports: 29 | - "10080:80" 30 | - "10022:22" 31 | volumes: 32 | - ./gitlab/data:/home/git/data:Z 33 | - ./gitlab/logs:/var/log/gitlab:Z 34 | depends_on: 35 | - redis 36 | - postgresql 37 | env_file: 38 | - .env 39 | gitlab-ci: 40 | image: bravist/gitlab-ci-php-envoy:1.0 41 | container_name: gitlab-ci-php-envoy-runner 42 | volumes: 43 | - ./gitlab-ci/config:/etc/gitlab-runner:Z 44 | - ./gitlab-ci/.ssh:/root/.ssh:Z 45 | - /var/run/docker.sock:/var/run/docker.sock 46 | restart: always 47 | 48 | -------------------------------------------------------------------------------- /gitlab-ci/.ssh/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore -------------------------------------------------------------------------------- /gitlab-ci/Dockerfile: -------------------------------------------------------------------------------- 1 | FROM gitlab/gitlab-runner:alpine 2 | 3 | MAINTAINER bravist 4 | 5 | # https://pkgs.alpinelinux.org/packages 6 | 7 | # Mirror mirror switch to Ali-OSM (Alibaba Open Source Mirror Site) - http://mirrors.aliyun.com/ 8 | RUN echo 'http://mirrors.aliyun.com/alpine/latest-stable/main' > /etc/apk/repositories \ 9 | && echo '@community http://mirrors.aliyun.com/alpine/latest-stable/community' >> /etc/apk/repositories \ 10 | && echo '@testing http://mirrors.aliyun.com/alpine/edge/testing' >> /etc/apk/repositories 11 | 12 | # https://github.com/matriphe/docker-alpine-php/blob/master/7.0/FPM/Dockerfile 13 | # Environments 14 | ENV TIMEZONE Asia/Shanghai 15 | ENV PHP_MEMORY_LIMIT 512M 16 | ENV MAX_UPLOAD 50M 17 | ENV PHP_MAX_FILE_UPLOAD 200 18 | ENV PHP_MAX_POST 100M 19 | ENV COMPOSER_ALLOW_SUPERUSER 1 20 | 21 | 22 | # Mirror mirror switch to Alpine Linux - http://dl-4.alpinelinux.org/alpine/ 23 | RUN apk update \ 24 | && apk upgrade \ 25 | && apk add \ 26 | curl \ 27 | tzdata \ 28 | php7@community \ 29 | php7-dev@community \ 30 | php7-apcu@community \ 31 | php7-bcmath@community \ 32 | php7-xmlwriter@community \ 33 | php7-ctype@community \ 34 | php7-curl@community \ 35 | php7-exif@community \ 36 | php7-iconv@community \ 37 | php7-intl@community \ 38 | php7-json@community \ 39 | php7-mbstring@community\ 40 | php7-opcache@community \ 41 | php7-openssl@community \ 42 | php7-pcntl@community \ 43 | php7-pdo@community \ 44 | php7-mysqlnd@community \ 45 | php7-mysqli@community \ 46 | php7-pdo_mysql@community \ 47 | php7-pdo_pgsql@community \ 48 | php7-phar@community \ 49 | php7-posix@community \ 50 | php7-session@community \ 51 | php7-xml@community \ 52 | php7-simplexml@community \ 53 | php7-mcrypt@community \ 54 | php7-xsl@community \ 55 | php7-zip@community \ 56 | php7-zlib@community \ 57 | php7-dom@community \ 58 | php7-redis@community\ 59 | php7-tokenizer@community \ 60 | php7-gd@community \ 61 | php7-mongodb@testing \ 62 | php7-fileinfo@community \ 63 | php7-zmq@community \ 64 | php7-memcached@community \ 65 | openssh \ 66 | && cp /usr/share/zoneinfo/${TIMEZONE} /etc/localtime \ 67 | && echo "${TIMEZONE}" > /etc/timezone \ 68 | && apk del tzdata \ 69 | && rm -rf /var/cache/apk/* 70 | 71 | # https://github.com/docker-library/php/issues/240 72 | # https://gist.github.com/guillemcanal/be3db96d3caa315b4e2b8259cab7d07e 73 | # https://forum.alpinelinux.org/forum/installation/php-iconv-issue 74 | 75 | RUN apk add --no-cache --repository http://dl-3.alpinelinux.org/alpine/edge/testing gnu-libiconv 76 | ENV LD_PRELOAD /usr/lib/preloadable_libiconv.so php 77 | RUN rm -rf /var/cache/apk/* 78 | 79 | # Set environments 80 | RUN sed -i "s|;*date.timezone =.*|date.timezone = ${TIMEZONE}|i" /etc/php7/php.ini && \ 81 | sed -i "s|;*memory_limit =.*|memory_limit = ${PHP_MEMORY_LIMIT}|i" /etc/php7/php.ini && \ 82 | sed -i "s|;*upload_max_filesize =.*|upload_max_filesize = ${MAX_UPLOAD}|i" /etc/php7/php.ini && \ 83 | sed -i "s|;*max_file_uploads =.*|max_file_uploads = ${PHP_MAX_FILE_UPLOAD}|i" /etc/php7/php.ini && \ 84 | sed -i "s|;*post_max_size =.*|post_max_size = ${PHP_MAX_POST}|i" /etc/php7/php.ini && \ 85 | sed -i "s|;*cgi.fix_pathinfo=.*|cgi.fix_pathinfo= 0|i" /etc/php7/php.ini 86 | 87 | # composer 88 | RUN curl -sS https://getcomposer.org/installer | \ 89 | php -- --install-dir=/usr/bin/ --filename=composer 90 | 91 | RUN mkdir -p /root/.ssh 92 | RUN composer global require laravel/envoy 93 | 94 | VOLUME ["/root/.ssh"] 95 | 96 | CMD ["run", "--user=root", "--working-directory=/root"] -------------------------------------------------------------------------------- /gitlab-ci/config/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore -------------------------------------------------------------------------------- /gitlab/data/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore -------------------------------------------------------------------------------- /gitlab/logs/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore -------------------------------------------------------------------------------- /laravel-gitlab-runner.md: -------------------------------------------------------------------------------- 1 | # 使用Gitlab Runner 部署Laravel 项目 2 | 3 | ## 新建部署用户 4 | 5 | 创建一个deployer用户 6 | 7 | ```bash 8 | $ sudo useradd deployer 9 | ``` 10 | 修改用户权限，允许其新建目录等命令操作 11 | ```bash 12 | $ ls -l /etc/sudoers 13 | -r--r----- 1 root root 3985 10月 30 19:33 /etc/sudoers 14 | ``` 15 | `etc/sudoers`只有只读的权限，如果想要修改的话，需要先添加w权限 16 | 17 | ```bash 18 | $ chmod -v u+w /etc/sudoers 19 | ``` 20 | 在最下面增加一个用户 21 | ```bash 22 | $vim /etc/sudoers 23 | 24 | ... 25 | deployer ALL=(ALL) NOPASSWD: ALL 26 | ``` 27 | 这时候要记得将写权限收回 28 | ```bash 29 | chmod -v u-w /etc/sudoers 30 | ``` 31 | 32 | 设置用户密码 33 | 34 | ```bash 35 | $ passwd deployer 36 | ``` 37 | 38 | 登录验证 39 | 40 | ```bash 41 | $ ssh deployer@your_ip_address 42 | ``` 43 | 44 | 生成RSA秘钥对 45 | 46 | ```bash 47 | $ ssh-keygen -t rsa 48 | Generating public/private rsa key pair. 49 | Enter file in which to save the key (/home/deployer/.ssh/id_rsa): 50 | Created directory '/home/deployer/.ssh'. 51 | Enter passphrase (empty for no passphrase): 52 | Enter same passphrase again: 53 | Your identification has been saved in /home/deployer/.ssh/id_rsa. 54 | Your public key has been saved in /home/deployer/.ssh/id_rsa.pub. 55 | The key fingerprint is: 56 | SHA256:BGGNOhmUvmvaQT0nn3D3iMeISOT036Jj/+/77vqMdYY deployer@iz8vbh3xuahhi5gqllg1u1z 57 | The key's randomart image is: 58 | +---[RSA 2048]----+ 59 | | ...++ | 60 | | o.... | 61 | | .o+ . | 62 | | +=o . | 63 | | +o* S . | 64 | | o.. X B o . | 65 | | o.. B = . E o| 66 | | .o.o. o + o | 67 | | .o...o...o*B* | 68 | +----[SHA256]-----+ 69 | ``` 70 | 71 | 查看私钥 72 | 73 | ```bash 74 | $ cat /home/deployer/.ssh/id_rsa 75 | ``` 76 | 77 | ## 安装 Gitlab Runner 78 | 79 | root账户登录 80 | 81 | ```bash 82 | $ ssh root@your_ip_address 83 | ``` 84 | 85 | 添加Gitlab 官方仓库 86 | 87 | ```bash 88 | # For RHEL/CentOS/Fedora 89 | $ curl -L https://packages.gitlab.com/install/repositories/runner/gitlab-runner/script.rpm.sh | sudo bash 90 | ``` 91 | 92 | 安装Gitlab Runner 93 | 94 | ```bash 95 | # For RHEL/CentOS/Fedora 96 | $ sudo yum install gitlab-runner 97 | ``` 98 | 99 | 查看安装版本 100 | 101 | ```bash 102 | $ gitlab-runner -v 103 | Version: 12.4.1 104 | Git revision: 05161b14 105 | Git branch: 12-4-stable 106 | GO version: go1.10.8 107 | Built: 2019-10-28T12:49:57+0000 108 | OS/Arch: linux/amd64 109 | ``` 110 | 111 | > 更多安装参考官方：https://docs.gitlab.com/runner/install/linux-repository.html 112 | 113 | ## 新注册Gitlab Runner 114 | 115 | 登录项目仓库，查看Token并按照下面的配置方式设置参数 116 | 117 | ![image-20191030161106282](./assets/image-20191030161106282.png) 118 | 119 | 注册成功后，在服务端和Gitlab中查看结果 120 | 121 | ```bash 122 | $ gitlab-runner list 123 | ``` 124 | 125 | ## 新建`.gitlab.ci.yml`配置文件 126 | 127 | 切换项目仓库分支为：`develop`，在其中添加`.gitlab-ci.yml`文件，验证内容如下： 128 | 129 | ```bash 130 | before_script: 131 | - echo "Before script" 132 | - cd /var/www/ 133 | building: 134 | stage: build 135 | script: 136 | - echo "building..." 137 | testing: 138 | stage: test 139 | script: 140 | - echo "testing..." 141 | deploying: 142 | stage: deploy 143 | script: 144 | - echo "deploying..." 145 | ``` 146 | 147 | 提交代码，如果能看到下面内容，简单的CI/CD流程就成功完成了。 148 | 149 | ![image-20191030172638128](./assets/image-20191030172638128.png) 150 | 151 | 152 | 153 | ## 推荐CI/CD 配置 154 | 155 | 项目、系统、环境等不尽相同，推荐部署Laravel项目按照的`dev`，`test`，`production`三个环境构建项目，仓库分支保持`develop`，`testing`，`master`三个分支对应前面三个环境构建代码，每个环境的应用参数也不同，可以采用`.env.dev`，`.env.test`，`.env.production`保存参数。 156 | 157 | ```bash 158 | variables: 159 | RELEASES_STORAGE_DIR: '/var/www/$CI_COMMIT_REF_NAME/$CI_PROJECT_PATH/storage' 160 | CREATE_RELEASES_STORAGE_DIR: '[ -d $RELEASES_STORAGE_DIR ] || sudo mkdir -p $RELEASES_STORAGE_DIR' 161 | RELEASES_DIR: '/var/www/$CI_COMMIT_REF_NAME/$CI_PROJECT_PATH/releases' 162 | CREATE_RELEASE_DIR: '[ -d $RELEASES_DIR ] || sudo mkdir -p $RELEASES_DIR' 163 | NEW_RELEASES_DIR: '$RELEASES_DIR/$CI_COMMIT_SHORT_SHA' 164 | CREATE_NEW_RELEASES_DIR: '[ -d $NEW_RELEASES_DIR ] || sudo mkdir -p $NEW_RELEASES_DIR' 165 | BEFORE_CHMOD: 'sudo chown -R deployer:deployer $NEW_RELEASES_DIR' 166 | BEFORE_CHMOD_VENDOR: 'sudo chown -R deployer:deployer $NEW_RELEASES_DIR/vendor' 167 | AFTER_CHMOD: 'sudo chown -R apache:apache /var/www/$CI_COMMIT_REF_NAME && sudo chown -R apache:apache $RELEASES_STORAGE_DIR && sudo chmod -R 777 $RELEASES_STORAGE_DIR' 168 | CD_NEW_RELEASES_DIR: 'cd $NEW_RELEASES_DIR' 169 | CD_RELEASES_DIR: 'cd $RELEASES_DIR' 170 | #Linux删除除了某个文件之外的所有文件/目录 171 | CLEAN_RELEASES_DIR: 'ls |grep -v $CI_COMMIT_SHORT_SHA |xargs sudo rm -rf' 172 | RM_RELEASE_STORAGE_DIR: 'sudo rm -rf $NEW_RELEASES_DIR/storage' 173 | LN_RELEASE_STORAGE_DIR: 'sudo ln -nfs $RELEASES_STORAGE_DIR $NEW_RELEASES_DIR/storage' 174 | LN_RELEASE_DIR: 'sudo ln -nfs $NEW_RELEASES_DIR /var/www/$CI_COMMIT_REF_NAME/$CI_PROJECT_PATH/current' 175 | MV_REPO: 'sudo mv -fv /home/deployer/$CI_PROJECT_DIR/* $NEW_RELEASES_DIR' 176 | CP_DEV_ENV: 'cp /home/deployer/$CI_PROJECT_DIR/.env.dev $NEW_RELEASES_DIR/.env' 177 | CREATE_FRAMEWORK_CACHE: '[ -d $RELEASES_STORAGE_DIR/framework/cache ] || sudo mkdir -p $RELEASES_STORAGE_DIR/framework/cache' 178 | CREATE_FRAMEWORK_SESSIONS: '[ -d $RELEASES_STORAGE_DIR/framework/sessions ] || sudo mkdir -p $RELEASES_STORAGE_DIR/framework/sessions' 179 | CREATE_FRAMEWORK_TESTING: '[ -d $RELEASES_STORAGE_DIR/framework/testing ] || sudo mkdir -p $RELEASES_STORAGE_DIR/framework/testing' 180 | CREATE_FRAMEWORK_VIEWS: '[ -d $RELEASES_STORAGE_DIR/framework/views ] || sudo mkdir -p $RELEASES_STORAGE_DIR/framework/views' 181 | 182 | 183 | before_script: 184 | - echo "Before script" 185 | - echo $CI_COMMIT_REF_NAME 186 | - echo $CI_PROJECT_PATH 187 | - echo $CI_COMMIT_SHORT_SHA 188 | - echo $CI_REPOSITORY_URL 189 | - echo $CI_PROJECT_DIR 190 | - 'eval $CREATE_RELEASES_STORAGE_DIR' # will execute 191 | - 'eval $CREATE_RELEASE_DIR' # will execute 192 | - 'eval $CREATE_NEW_RELEASES_DIR' # will execute 193 | - 'eval $CD_NEW_RELEASES_DIR' 194 | 195 | 196 | stages: 197 | - build 198 | - test 199 | - deploy-dev 200 | 201 | building: 202 | stage: build 203 | script: 204 | - echo "Move repo..." 205 | - echo $NEW_RELEASES_DIR 206 | - 'eval $BEFORE_CHMOD' 207 | - 'eval $MV_REPO' 208 | - composer install 209 | - 'eval $BEFORE_CHMOD_VENDOR' 210 | 211 | testing: 212 | stage: test 213 | script: 214 | - echo "testing..." 215 | # - php ./vendor/bin/phpunit 216 | 217 | deploying_dev: 218 | stage: deploy-dev 219 | script: 220 | - echo "deploying dev..." 221 | - 'eval $CP_DEV_ENV' 222 | - php artisan key:generate 223 | - 'eval $CREATE_FRAMEWORK_CACHE' 224 | - 'eval $CREATE_FRAMEWORK_SESSIONS' 225 | - 'eval $CREATE_FRAMEWORK_TESTING' 226 | - 'eval $CREATE_FRAMEWORK_VIEWS' 227 | - php artisan cache:clear 228 | - php artisan config:clear 229 | - php artisan storage:link 230 | - php artisan migrate --force 231 | - php artisan passport:keys 232 | - echo "Restarting supervisor" 233 | - sudo supervisorctl restart all 234 | - echo "Linking storage directory" 235 | - 'eval $RM_RELEASE_STORAGE_DIR' 236 | - 'eval $LN_RELEASE_STORAGE_DIR' 237 | - echo 'Linking current directory' 238 | - 'eval $AFTER_CHMOD' 239 | - 'eval $LN_RELEASE_DIR' 240 | - echo 'Removing earlier app' 241 | - 'eval $CD_RELEASES_DIR' 242 | - 'eval $CLEAN_RELEASES_DIR' 243 | only: 244 | - develop 245 | 246 | ``` 247 | 248 | 参考 249 | 250 | > 1. [Test and deploy Laravel applications with GitLab CI/CD and Envoy](https://docs.gitlab.com/ce/ci/examples/laravel_with_gitlab_and_envoy/index.html) 251 | > 2. [GitLab CI/CD environment variables](https://docs.gitlab.com/ee/ci/variables/README.html) 252 | > 3. https://github.com/bravist/gitlab-ci-docker 253 | > 4. https://github.com/tuandm/laravue/blob/master/Envoy.blade.php 254 | 255 | 256 | 257 | ## 可能的问题 258 | 259 | ### 1. is this a git repository? 260 | 261 | > Gitlab Runner Nginx 自定义端口后出现无法克隆仓库，Gitlab issue: [unable to access with 8080 web port](https://gitlab.com/gitlab-org/gitlab-runner/issues/1148) 262 | 263 | ```bash 264 | Running with gitlab-runner 12.4.1 (05161b14) 265 | on Gitlab Runner For Deploy 4LgtuQbB 266 | Using SSH executor... 267 | Running on iz8vbh3xuahhi5gqllg1u1z via iz8vbh3xuahhi5gqllg1u1z... 268 | Fetching changes with git depth set to 50... 269 | warning: templates not found builds/4LgtuQbB/0/zhangqiuzhe/api.tmp/git-template 270 | Reinitialized existing Git repository in /home/deployer/builds/4LgtuQbB/0/zhangqiuzhe/api/.git/ 271 | fatal: http://gitlab-ci-token:[MASKED]@gitlab.higgses.com/zhangqiuzhe/api.git/info/refs not valid: is this a git repository? 272 | ERROR: Job failed: Process exited with: 1. Reason was: () 273 | 274 | ``` 275 | 276 | 修改Gitlab 内置Nginx监听端口号，比如设置：`8888` 277 | 278 | ```bash 279 | vi /var/opt/gitlab/nginx/conf/gitlab-http.conf 280 | 281 | ## 282 | ################################### 283 | ## configuration ## 284 | ################################### 285 | 286 | 287 | server { 288 | listen *:8888; 289 | 290 | 291 | server_name your_domain; 292 | ... 293 | ``` 294 | 295 | 修改`external_url`端口号，比如设置：`8888` 296 | 297 | ```bash 298 | vim /etc/gitlab/gitlab.rb 299 | 300 | ## GitLab configuration settings 301 | ##! This file is generated during initial installation and **is not** modified 302 | ##! during upgrades. 303 | ##! Check out the latest version of this file to know about the different 304 | ##! settings that can be configured by this file, which may be found at: 305 | ##! https://gitlab.com/gitlab-org/omnibus-gitlab/raw/master/files/gitlab-config-template/gitlab.rb.template 306 | 307 | 308 | ## GitLab URL 309 | ##! URL on which GitLab will be reachable. 310 | ##! For more details on configuring external_url see: 311 | ##! https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab 312 | external_url 'http://your_domain:8888' 313 | ... 314 | ``` 315 | 316 | 317 | 318 | 修改了配置需要更新并重启 319 | 320 | ```bash 321 | $ gitlab-ctl reconfigure 322 | 323 | $ gitlab-ctl restart 324 | ``` 325 | 326 | 327 | 328 | ### 2. Pipeline 不执行 329 | 330 | Push 代码后Pipelines 卡住不执行，提示没有可以使用的 runner 。如果出现这种情况，需要在注册成功的 runner 中编辑一下设置，运行未标记的作业需要勾选 331 | 332 | ![image-20191030165624205](./assets/image-20191030165624205.png) 333 | 334 | ![image-20191030165643847](./assets/image-20191030165643847.png) 335 | -------------------------------------------------------------------------------- /postgresql/data/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore -------------------------------------------------------------------------------- /redis/.gitignore: -------------------------------------------------------------------------------- 1 | * 2 | !.gitignore --------------------------------------------------------------------------------