This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

# docker-conduct

[![Build Status](https://travis-ci.org/nick-allen/docker-conduct.svg)](https://travis-ci.org/nick-allen/docker-conduct)

Install and run docker-compose projects as portable apps available from various types of remote or local sources

# Quick Start

docker-conduct install [–name <app_name>] <remote_uri> docker-conduct run <app_name>

# Installation

docker-conduct is available as a python package and as a docker image.

## Host Install

pip install docker-conduct

This will install the docker-conduct command. Apps using docker-compose can then be installed and run locally.

e.g.

docker-conduct install [–name <app_name>] <remote_uri> docker-conduct run <app_name>

## Docker Install

docker pull nickallen/docker-conduct

Using docker-conduct from the docker image requires two volumes to be mounted for long-term usage.

The working directory should be mounted to /target, and the docker.sock file should be mounted to /var/run/docker.sock

All options following the docker run are the same as running docker-conduct on the host

e.g.

docker run -v $(pwd):/target -v /var/run/docker.sock:/var/run/docker.sock nickallen/docker-conduct run <app_name>

# Important Files

## Local

These files are present in the working directory when running docker-conduct

### .conduct/

Automatically created in working directory containing all data related to the current docker-conduct context

## Remote

These files should exist in the remote

### .conduct.yml

Optional file in root directory of remote package that can specify various parameters and configuration options for the respective app

### docker-compose.yml

docker-compose configuration file found in the root of the remote project. A different file can be specified in the .conduct.yml

Release History

Release History

0.1.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting