| # This docker-compose file intent to create a multi-container application | |
| # that runs a Jenkins container connected via TLS to a Docker-in-Docker (dind) container as Docker daemon. | |
| # | |
| # Advice about this approach can be found at: | |
| # http://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ | |
| # | |
| # As well discussion about another alternatives on this setup can be found at: | |
| # https://forums.docker.com/t/using-docker-in-a-dockerized-jenkins-container/322/11 | |
| # | |
| # Quick reference about Docker-in-Docker can be fount at: |
| 'use strict'; | |
| const crypto = require('crypto'); | |
| const ENC_KEY = "bf3c199c2470cb477d907b1e0917c17b"; // set random encryption key | |
| const IV = "5183666c72eec9e4"; // set random initialisation vector | |
| // ENC_KEY and IV can be generated as crypto.randomBytes(32).toString('hex'); | |
| const phrase = "who let the dogs out"; | |
| var encrypt = ((val) => { |
| package main | |
| import( | |
| "log" | |
| "net/url" | |
| "net/http" | |
| "net/http/httputil" | |
| ) | |
| func main() { |
Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).
