Apply the footer update from fred
This commit is contained in:
Joe Ferguson
parent
faca93f1e3
commit
6b0f30f067
|
|
@ -11,10 +11,17 @@
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/buildpack-deps/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/buildpack-deps/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/buildpack-deps/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/buildpack-deps/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.
|
||||
|
|
|
|||
|
|
@ -54,10 +54,17 @@ This will build your project into a jar file located in your project's target/ub
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/Quantisan/docker-clojure/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/Quantisan/docker-clojure/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/Quantisan/docker-clojure/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/Quantisan/docker-clojure/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.
|
||||
|
|
|
|||
|
|
@ -38,10 +38,17 @@ This will add your current directory as a volume to the container, set the worki
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/gcc/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/gcc/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/gcc/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/gcc/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.
|
||||
|
|
|
|||
|
|
@ -66,10 +66,17 @@ Alternatively, build for multiple platforms at once:
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/golang/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/golang/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/golang/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/golang/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.
|
||||
|
|
|
|||
|
|
@ -31,10 +31,17 @@
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/hello-world/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/hello-world/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/hello-world/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/hello-world/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.
|
||||
|
|
|
|||
|
|
@ -32,10 +32,17 @@ For many single file projects, it may not be convenient to write a `Dockerfile`
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/hylang/hy/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/hylang/hy/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/hylang/hy/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/hylang/hy/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.
|
||||
|
|
|
|||
|
|
@ -43,10 +43,17 @@ This will add your current directory as a volume to the container, set the worki
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/java/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/java/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/java/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/java/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.
|
||||
|
|
|
|||
|
|
@ -30,10 +30,17 @@ This image includes `EXPOSE 27017` (the mongo port), so standard container linki
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/mongo/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/mongo/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/mongo/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/mongo/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.
|
||||
|
|
|
|||
|
|
@ -33,10 +33,17 @@ This image includes `EXPOSE 3306` (the mysql port), so standard container linkin
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/mysql/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/mysql/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/mysql/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/mysql/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.
|
||||
|
|
|
|||
|
|
@ -54,10 +54,17 @@ Then, build with `docker build -t some-custom-nginx .` and run:
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/nginx/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/nginx/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/nginx/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/nginx/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.
|
||||
|
|
|
|||
|
|
@ -43,10 +43,17 @@ For many single file projects, it may not be convenient to write a `Dockerfile`
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/node/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/node/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/node/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/node/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.
|
||||
|
|
|
|||
|
|
@ -34,10 +34,17 @@ For many single file projects, it may not be convenient to write a `Dockerfile`
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/Perl/docker-perl/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/Perl/docker-perl/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/Perl/docker-perl/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/Perl/docker-perl/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.
|
||||
|
|
|
|||
|
|
@ -62,10 +62,17 @@ If you don't want to include a `Dockerfile` in your project, then it is sufficie
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/php/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/php/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/php/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/php/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.
|
||||
|
|
|
|||
|
|
@ -32,10 +32,17 @@ This image includes `EXPOSE 5432` (the postgres port), so standard container lin
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us on the [mailing list](http://www.postgresql.org/community/lists/subscribe/) or through a [GitHub issue](https://github.com/docker-library/postgres/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
on the [mailing list](http://www.postgresql.org/community/lists/subscribe/) or through a [GitHub issue](https://github.com/docker-library/postgres/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans on the [mailing list](http://www.postgresql.org/community/lists/subscribe/) or through a [GitHub issue](https://github.com/docker-library/postgres/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans on the [mailing list](http://www.postgresql.org/community/lists/subscribe/) or through a
|
||||
[GitHub issue](https://github.com/docker-library/postgres/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.
|
||||
|
|
|
|||
|
|
@ -44,10 +44,17 @@ or (again, if you need to use Python 2):
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/python/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/python/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/python/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/python/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.
|
||||
|
|
|
|||
|
|
@ -33,10 +33,17 @@ Then hit `http://localhost:8080` or `http://host-ip:8080` in a browser.
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/rails/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/rails/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/rails/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/rails/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.
|
||||
|
|
|
|||
|
|
@ -56,10 +56,17 @@ Using this method means that there is no need for you to have a Dockerfile for y
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/redis/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/redis/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/redis/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/redis/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.
|
||||
|
|
|
|||
|
|
@ -39,10 +39,17 @@ For many single file projects, it may not be convenient to write a `Dockerfile`
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/ruby/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/ruby/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/ruby/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/ruby/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.
|
||||
|
|
|
|||
|
|
@ -85,10 +85,17 @@ If you run into any problems with this image, please check (and potentially file
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/ubuntu/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/ubuntu/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/ubuntu/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/ubuntu/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.
|
||||
|
|
|
|||
|
|
@ -30,10 +30,17 @@ Then, access it via `http://localhost:8080` or `http://host-ip:8080` in a browse
|
|||
|
||||
## Issues
|
||||
|
||||
If you have any questions about the image, please contact us through a [GitHub issue](https://github.com/docker-library/wordpress/issues) or in the IRC channel `#docker-library` on [Freenode](https://freenode.net).
|
||||
If you have any problems with, or questions about this image, please contact us
|
||||
through a [GitHub issue](https://github.com/docker-library/wordpress/issues) or via the IRC channel
|
||||
`#docker-library` on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
If you want to contribute new features or updates, we are always thrilled to receive pull requests, and do our best to process them as fast as possible.
|
||||
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.
|
||||
|
||||
We recommend discussing your plans through a [GitHub issue](https://github.com/docker-library/wordpress/issues) before starting to code - especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give feedback on your design, and maybe point out if someone else is working on the same thing.
|
||||
Before you start to code, we recommend discussing your plans through a
|
||||
[GitHub issue](https://github.com/docker-library/wordpress/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