mirror of
https://github.com/EpicMorg/docker-scripts.git
synced 2024-10-16 23:36:58 +03:00
readme md updates
This commit is contained in:
parent
ba3191b74c
commit
86c13bf136
23
README.md
23
README.md
@ -1,8 +1,27 @@
|
||||
# docker-scripts
|
||||
|
||||
## Custom Nginx
|
||||
[](https://github.com/EpicMorg/docker-scripts/issues) [](https://github.com/EpicMorg/docker-scripts/network) [](https://github.com/EpicMorg/docker-scripts/stargazers) [](https://github.com/EpicMorg/docker-scripts/blob/master/LICENSE)
|
||||
|
||||
## Products
|
||||
|
||||
### Atlassian  
|
||||
* https://hub.docker.com/r/epicmorg/balancer/
|
||||
* https://github.com/EpicMorg/docker-scripts/tree/master/bitbucket
|
||||
|
||||
|
||||
## Custom Apache2 + php7
|
||||
### Atlassian  
|
||||
* https://hub.docker.com/r/epicmorg/balancer/
|
||||
* https://github.com/EpicMorg/docker-scripts/tree/master/confluence
|
||||
|
||||
### Atlassian  
|
||||
* https://hub.docker.com/r/epicmorg/balancer/
|
||||
* https://github.com/EpicMorg/docker-scripts/tree/master/jira
|
||||
|
||||
### Nginx  
|
||||
* https://hub.docker.com/r/epicmorg/balancer/
|
||||
* https://github.com/EpicMorg/docker-scripts/tree/master/balancer
|
||||
|
||||
### Apache2 + php7   
|
||||
* https://hub.docker.com/r/epicmorg/websites/
|
||||
* https://github.com/EpicMorg/docker-scripts/tree/master/websites
|
||||
|
||||
@ -1,5 +1,7 @@
|
||||
# nginx web/proxy server (extended version)
|
||||
|
||||
* **SOURCE:** https://launchpad.net/~ondrej/+archive/ubuntu/nginx-mainline?field.series_filter=bionic
|
||||
|
||||
Nginx ("engine X") is a high-performance web and reverse proxy server created by Igor Sysoev. It can be used both as a standalone web server and as a proxy to reduce the load on back-end HTTP or mail servers.
|
||||
|
||||
This package provides a version of nginx with the standard modules, plus extra features and modules such as the Perl module, which allows the addition of Perl in configuration files.
|
||||
|
||||
@ -1,93 +1,23 @@
|
||||
|
||||
|
||||
Bitbucket Server is an on-premises source code management solution for Git that's secure, fast, and enterprise grade. Create and manage repositories, set up fine-grained permissions, and collaborate on code - all with the flexibility of your servers.
|
||||
|
||||
Learn more about Bitbucket Server: <https://www.atlassian.com/software/bitbucket/server>
|
||||
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of Bitbucket up and running.
|
||||
|
||||
** We strongly recommend you run this image using a specific version tag instead of latest. This is because the image referenced by the latest tag changes often and we cannot guarantee that it will be backwards compatible. **
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the `BITBUCKET_HOME` directory that is used to store the repository data
|
||||
(amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#/data-volumes), or via a named volume if using a docker version >= 1.9.
|
||||
|
||||
## For Bitbucket 4.12+
|
||||
|
||||
In Bitbucket 4.12 and later versions, volume permission is managed by entry scripts. To get started you can use a data volume, or named volumes. In this example we'll use named volumes.
|
||||
|
||||
$> docker volume create --name bitbucketVolume
|
||||
$> docker run -v bitbucketVolume:/var/atlassian/application-data/bitbucket --name="bitbucket" -d -p 7990:7990 -p 7999:7999 atlassian/bitbucket-server
|
||||
|
||||
## For other versions
|
||||
|
||||
Set permissions for the data directory so that the runuser can write to it:
|
||||
|
||||
$> docker run -u root -v /data/bitbucket:/var/atlassian/application-data/bitbucket atlassian/bitbucket-server chown -R daemon /var/atlassian/application-data/bitbucket
|
||||
|
||||
Note that this command can be replaced by named volumes.
|
||||
|
||||
Start Atlassian Bitbucket Server:
|
||||
|
||||
$> docker run -v /data/bitbucket:/var/atlassian/application-data/bitbucket --name="bitbucket" -d -p 7990:7990 -p 7999:7999 atlassian/bitbucket-server
|
||||
|
||||
**Success**. Bitbucket is now available on [http://localhost:7990](http://localhost:7990)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it.
|
||||
We recommend 2GiB of memory allocated to accommodate both the application server
|
||||
and the git processes.
|
||||
See [Supported Platforms](https://confluence.atlassian.com/display/BitbucketServer/Supported+platforms) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):7990` instead._
|
||||
|
||||
This Docker unofficial container makes it easy to get an instance of Bitbucket up and running.
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If Bitbucket is run behind a reverse proxy server as [described here](https://confluence.atlassian.com/bitbucketserver/proxying-and-securing-bitbucket-server-776640099.html),
|
||||
then you need to specify extra options to make bitbucket aware of the setup. They can be controlled via the below
|
||||
environment variables.
|
||||
|
||||
### Bitbucket Server 5.0 +
|
||||
|
||||
Due to the migration to Spring Boot in 5.0, there are changes to how you set up Bitbucket to run behind a reverse proxy.
|
||||
|
||||
In this example, we'll use an environment file. You can also do this via [specifying each environment variable](https://docs.docker.com/engine/reference/run/#env-environment-variables) via the `-e` argument in `docker run`.
|
||||
|
||||
#### secure-bitbucket.env
|
||||
|
||||
#### Bitbucket Server >= 5.0 secure-bitbucket.env
|
||||
```
|
||||
SERVER_SECURE=true
|
||||
SERVER_SCHEME=https
|
||||
SERVER_PROXY_PORT=443
|
||||
SERVER_PROXY_NAME=<Your url here>
|
||||
```
|
||||
|
||||
Then you run Bitbucket as usual
|
||||
|
||||
`docker run -v bitbucketVolume:/var/atlassian/application-data/bitbucket --name="bitbucket" -d -p 7990:7990 -p 7999:7999 --env-file=/path/to/env/file/secure-bitbucket.env atlassian/bitbucket-server:5.0`
|
||||
|
||||
### Bitbucket Server < 5.0
|
||||
|
||||
To set the reverse proxy arguments, you specify the following as environment variables in the `docker run` command
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
The reverse proxy's fully qualified hostname.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which bitbucket is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which bitbucket is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
Set 'true' if CATALINA\_CONNECTOR\_SCHEME is 'https'.
|
||||
|
||||
|
||||
## JVM Configuration (Bitbucket Server 5.0 + only)
|
||||
|
||||
If you need to override Bitbucket Server's default memory configuration or pass additional JVM arguments, use the environment variables below
|
||||
@ -178,45 +108,4 @@ Bitbucket Server supports detailed JMX monitoring. To enable and configure JMX,
|
||||
$> docker run -e JMX_ENABLED=true -e JMX_REMOTE_AUTH=password -e JMX_REMOTE_RMI_PORT=3333 -e RMI_SERVER_HOSTNAME=bitbucket \
|
||||
-e JMX_PASSWORD_FILE=/data/bitbucket:/var/atlassian/application-data/bitbucket/jmx.access \
|
||||
-v /data/bitbucket:/var/atlassian/application-data/bitbucket --name="bitbucket" -d -p 7990:7990 -p 7999:7999 -p 3333:3333 atlassian/bitbucket-server
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of Bitbucket Server you can simply stop the `bitbucket`
|
||||
container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop bitbucket
|
||||
$> docker rm bitbucket
|
||||
$> docker pull atlassian/bitbucket-server:<desired_version>
|
||||
$> docker run ... (See above)
|
||||
|
||||
As your data is stored in the data volume directory on the host it will still
|
||||
be available after the upgrade.
|
||||
|
||||
_Note: Please make sure that you **don't** accidentally remove the `bitbucket`
|
||||
container and its volumes using the `-v` option._
|
||||
|
||||
# Backup
|
||||
|
||||
For evaluations you can use the built-in database that will store its files in the Bitbucket Server home directory. In that case it is sufficient to create a backup archive of the directory on the host that is used as a volume (`/data/bitbucket` in the example above).
|
||||
|
||||
The [Bitbucket Server Backup Client](https://confluence.atlassian.com/display/BitbucketServer/Data+recovery+and+backups) is currently not supported in the Docker setup. You can however use the [Bitbucket Server DIY Backup](https://confluence.atlassian.com/display/BitbucketServer/Using+Bitbucket+Server+DIY+Backup) approach in case you decided to use an external database.
|
||||
|
||||
Read more about data recovery and backups: [https://confluence.atlassian.com/display/BitbucketServer/Data+recovery+and+backups](https://confluence.atlassian.com/display/BitbucketServer/Data+recovery+and+backups)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent version of this repository. Thus using `atlassian/bitbucket:latest` or `atlassian/bitbucket` will ensure you are running the most up to date version of this image.
|
||||
|
||||
However, we ** strongly recommend ** that for non-eval workloads you select a specific version in order to prevent breaking changes from impacting your setup.
|
||||
You can use a specific minor version of Bitbucket Server by using a version number
|
||||
tag: `atlassian/bitbucket-server:4.14`. This will install the latest `4.14.x` version that
|
||||
is available.
|
||||
|
||||
|
||||
# Issue tracker
|
||||
|
||||
Please raise an [issue](https://bitbucket.org/atlassian/docker-atlassian-bitbucket-server/issues) if you encounter any problems with this Dockerfile.
|
||||
|
||||
# Support
|
||||
|
||||
For product support, go to [support.atlassian.com](https://support.atlassian.com/)
|
||||
|
||||
@ -1,33 +1,8 @@
|
||||
|
||||
|
||||
Confluence Server is where you create, organise and discuss work with your team. Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence – where it's easy to find, use, and update. Give every team, project, or department its own space to create the things they need, whether it's meeting notes, product requirements, file lists, or project plans, you can get more done in Confluence.
|
||||
|
||||
Learn more about Confluence Server: <https://www.atlassian.com/software/confluence>
|
||||
|
||||
You can find the repository for this Dockerfile at <https://hub.docker.com/r/atlassian/confluence-server>
|
||||
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker container makes it easy to get an instance of Confluence up and running.
|
||||
|
||||
# Quick Start
|
||||
|
||||
For the directory in the environmental variable `CONFLUENCE_HOME` that is used to store Confluence data
|
||||
(amongst other things) we recommend mounting a host directory as a [data volume](https://docs.docker.com/userguide/dockervolumes/#mount-a-host-directory-as-a-data-volume):
|
||||
|
||||
Start Atlassian Confluence Server:
|
||||
|
||||
$> docker run -v /data/your-confluence-home:/var/atlassian/application-data/confluence --name="confluence" -d -p 8090:8090 -p 8091:8091 atlassian/confluence-server
|
||||
|
||||
|
||||
**Success**. Confluence is now available on [http://localhost:8090](http://localhost:8090)*
|
||||
|
||||
Please ensure your container has the necessary resources allocated to it.
|
||||
We recommend 2GiB of memory allocated to accommodate the application server.
|
||||
See [Supported Platforms](https://confluence.atlassian.com/display/DOC/Supported+platforms) for further information.
|
||||
|
||||
|
||||
_* Note: If you are using `docker-machine` on Mac OS X, please use `open http://$(docker-machine ip default):8090` instead._
|
||||
This Docker unofficial container makes it easy to get an instance of Confluence up and running.
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
@ -68,60 +43,4 @@ If you need to pass additional JVM arguments to Confluence such as specifying a
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for Confluence
|
||||
|
||||
Example:
|
||||
|
||||
$> docker run -e JVM_SUPPORT_RECOMMENDED_ARGS=-Djavax.net.ssl.trustStore=/var/atlassian/application-data/confluence/cacerts -v confluenceVolume:/var/atlassian/application-data/confluence --name="confluence" -d -p 8090:8090 -p 8091:8091 atlassian/confluence-server
|
||||
|
||||
|
||||
# Upgrade
|
||||
|
||||
To upgrade to a more recent version of Confluence Server you can simply stop the `Confluence`
|
||||
container and start a new one based on a more recent image:
|
||||
|
||||
$> docker stop confluence
|
||||
$> docker rm confluence
|
||||
$> docker run ... (see above)
|
||||
|
||||
As your data is stored in the data volume directory on the host, it will still
|
||||
be available after the upgrade.
|
||||
|
||||
_Note: Please make sure that you **don't** accidentally remove the `confluence`
|
||||
container and its volumes using the `-v` option._
|
||||
|
||||
# Backup
|
||||
|
||||
For evaluating Confluence you can use the built-in database that will store its files in the Confluence Server home directory. In that case it is sufficient to create a backup archive of the directory on the host that is used as a volume (`/data/your-confluence-home` in the example above).
|
||||
|
||||
Confluence's [automatic backup](https://confluence.atlassian.com/display/DOC/Configuring+Backups) is currently supported in the Docker setup. You can also use the [Production Backup Strategy](https://confluence.atlassian.com/display/DOC/Production+Backup+Strategy) approach if you're using an external database.
|
||||
|
||||
Read more about data recovery and backups: [Site Backup and Restore](https://confluence.atlassian.com/display/DOC/Site+Backup+and+Restore)
|
||||
|
||||
# Versioning
|
||||
|
||||
The `latest` tag matches the most recent release of Atlassian Confluence Server.
|
||||
So `atlassian/confluence-server:latest` will use the newest stable version of Confluence Server available.
|
||||
|
||||
Alternatively, you can use a specific minor version of Confluence Server by using a version number
|
||||
tag: `atlassian/confluence-server:5.10`. This will install the latest `5.10.x` version that
|
||||
is available.
|
||||
|
||||
For the latest developer (EAP) release use `atlassian/confluence-server:eap`. This will install our latest milestone (not supported for use in production).
|
||||
|
||||
# Known Problems
|
||||
In Mac OS X with Docker version 1.11.0, when running with docker-machine, there is a bug where the directory specified for `CONFLUENCE_HOME` in a volume mount will not have the correct permission, and thus startup fails with a permission denied error:
|
||||
Error writing state to confluence.cfg.xml
|
||||
com.atlassian.config.ConfigurationException: Couldn't save confluence.cfg.xml to /var/atlassian/confluence-home directory.
|
||||
|
||||
See https://github.com/docker/docker/issues/4023 for details.
|
||||
|
||||
To work around this issue, use a different host operating system other than Mac OSX until a newer release of Docker fixes this issue.
|
||||
|
||||
# Support
|
||||
|
||||
This Docker image is great for evaluating Confluence. However, it does not use an Oracle JDK due to licensing constraints. Instead, it uses OpenJDK which is not supported for running Confluence in production.
|
||||
|
||||
To meet our supported platform requirements, you'll need to build your own image based on [Oracle JDK](https://github.com/oracle/docker-images/tree/master/OracleJDK). See [Update the Confluence Docker image to use Oracle JDK ](https://confluence.atlassian.com/display/CONFKB/Update+the+Confluence+Docker+image+to+use+Oracle+JDK) for more info.
|
||||
|
||||
For product support go to [support.atlassian.com](http://support.atlassian.com).
|
||||
|
||||
|
||||
@ -1,9 +1,12 @@
|
||||
|
||||
|
||||
# Overview
|
||||
|
||||
This Docker unofficial container makes it easy to get an instance of Jira up and running.
|
||||
|
||||
## Memory / Heap Size
|
||||
|
||||
If you need to override Confluence Server's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
If you need to override Jira Server's default memory allocation, you can control the minimum heap (Xms) and maximum heap (Xmx) via the below environment variables.
|
||||
|
||||
* `JVM_MINIMUM_MEMORY` (default: 1024m)
|
||||
|
||||
@ -15,7 +18,7 @@ If you need to override Confluence Server's default memory allocation, you can c
|
||||
|
||||
## Reverse Proxy Settings
|
||||
|
||||
If Confluence is run behind a reverse proxy server, then you need to specify extra options to make Confluence aware of the setup. They can be controlled via the below environment variables.
|
||||
If Jira is run behind a reverse proxy server, then you need to specify extra options to make Jira aware of the setup. They can be controlled via the below environment variables.
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYNAME` (default: NONE)
|
||||
|
||||
@ -23,11 +26,11 @@ If Confluence is run behind a reverse proxy server, then you need to specify ext
|
||||
|
||||
* `CATALINA_CONNECTOR_PROXYPORT` (default: NONE)
|
||||
|
||||
The reverse proxy's port number via which Confluence is accessed.
|
||||
The reverse proxy's port number via which Jira is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SCHEME` (default: http)
|
||||
|
||||
The protocol via which Confluence is accessed.
|
||||
The protocol via which Jira is accessed.
|
||||
|
||||
* `CATALINA_CONNECTOR_SECURE` (default: false)
|
||||
|
||||
@ -35,10 +38,10 @@ If Confluence is run behind a reverse proxy server, then you need to specify ext
|
||||
|
||||
## JVM configuration
|
||||
|
||||
If you need to pass additional JVM arguments to Confluence such as specifying a custom trust store, you can add them via the below environment variable
|
||||
If you need to pass additional JVM arguments to Jira such as specifying a custom trust store, you can add them via the below environment variable
|
||||
|
||||
* `JVM_SUPPORT_RECOMMENDED_ARGS`
|
||||
|
||||
Additional JVM arguments for Confluence
|
||||
Additional JVM arguments for Jira
|
||||
|
||||
|
||||
@ -1 +1,38 @@
|
||||
just custom apache2 + php7
|
||||
# Apache2
|
||||
|
||||
* **SOURCE:** https://launchpad.net/~ondrej/+archive/ubuntu/apache2?field.series_filter=bionic
|
||||
|
||||
This branch follows latest Apache2 packages as maintained by the Debian Apache2 team with couple of compatibility patches on top.
|
||||
|
||||
It also includes some widely used Apache 2 modules (if you need some other feel free to send me a request).
|
||||
|
||||
BUGS&FEATURES: This PPA now has a issue tracker: https://deb.sury.org/#bug-reporting
|
||||
|
||||
PLEASE READ: If you like my work and want to give me a little motivation, please consider donating: https://deb.sury.org/#donate
|
||||
|
||||
|
||||
# PHP7
|
||||
|
||||
* **SOURCE:** https://launchpad.net/~ondrej/+archive/ubuntu/php?field.series_filter=bionic
|
||||
|
||||
Co-installable PHP versions: PHP 5.6, PHP 7.x and most requested extensions are included. Only Supported Versions of PHP (http://php.net/supported-versions.php) for Supported Ubuntu Releases (https://wiki.ubuntu.com/Releases) are provided. Don't ask for end-of-life PHP versions or Ubuntu release, they won't be provided.
|
||||
|
||||
Debian oldstable and stable packages are provided as well: https://deb.sury.org/#debian-dpa
|
||||
|
||||
You can get more information about the packages at https://deb.sury.org
|
||||
|
||||
BUGS&FEATURES: This PPA now has a issue tracker:
|
||||
https://deb.sury.org/#bug-reporting
|
||||
|
||||
CAVEATS:
|
||||
1. If you are using php-gearman, you need to add ppa:ondrej/pkg-gearman
|
||||
2. If you are using apache2, you are advised to add ppa:ondrej/apache2
|
||||
3. If you are using nginx, you are advise to add ppa:ondrej/nginx-mainline
|
||||
or ppa:ondrej/nginx
|
||||
|
||||
PLEASE READ: If you like my work and want to give me a little motivation, please consider donating regularly: https://donate.sury.org/
|
||||
|
||||
WARNING: add-apt-repository is broken with non-UTF-8 locales, see
|
||||
https://github.com/oerdnj/deb.sury.org/issues/56 for workaround:
|
||||
|
||||
# LC_ALL=C.UTF-8 add-apt-repository ppa:ondrej/php
|
||||
Loading…
Reference in New Issue
Block a user