Run update.sh
This commit is contained in:
Docker Library Bot
parent
9902f062d4
commit
f9d80a5f22
|
|
@ -0,0 +1,129 @@
|
|||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`5.0.6`, `5.0`, `5`, `latest` (*5.0/5.0.6/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/5.0/5.0.6/debian/Dockerfile)
|
||||
- [`5.0.5` (*5.0/5.0.5/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/5.0/5.0.5/debian/Dockerfile)
|
||||
- [`5.0.4` (*5.0/5.0.4/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/5.0/5.0.4/debian/Dockerfile)
|
||||
- [`5.0.3` (*5.0/5.0.3/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/5.0/5.0.3/debian/Dockerfile)
|
||||
- [`5.0.2` (*5.0/5.0.2/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/5.0/5.0.2/debian/Dockerfile)
|
||||
- [`4.3.11`, `4.3`, `4` (*4.3/4.3.11/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/4.3/4.3.11/debian/Dockerfile)
|
||||
- [`4.3.10` (*4.3/4.3.10/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/4.3/4.3.10/debian/Dockerfile)
|
||||
- [`4.3.9` (*4.3/4.3.9/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/4.3/4.3.9/debian/Dockerfile)
|
||||
- [`4.3.8` (*4.3/4.3.8/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/4.3/4.3.8/debian/Dockerfile)
|
||||
- [`4.3.7` (*4.3/4.3.7/debian/Dockerfile*)](https://github.com/plone/plone.docker/blob/443c34c35e774820621bf5c0966c81c3b45cb284/4.3/4.3.7/debian/Dockerfile)
|
||||
|
||||
For more information about this image and its history, please see [the relevant manifest file (`library/plone`)](https://github.com/docker-library/official-images/blob/master/library/plone). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Fplone).
|
||||
|
||||
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see [the `repos/plone/tag-details.md` file](https://github.com/docker-library/repo-info/blob/master/repos/plone/tag-details.md) in [the `docker-library/repo-info` GitHub repo](https://github.com/docker-library/repo-info).
|
||||
|
||||
# What is Plone?
|
||||
|
||||
[Plone](https://plone.org) is a free and open source content management system built on top of the Zope application server.
|
||||
|
||||
|
||||
|
||||
## Features
|
||||
|
||||
- Images for Plone 5 and Plone 4
|
||||
- Enable add-ons via environment variables
|
||||
|
||||
## Usage
|
||||
|
||||
### Start a single Plone instance
|
||||
|
||||
This will download and start the latest Plone 5 container, based on [Debian](https://www.debian.org/).
|
||||
|
||||
```console
|
||||
$ docker run -p 8080:8080 plone
|
||||
```
|
||||
|
||||
This image includes `EXPOSE 8080` (the Plone port), so standard container linking will make it automatically available to the linked containers. Now you can add a Plone Site at http://localhost:8080 - default Zope user and password are `admin/admin`.
|
||||
|
||||
### Start Plone within a ZEO cluster
|
||||
|
||||
Start ZEO server
|
||||
|
||||
```console
|
||||
$ docker run --name=zeo plone zeoserver
|
||||
```
|
||||
|
||||
Start 2 Plone clients
|
||||
|
||||
```console
|
||||
$ docker run --link=zeo -e ZEO_ADDRESS=zeo:8100 -p 8081:8080 plone
|
||||
$ docker run --link=zeo -e ZEO_ADDRESS=zeo:8100 -p 8082:8080 plone
|
||||
```
|
||||
|
||||
### Start Plone in debug mode
|
||||
|
||||
You can also start Plone in debug mode (`fg`) by running
|
||||
|
||||
```console
|
||||
$ docker run -p 8080:8080 plone fg
|
||||
```
|
||||
|
||||
### Add-ons
|
||||
|
||||
You can enable Plone add-ons via the `PLONE_ADDONS` environment variable
|
||||
|
||||
```console
|
||||
$ docker run -p 8080:8080 -e PLONE_ADDONS="eea.facetednavigation Products.PloneFormGen" plone
|
||||
```
|
||||
|
||||
For more information on how to extend this image with your own custom settings, adding more add-ons, building it or mounting volumes, please refer to our [documentation](https://github.com/plone/plone.docker/blob/master/docs/usage.rst).
|
||||
|
||||
### Supported Environment Variables
|
||||
|
||||
The Plone image uses several environment variable that allow to specify a more specific setup.
|
||||
|
||||
- `PLONE_ADDONS`, `ADDONS` - Customize Plone via Plone add-ons using this environment variable
|
||||
- `PLONE_ZCML`, `ZCML` - Include custom Plone add-ons ZCML files
|
||||
- `PLONE_DEVELOP`, `DEVELOP` - Develop new or existing Plone add-ons
|
||||
- `ZEO_ADDRESS` - This environment variable allows you to run Plone image as a ZEO client.
|
||||
- `ZEO_READ_ONLY` - Run Plone as a read-only ZEO client. Defaults to `off`.
|
||||
- `ZEO_CLIENT_READ_ONLY_FALLBACK` - A flag indicating whether a read-only remote storage should be acceptable as a fallback when no writable storages are available. Defaults to `false`.
|
||||
- `ZEO_SHARED_BLOB_DIR` - Set this to on if the ZEO server and the instance have access to the same directory. Defaults to `off`.
|
||||
- `ZEO_STORAGE` - Set the storage number of the ZEO storage. Defaults to `1`.
|
||||
- `ZEO_CLIENT_CACHE_SIZE` - Set the size of the ZEO client cache. Defaults to `128MB`.
|
||||
- `ZEO_PACK_KEEP_OLD` - Can be set to false to disable the creation of `*.fs.old` files before the pack is run. Defaults to true.
|
||||
- `HEALTH_CHECK_TIMEOUT` - Time in seconds to wait until health check starts. Defaults to `1` second.
|
||||
- `HEALTH_CHECK_INTERVAL` - Interval in seconds to check that the Zope application is still healthy. Defaults to `1` second.
|
||||
|
||||
## Documentation
|
||||
|
||||
Full documentation for end users can be found in the ["docs"](https://github.com/plone/plone.docker/tree/master/docs) folder. It is also available online at http://docs.plone.org/
|
||||
|
||||
## Credits
|
||||
|
||||
This docker image was originally financed by the [European Environment Agency](http://eea.europa.eu), an agency of the European Union.
|
||||
|
||||
Thanks to [Antonio De Marinis](https://github.com/demarant), [Sven Strack](https://github.com/svx) and [Alin Voinea](https://github.com/avoinea) for their preliminary work.
|
||||
|
||||
# License
|
||||
|
||||
View [license information](https://plone.org/foundation/copyrights/license-faq) for the software contained in this image.
|
||||
|
||||
# Supported Docker versions
|
||||
|
||||
This image is officially supported on Docker version 1.12.2.
|
||||
|
||||
Support for older versions (down to 1.6) is provided on a best-effort basis.
|
||||
|
||||
Please see [the Docker installation documentation](https://docs.docker.com/installation/) for details on how to upgrade your Docker daemon.
|
||||
|
||||
# User Feedback
|
||||
|
||||
## Documentation
|
||||
|
||||
Documentation for this image is stored in the [`plone/` directory](https://github.com/docker-library/docs/tree/master/plone) of the [`docker-library/docs` GitHub repo](https://github.com/docker-library/docs). Be sure to familiarize yourself with the [repository's `README.md` file](https://github.com/docker-library/docs/blob/master/README.md) before attempting a pull request.
|
||||
|
||||
## Issues
|
||||
|
||||
If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/plone/plone.docker/issues). If the issue is related to a CVE, please check for [a `cve-tracker` issue on the `official-images` repository first](https://github.com/docker-library/official-images/issues?q=label%3Acve-tracker).
|
||||
|
||||
You can also reach many of the official image maintainers via the `#docker-library` IRC channel on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
|
||||
|
||||
Before you start to code, we recommend discussing your plans through a [GitHub issue](https://github.com/plone/plone.docker/issues), especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
|
||||
|
|
@ -0,0 +1,140 @@
|
|||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`0.9.7`, `0.9` (*0.9.7/Dockerfile*)](https://github.com/31z4/storm-docker/blob/93746fa3936afb3751565860632d3e49d53e9b0e/0.9.7/Dockerfile)
|
||||
- [`0.10.2`, `0.10` (*0.10.2/Dockerfile*)](https://github.com/31z4/storm-docker/blob/93746fa3936afb3751565860632d3e49d53e9b0e/0.10.2/Dockerfile)
|
||||
- [`1.0.2`, `1.0`, `latest` (*1.0.2/Dockerfile*)](https://github.com/31z4/storm-docker/blob/93746fa3936afb3751565860632d3e49d53e9b0e/1.0.2/Dockerfile)
|
||||
|
||||
For more information about this image and its history, please see [the relevant manifest file (`library/storm`)](https://github.com/docker-library/official-images/blob/master/library/storm). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Fstorm).
|
||||
|
||||
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see [the `repos/storm/tag-details.md` file](https://github.com/docker-library/repo-info/blob/master/repos/storm/tag-details.md) in [the `docker-library/repo-info` GitHub repo](https://github.com/docker-library/repo-info).
|
||||
|
||||
# What is Apache Storm?
|
||||
|
||||
Apache Storm is a distributed computation framework written predominantly in the Clojure programming language. Originally created by Nathan Marz and team at BackType, the project was open sourced after being acquired by Twitter. It uses custom created "spouts" and "bolts" to define information sources and manipulations to allow batch, distributed processing of streaming data. The initial release was on 17 September 2011.
|
||||
|
||||
> [wikipedia.org/wiki/Storm_(event_processor)](https://en.wikipedia.org/wiki/Storm_(event_processor))
|
||||
|
||||
|
||||
|
||||
# How to use this image
|
||||
|
||||
## Running topologies in local mode
|
||||
|
||||
Assuming you have `storm-starter-topologies-1.0.2.jar` in the current directory.
|
||||
|
||||
$ docker run -it -v $(pwd)/storm-starter-topologies-1.0.2.jar:/topology.jar storm:1.0.2 storm jar /topology.jar org.apache.storm.starter.ExclamationTopology
|
||||
|
||||
## Setting up a minimal Storm cluster
|
||||
|
||||
1. [Apache Zookeeper](https://zookeeper.apache.org/) is a must for running a Storm cluster. Start it first. Since the Zookeeper "fails fast" it's better to always restart it.
|
||||
|
||||
$ docker run -d --restart always --name some-zookeeper zookeeper:3.4
|
||||
|
||||
2. The Nimbus daemon has to be connected with the Zookeeper. It's also a "fail fast" system.
|
||||
|
||||
$ docker run -d --restart always --name some-nimbus --link some-zookeeper:zookeeper storm:1.0.2 storm nimbus
|
||||
|
||||
3. Finally start a single Supervisor node. It will talk to the Nimbus and Zookeeper.
|
||||
|
||||
$ docker run -d --restart always --name supervisor --link some-zookeeper:zookeeper --link some-nimbus:nimbus storm:1.0.2 storm supervisor
|
||||
|
||||
4. Now you can submit a topology to our cluster.
|
||||
|
||||
$ docker run --link some-nimbus:nimbus -it --rm -v $(pwd)/storm-starter-topologies-1.0.2.jar:/topology.jar storm:1.0.2 storm jar /topology.jar org.apache.storm.starter.WordCountTopology topology
|
||||
|
||||
5. Optionally, you can start the Storm UI.
|
||||
|
||||
$ docker run -d -p 8080:8080 --restart always --name ui --link some-nimbus:nimbus storm:1.0.2 storm ui
|
||||
|
||||
## ... via [`docker-compose`](https://github.com/docker/compose)
|
||||
|
||||
Example `docker-compose.yml` for `storm`:
|
||||
|
||||
```yaml
|
||||
version: '2'
|
||||
services:
|
||||
zookeeper:
|
||||
image: zookeeper:3.4
|
||||
container_name: zookeeper
|
||||
restart: always
|
||||
|
||||
nimbus:
|
||||
image: storm:1.0.2
|
||||
container_name: nimbus
|
||||
command: storm nimbus
|
||||
depends_on:
|
||||
- zookeeper
|
||||
links:
|
||||
- zookeeper
|
||||
restart: always
|
||||
ports:
|
||||
- 6627:6627
|
||||
|
||||
supervisor:
|
||||
image: storm:1.0.2
|
||||
container_name: supervisor
|
||||
command: storm supervisor
|
||||
depends_on:
|
||||
- nimbus
|
||||
- zookeeper
|
||||
links:
|
||||
- nimbus
|
||||
- zookeeper
|
||||
restart: always
|
||||
```
|
||||
|
||||
Run `docker-compose up` and wait for it to initialize completely. The Nimbus will be available at your host and port `6627`.
|
||||
|
||||
## Configuration
|
||||
|
||||
This image uses [default configuration](https://github.com/apache/storm/blob/v1.0.2/conf/defaults.yaml) of the Apache Storm. There are two main ways to change it.
|
||||
|
||||
1. Using command line arguments.
|
||||
|
||||
$ docker run -d --restart always --name nimbus storm:1.0.2 storm nimbus -c storm.zookeeper.servers="[zookeeper]"
|
||||
|
||||
2. Assuming you have `storm.yaml` in the current directory you can mount it as a volume.
|
||||
|
||||
$ docker run -it -v $(pwd)/storm.yaml:/conf/storm.yaml storm:1.0.2 storm nimbus
|
||||
|
||||
## Logging
|
||||
|
||||
This image uses [default logging configuration](https://github.com/apache/storm/tree/v1.0.2/log4j2). All logs go to the `/logs` directory by default.
|
||||
|
||||
## Data persistence
|
||||
|
||||
No data are persisted by default. For convenience there are `/data` and `/logs` directories in the image owned by `storm` user. Use them accordingly to persist data and logs using volumes.
|
||||
|
||||
$ docker run -it -v /logs -v /data storm:1.0.2 storm nimbus
|
||||
|
||||
*Please be noticed that using paths other than those predefined is likely to cause permission denied errors. It's because for [security reasons](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#user) the Storm is running under the non-root `storm` user.*
|
||||
|
||||
# License
|
||||
|
||||
View [license information](http://storm.apache.org/about/free-and-open-source.html) for the software contained in this image.
|
||||
|
||||
# Supported Docker versions
|
||||
|
||||
This image is officially supported on Docker version 1.12.2.
|
||||
|
||||
Support for older versions (down to 1.6) is provided on a best-effort basis.
|
||||
|
||||
Please see [the Docker installation documentation](https://docs.docker.com/installation/) for details on how to upgrade your Docker daemon.
|
||||
|
||||
# User Feedback
|
||||
|
||||
## Documentation
|
||||
|
||||
Documentation for this image is stored in the [`storm/` directory](https://github.com/docker-library/docs/tree/master/storm) of the [`docker-library/docs` GitHub repo](https://github.com/docker-library/docs). Be sure to familiarize yourself with the [repository's `README.md` file](https://github.com/docker-library/docs/blob/master/README.md) before attempting a pull request.
|
||||
|
||||
## Issues
|
||||
|
||||
If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/31z4/storm-docker/issues). If the issue is related to a CVE, please check for [a `cve-tracker` issue on the `official-images` repository first](https://github.com/docker-library/official-images/issues?q=label%3Acve-tracker).
|
||||
|
||||
You can also reach many of the official image maintainers via the `#docker-library` IRC channel on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
|
||||
|
||||
Before you start to code, we recommend discussing your plans through a [GitHub issue](https://github.com/31z4/storm-docker/issues), especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
|
||||
Loading…
Reference in New Issue