Sign inSign up

hoist/core-box

By hoist

Updated over 10 years ago

Hoist's Core Node.js/io.js box with a number of built in dependencies

Image
0

2.5K

hoist/core-box repository overview

Hoist Services

This repository holds infrastructure services for Hoist's Docker/CoreOS infrastructure.

*.service files

Each of these files represent a service that runs on CoreOS.

Introduction to Unit Files

  • clean-docker-containers (service/timer):

    regularly cleans out any inactive containers

  • clean-docker-images (service/timer):

    regularly cleans any unreferenced docker images

  • consul-alerts:

    monitors consul and posts alerts to Slack (Dockerfile)

  • consul-nginx:

    monitors consul and rewrites nginx config based on service registration (Dockerfile)

  • mongo-backup (service/timer)

    runs the mongo backup service that backs up to MongoDB Cloud (Dockerfile)

  • mongo-monitoring (service/timer)

    runs the mongo monitoring service for the MongoDB Cloud (Dockerfile)

  • nginx

    runs nginx as configured by the standard NGINX image and binds to the config container (to allow access to certificates)

  • redis-configure

    configures redis instance as a sidekick to redis

  • redis-sentinal

    sets up a sentinal image for the redis cluster

  • redis

    sets up a redis docker container

  • registry

    sets up a Docker registry

Clusters

these are ways of setting up test clusters

  • test (docker compose test stack)

    this is the standard test docker-compose for Hoist applications.

    • download docker-compose

      Install docker, docker-compose and docker-machine.

      Assuming you have Homebrew installed:

      brew install docker docker-compose docker-machine
      
    • setup docker-machine

      Docker machine getting started guide

      docker-machine create --driver virtualbox dev
      eval "$(docker-machine env dev)"
      

      I have the following lines in my ~/.bash_profile

      /usr/local/bin/docker-machine start dev
      eval "$(/usr/local/bin/docker-machine env dev)"
      
    • start the cluster just run the start.sh script in the test directory

      cd /path/to/clusters/test && ./start.sh
      
  • vagrant (vagrant based CoreOS stack)

    this is a vagrant based CoreOS cluster which is the best way to test fleet unit files.

    • Start the cluster

    ensure you have Homebrew cask installed by following the instructions

    brew install caskroom/cask/brew-cask
    

    then use cask to install vagrant

    brew cask install vagrant
    

    then you can up the cluster

    cd /path/to/clusters/vagrant && vagrant up
    

Tag summary

Content type

Image

Digest

sha256:dda3aaaca

Size

256.6 MB

Last updated

almost 11 years ago

docker pull hoist/core-box