Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
/ taupage Public archive

THIS PROJECT IS NOT LONGER ACTIVELY MAINTAINED - The base Amazon Machine Image (AMI) allowing dockerized applications to run with STUPS

License

Notifications You must be signed in to change notification settings

zalando-stups/taupage

Repository files navigation

Zalando AMI generation tooling

Build Status Join the chat at https://gitter.im/zalando-stups/taupage

NOTE

While we do not consider Taupage to have reached its end of life, we are currently not planning to add new features or extend its functionalities. We will consider any pull request, but we do not plan to directly work on enhancements.

Prerequisites

You need to have jq and AWS CLI preinstalled.

Build a new AMI

You need to be logged in (mai login). (As a configuration example, you can find the file config-stups-example.sh in the code base. You should modify it to suit it to your needs.)

$ ./create-ami.sh ./config-stups.sh <version>

This will spin up a new server, configure it, create an AMI from it, terminate the server and share the AMI. If you want to debug the server after setup, you can add a --dry-run flag: AMI generation, terminating and sharing will be skipped.

$ ./create-ami.sh --dry-run ./config-stups.sh

See the STUPS documentation for more information.

Directory structure

  • /build/ (scripts and files for the initial setup)
    • setup.d/ (all setup scripts that get executed on the server)
  • /runtime/ (everything, that has to be present during runtime)
  • /tests/ (contains various tests, such as python, serverspec and shell script tests)