What happens when you Dockerize your Laravel testing environment and throw it at Gitlab CI?
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
ssh/5.6
LICENSE
README.md

README.md

Gitlabby Dockerish Laravel

What happens when you Dockerize your Laravel testing environment and throw it at Gitlab CI?

This repository includes several files required to run the Gitlab CI for your Laravel. The Docker container is pre-packaged with Laravel vendor dependecies, which reduces the number of files required to be downloaded.

It pulls the PHP Laravel image from this repository.

Support

  • PHP 7.1/7.2
  • Laravel 5.6
  • MySQL 5.5
  • Redis (Your Laravel will require predis/predis composer package)
  • Laravel Dusk (UI automated testing)

Usage

There are several deployment techniques available: SSH and Docker

SSH Deployment

Copy the following files and drop them in your Laravel base repository:

  • .env.gitlab-testing
  • .gitlab-ci.yml
  • .gitlab-build.sh
  • .gitlab-test.sh
  • .gitlab-staging-deploy.sh

Ensure that your repository has set a Git deployment remote and you have created a SSH key for access to this remote.

Open up .gitlab-ci.yml and set the variables for the following:

  GIT_DEPLOYMENT_URL: git@gitlab.com:woohuiren/test-laravel-project.git
  GIT_DEPLOYMENT_REMOTE: staging
  GIT_DEPLOYMENT_BRANCH: master
  SSH_PRIVATE_KEY: somethingsomethingblahblah # Recommended to put into GitLab secret variables instead