Skip to content

Latest commit

 

History

History
119 lines (94 loc) · 3.53 KB

README.md

File metadata and controls

119 lines (94 loc) · 3.53 KB
Raw

Fristen

👾 I don't remember what the name even means

This is an ansible playbook that sets up a Git-driven deployment style Jekyll instance on a fresh linux machine, based on the workflow I use to deploy the rare blog post gems of knowledge I tend to write. The explanation is in the Jekyll official blog post

These are the things that the playbook sets up (unless specified, the versions installed are the ones that come with running apt-get install):

  1. Nginx as the server
  2. fail2ban with some custom rules
  3. Git (obtained from git-core ppa)
  4. Nodejs 6 (execjs backend if required)
  5. Ruby-Install
  6. Chruby
  7. Ruby (hard-coded to 2.4.1), customisable via a variable
  8. Bundler
  9. A bare Git repository on the remote that has a Git hook. This is used to listen to Git pushes, and then clone the blog from GitHub, and build the application

I haven't made this terribly configurable, but you can try out modifying the variables and stuff to customise it to suit your personal needs.

Linux compatibility

I've tested this on Debian Jessie, and Ubuntu 14. Ubuntu latest (I think Xenial is the one I tried) doesn't ship with Python 2.7, and only has a python3 binary, which made ansible crash, and I didn't investigate much because I don't intend to use it.

Playbook Layout

All the individual steps are separated into ansible roles, which have a particular layout structure. Each role has a tasks folder, which is the most important one, and optionally vars, templates, files.

roles
├── chruby
│   ├── tasks
│   │   └── main.yml
│   └── vars
│       └── main.yml
├── common
│   └── tasks
│       └── main.yml
├── fail2ban
│   ├── files
│   │   ├── fail2ban.conf
│   │   ├── nginx-login.conf
│   │   ├── nginx-noscript.conf
│   │   └── nginx-proxy.conf
│   └── tasks
│       └── main.yml
├── git-hook
│   ├── tasks
│   │   └── main.yml
│   ├── templates
│   │   └── post-receive
│   └── vars
│       └── main.yml
├── nginx
│   ├── handlers
│   │   └── main.yml
│   ├── tasks
│   │   └── main.yml
│   ├── templates
│   │   └── webserver.conf
│   └── vars
│       └── main.yml
├── ruby
│   ├── tasks
│   │   └── main.yml
│   ├── templates
│   │   └── ruby-version
│   └── vars
│       └── main.yml
└── ruby-install
    ├── tasks
    │   └── main.yml
    └── vars
        └── main.yml

Usage

Run:

ansible-playbook -l <hosts> all.yml

Might do in the future

  1. Add let's encrypt setup
  2. Add logrotate configurations, and tests for those
  3. Add a way to output all the exact git remotes properly to stdout.
  4. More conservative installations. Currently, Ruby is installed even if present. That should be done only if ruby is not present. Same goes for chruby, ruby-install etc.
  5. Cleanup unneeded user-creation
  6. May be avoid installing Ruby dependency managers.