Skip to content

Update readme to fix broker dockerhub links #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update readme to fix broker dockerhub links #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,29 +1,29 @@
# Ubuntu and Alpine Docker images which use the Chaperone process manager

This repository is used to build several base-iamges which use the
This repository is used to build several base-images which use the
[Chaperone](http://garywiz.github.io/chaperone/guide/chap-intro.html) lightweight process manager.

Several images are included based upon Ubuntu 14.04:

* chaperone-baseimage (A framework for Chaperone-based development. On
[Docker Hub as chaperone-baseimage](https://registry.hub.docker.com/u/chapdev/chaperone-baseimage).
[Docker Hub as chaperone-baseimage](https://registry.hub.docker.com/r/chapdev/chaperone-baseimage).
* chaperone-lamp (A LAMP image managed by Chaperone. On
[Docker Hub as chaperone-lamp](https://registry.hub.docker.com/u/chapdev/chaperone-lamp).
[Docker Hub as chaperone-lamp](https://registry.hub.docker.com/r/chapdev/chaperone-lamp).
* chaperone-lemp (A LEMP image with Nginx instead of Apache, managed by Chaperone. On
[Docker Hub as chaperone-lemp](https://registry.hub.docker.com/u/chapdev/chaperone-lemp).
[Docker Hub as chaperone-lemp](https://registry.hub.docker.com/r/chapdev/chaperone-lemp).
* chaperone-apache (An Apache-only image, managed by Chaperone. On
[Docker Hub as chaperone-lemp](https://registry.hub.docker.com/u/chapdev/chaperone-apache).
[Docker Hub as chaperone-lemp](https://registry.hub.docker.com/r/chapdev/chaperone-apache).

In addition, these images are designed for leaner deployments, and are based upon Alpine Linux:

* chaperone-alpinebase (A 55MB Alpine Linux image including Python3, managed by Chaperone. On
[Docker Hub as chaperone-alpinebase](https://registry.hub.docker.com/u/chapdev/chaperone-alpinebase).
[Docker Hub as chaperone-alpinebase](https://registry.hub.docker.com/r/chapdev/chaperone-alpinebase).
* chaperone-alpinejava (A 210MB Alpine image containing Oracle Java 8 and Python3, managed by Chaperone. On
[Docker Hub as chaperone-alpinejava](https://registry.hub.docker.com/u/chapdev/chaperone-alpinejava).
[Docker Hub as chaperone-alpinejava](https://registry.hub.docker.com/r/chapdev/chaperone-alpinejava).
* alpine-nginx-php (A 75MB Alpine image containing Nginx, PHP, Python3, managed by Chaperone. On
[Docker Hub as alpine-nginx-php](https://registry.hub.docker.com/u/chapdev/alpine-nginx-php).
[Docker Hub as alpine-nginx-php](https://registry.hub.docker.com/r/chapdev/alpine-nginx-php).
* alpine-nginx-django (A 87MB Apine image containing Nginx, uWSGI, Python3, and Django 1.9, managed by Chaperone. On
[Docker Hub as alpine-nginx-django](https://registry.hub.docker.com/u/chapdev/alpine-nginx-django).
[Docker Hub as alpine-nginx-django](https://registry.hub.docker.com/r/chapdev/alpine-nginx-django).

Chaperone is a lightweight process manager specifically designed as an ENTRYPOINT for Docker containers that runs as PID 1.
As a single controlling process, it provides:
Expand All @@ -47,8 +47,8 @@ for production. *Please* [submit issues](https://github.com/garywiz/chaperone-d

## Try it out

All of these images work the same way. To get a quick idea of how things work, try the LAMP image and create your own
userspace development directory. It's best if you do this *as a normal user* that is a member of the docker group, since
All of these images work the same way. To get a quick idea of how things work, try the LAMP image and create your own
userspace development directory. It's best if you do this *as a normal user* that is a member of the docker group, since
that will give you a good idea of how the userspace development model works.

First, get the `chaplocal` script, a quick script which allows you to create userspace development "home directories":
Expand All @@ -73,7 +73,7 @@ Images also support a `get-help` feature so you can find out about the version y
you can simply say:

docker run -i --rm chapdev/chaperone-alpinejava --task get-help

We still have more work to do on these images, and feedback would be great. This approach
has solved a lot of problems for us.

Expand Down