For educational reasons I've decided to create my own CA. Here is what I learned.
Lets get some context first.
| // --- Compiling --- | |
| $ wget http://download.redis.io/releases/redis-2.8.3.tar.gz | |
| $ tar xzvf redis-2.8.3.tar.gz | |
| $ cd redis-2.8.3 | |
| $ make | |
| $ make install | |
| // --- or using yum --- | |
| $ rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm | |
| $ rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-6.rpm |
| <?php | |
| $cb = function ($fn) { | |
| return $fn; | |
| }; | |
| echo <<<HEREDOC | |
| Hello, {$cb(ucfirst('world'))} | |
| HEREDOC; |
| #!/bin/bash | |
| ## List all manually installed packages on a debian/ubuntu system | |
| ## manually installed means: | |
| ## 1. not pre-installed with the system | |
| ## 2. not marked auto-installed by apt (not dependencies of other | |
| ## packages) | |
| ## Note: pre-installed packages that got updated still needs to be | |
| ## filtered out. |
| <div>Execution ${execution.id} was <b>${execution.status}</b></div> | |
| <ul> | |
| <li><a href="${execution.href}">Execution result</a></li> | |
| <li><a href="${job.href}">Job</a></li> | |
| <li><a href="${execution.projectHref}">Project: ${execution.project}</a></li> | |
| <li><a href="${rundeck.href}">Rundeck</a></li> | |
| </ul> | |
| <p> | |
| </p> |
| source.c | |
| source.c++ | |
| source.coffee | |
| source.css | |
| source.css.less | |
| source.css.scss | |
| source.gfm | |
| source.git-config | |
| source.go | |
| source.java |
| { | |
| "name": "my-app", | |
| "version": "1.0.0", | |
| "description": "My test app", | |
| "main": "src/js/index.js", | |
| "scripts": { | |
| "jshint:dist": "jshint src/js/*.js", | |
| "jshint": "npm run jshint:dist", | |
| "jscs": "jscs src/*.js", | |
| "browserify": "browserify -s Validating -o ./dist/js/build.js ./lib/index.js", |
To remove a submodule you need to:
Finding Packer-generated AMIs automatically after builds
The basic technique is to have Packer add a tag with a unique value during the build, and use AWS' built-in filtering capabilities to find that specific AMI after the build finishes.