| stages: | |
| - Lint images | |
| - Build and publish images | |
| ## Load a node.js image, install dockerlint and lint all Dockerfiles | |
| linting: | |
| stage: Lint images | |
| image: node:4-alpine | |
| script: | |
| - npm install -g dockerlint && npm cache clean |
| #!/bin/bash | |
| # In honor of the remarkable Windson | |
| #/bin/bash | |
| namespace=$1 | |
| if [[ -z "$namespace" ]]; then | |
| echo "Use "$(basename "$0")" NAMESPACE"; | |
| exit 1; | |
| fi |
I have tried this setup and although it works and may be good for ceratin circumstances I would advise using ubuntu as the base with docker, docker-compose, and portainer. https://gist.github.com/mow4cash/626275e095f7f90898944a85d66b3be6
Link to my docker run file https://gist.github.com/mow4cash/6a25343cdeb0cd115f263dea0a3b623d
| #!/bin/bash | |
| # Usage: ./get_kubeconfig_custom_cluster_rancher2.sh cluster_name | |
| # Needs to be run on the server running `rancher/rancher` container | |
| # Check if jq exists | |
| command -v jq >/dev/null 2>&1 || { echo "jq is not installed. Exiting." >&2; exit 1; } | |
| # Check if clustername is given | |
| if [ -z "$1" ]; then | |
| echo "Usage: $0 [clustername]" |
This has been updated to install Dashboard v2.0.0, see below for pre v2.0.0 instructions
Generate the kubeconfig file for your cluster using the Kubeconfig File button in the Cluster view of your cluster.
| This project has been moved to a GitHub repository to allow Pull Requests. | |
| See: https://github.com/Ewpratten/youtube_ad_blocklist |
I posted several talks about compiling PHP from source, but everyone was trying to convince me that a package manager like Homebrew was a more convenient way to install.
The purpose of Homebrew is simple: a package manager for macOS that will allow you to set up and install common packages easily and allows you to update frequently using simple commands.
I used a clean installation of macOS Sierra to ensure all steps could be recorded and tested. In most cases you already have done work on your Mac, so chances are you can skip a few steps in this tutorial.
I’ve made this according to the installation instructions given on GetGrav.
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| Using MongoDB in golang with mgo |
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |