https://github.com/edenreich/voyager-laravel-backend

A simple repository for deploying a laravel voyager backend on digitalocean kubernetes cluster.
https://github.com/edenreich/voyager-laravel-backend

Last synced: about 5 hours ago
JSON representation

A simple repository for deploying a laravel voyager backend on digitalocean kubernetes cluster.

• Host: GitHub
• URL: https://github.com/edenreich/voyager-laravel-backend
• Owner: edenreich
• Created: 2019-08-02T23:25:52.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2023-02-02T07:21:49.000Z (almost 2 years ago)
• Last Synced: 2023-03-04T09:40:50.628Z (over 1 year ago)
• Language: PHP
• Homepage:
• Size: 316 KB
• Stars: 2
• Watchers: 2
• Forks: 1
• Open Issues: 3
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        

# Complete Admin Panel PHP-Laravel-Voyager Application Including IaC Hosted on Digitalocean

This repository provide a kubernetes cluster with access to dockerhub private registry, this cluster is very minimalistic and contains only one node, you may increase it for your own need.

To do so just increase `cluster_node_count` variable.

The `src` directory will be packaged into a docker image and pushed to a dockerhub. 

Do note that on the first run the creation of the cluster on digitalocean can take up to `20min`.

This setup goal is to create a kubernetes cluster for each environment - `staging` or `production`, depending on the chosen workspace, defaults to `staging`.

## Todo

 [ ] Add a managed RDS instance.

## Technologies

- Terraform v0.12.6

- Docker Client v18.09.6

- Kubernetes Client (kubectl v1.15.0)

- PHP v7.3.3-fpm on alpine3.8 OS

## Authentication

Before you begin you have to make sure that terraform is authenticated with digitalocean: `export TF_VAR_do_token='[digitalocean-access-token]'`.

Also make sure that your computer is authenticated with dockerhub. (a `~/.docker/config` file should be present, this will be uploaded as a secret to kubernetes cluster, for pulling private images from your dockerhub registry).

## Deploy to Staging

1. From the root directory build and tag a docker image `docker build -t [repository]/[image]:[version] -f ops/docker/app/Dockerfile .`.

2. Push the image to a registry `docker push [repository]/[image]:[version]`.

3. Enter the terraform directory `cd ops/terraform`.

4. Download needed plugins `terraform init`.

5. Create a plan `terraform plan -out terraform.tfplan`.

6. Apply the plan `terraform apply -autoapprove`.

## Deploy to Production

1. From the root directory build and tag a docker image `docker build -t [repository]/[image]:[version] -f ops/docker/app/Dockerfile .`.

2. Push the image to a registry `docker push [repository]/[image]:[version]`.

3. Enter the terraform directory `cd ops/terraform`.

4. Download needed plugins `terraform init`.

5. Switch to production workspace `terraform workspace select production || terraform workspace new production`.

6. Create the plan `terraform plan -out terraform.tfplan`.

7. Apply the plan `terraform apply -autoapprove`.

## Client Access

Assuming you ran one of the above mentioned deployments, a configuration file of the 

cluster was downloaded from the digitalocean provider and you should have an access to the cluster.

To test it, we can issue the following command from the `ops/terraform` directory:

`kubectl --kubeconfig config/[workspace]-kubeconfig.yaml get pods,services`

## Rolling Updates

Simply cd into `ops/terraform` modifiy the docker image (`backend_pod_image`) and run `terraform apply`, 

ideally you change this version using a pipeline that exports a `TF_VAR_backend_pod_image` env variable with the value of the latest image built.