AProx :: Docker Utilities

CommonJava top-level parent POM.

License	Apache License, Version 2.0
Categories	Docker Container Virtualization Tools
GroupId	org.commonjava.aprox.docker
ArtifactId	aprox-docker-utils
Last Version	0.22.0-1
Release Date	Jun 26, 2015
Type	pom
Description	AProx :: Docker Utilities CommonJava top-level parent POM.
Project URL	https://github.com/Commonjava/aprox-docker
Source Code Management	https://github.com/Commonjava/aprox-docker

Download aprox-docker-utils

Filename	Size
aprox-docker-utils-0.22.0-1.pom
aprox-docker-utils-0.22.0-1.tar.gz	3 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.commonjava.aprox.docker/aprox-docker-utils/ -->
<dependency>
    <groupId>org.commonjava.aprox.docker</groupId>
    <artifactId>aprox-docker-utils</artifactId>
    <version>0.22.0-1</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.commonjava.aprox.docker/aprox-docker-utils/
implementation 'org.commonjava.aprox.docker:aprox-docker-utils:0.22.0-1'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.commonjava.aprox.docker/aprox-docker-utils/
implementation ("org.commonjava.aprox.docker:aprox-docker-utils:0.22.0-1")

Apache Buildr

'org.commonjava.aprox.docker:aprox-docker-utils:pom:0.22.0-1'

Apache Ivy

<dependency org="org.commonjava.aprox.docker" name="aprox-docker-utils" rev="0.22.0-1">
  <artifact name="aprox-docker-utils" type="pom" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.commonjava.aprox.docker', module='aprox-docker-utils', version='0.22.0-1')
)

Scala SBT

libraryDependencies += "org.commonjava.aprox.docker" % "aprox-docker-utils" % "0.22.0-1"

Leiningen

[org.commonjava.aprox.docker/aprox-docker-utils "0.22.0-1"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

There are no modules declared in this project.

Docker Utilities and Image Files for Indy

This repository contains a set of init scripts for setting up indy docker containers of three flavors:

• A stripped-down volumes container (init-indy-volumes)
• An Indy server container meant to work with the volume container (init-indy-server)
• A standalone Indy server container (init-indy-server-no-vols)

You can run any of the above scripts with -h to see the available options.

It also contains an autodeploy script (./scripts/autodeploy-indy-server) that you can add to your cron jobs, to autodeploy an Indy tarball in dev-mode. Systemd scripts are provided in the systemd/ directory, for maintaining active Indy containers, with one service definition for each of the init scripts above.

Finally, it contains the docker image source materials (Dockerfile + supporting scripts) for the two basic image types (server and volume container).

Quickstart for CentOS 7

This is intended to be more or less a list of instructions for you to run. It would take a bit more effort to turn it into a really functional script:

#!/bin/bash

yum -y update
yum -y install epel-release
yum -y install docker tree lsof python-lxml python-httplib2
systemctl enable docker
systemctl start docker

# ./scripts/init-indy-volumes -h
./scripts/init-indy-volumes

# ./scripts/init-indy-server -h
./scripts/init-indy-server -p 80 -q

#Or, if you want, you can leave off the '-q' option and watch the server come up
#...then use CTL-C to exit the tty (the container will keep running)

cp systemd/indy-volumes.service systemd/indy.service /etc/systemd/system
systemctl enable indy-volumes indy

docker stop indy indy-volumes
systemctl start indy-volumes
systemctl start indy

# Use this to see the server log as it starts up, to make sure it boots properly.
journalctl -f

Red Hat NOS

Middleware pipeline content management projects

Versions

Version
0.22.0-1 Jun 26, 2015
0.19.2-3 Apr 27, 2015
0.19.2-2 Apr 27, 2015
0.19.2-1 Apr 14, 2015
0.19.1-3 Apr 3, 2015
0.19.1-2 Apr 2, 2015
0.19.1-1 Mar 17, 2015
0.19.1 Mar 16, 2015