mirror of
https://github.com/bitnami/containers.git
synced 2026-03-05 16:17:21 +08:00
260 lines
8.8 KiB
Markdown
260 lines
8.8 KiB
Markdown
[](https://hub.docker.com/r/bitnami/ghost/)
|
|
# What is Ghost?
|
|
|
|
> Ghost is a simple, powerful publishing platform that allows you to share your stories with the world
|
|
|
|
https://ghost.org/
|
|
|
|
# Prerequisites
|
|
|
|
To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.
|
|
|
|
# How to use this image
|
|
|
|
### Run the application using Docker Compose
|
|
|
|
This is the recommended way to run Ghost. You can use the following docker compose template:
|
|
|
|
```
|
|
version: '2'
|
|
|
|
services:
|
|
mariadb:
|
|
image: 'bitnami/mariadb:latest'
|
|
volumes:
|
|
- 'mariadb_data:/bitnami/mariadb'
|
|
application:
|
|
image: 'bitnami/ghost:latest'
|
|
ports:
|
|
- '80:2368'
|
|
volumes:
|
|
- 'ghost_data:/bitnami/ghost'
|
|
depends_on:
|
|
- mariadb
|
|
volumes:
|
|
mariadb_data:
|
|
driver: local
|
|
ghost_data:
|
|
driver: local
|
|
```
|
|
|
|
### Run the application manually
|
|
|
|
If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:
|
|
|
|
1. Create a new network for the application and the database:
|
|
|
|
```
|
|
$ docker network create ghost_network
|
|
```
|
|
|
|
2. Start a MariaDB database in the network generated:
|
|
|
|
```
|
|
$ docker run -d --name mariadb --net=ghost_network bitnami/mariadb
|
|
```
|
|
|
|
*Note:* You need to give the container a name in order to Ghost to resolve the host
|
|
|
|
3. Run the Ghost container:
|
|
|
|
```
|
|
$ docker run -d -p 80:2368 --name ghost --net=ghost_network bitnami/ghost
|
|
```
|
|
|
|
Then you can access your application at http://your-ip/
|
|
|
|
> **Note!** If you want to access your application from a public IP or hostname you need to properly configured Ghost . You can handle it adjusting the configuration of the instance by setting the environment variable "GHOST_HOST" to your public IP or hostname.
|
|
|
|
## Persisting your application
|
|
If you remove every container and volume all your data will be lost, and the next time you run the image the application will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed. If you are using docker-compose your data will be persistent as long as you don't remove `application_data` data volume. If you have run the containers manually or you want to mount the folders with persistent data in your host follow the next steps:
|
|
|
|
> **Note!** If you have already started using your application, follow the steps on [backing](#backing-up-your-application) up to pull the data from your running container down to your host.
|
|
|
|
### Mount persistent folders in the host using docker-compose
|
|
|
|
This requires a sightly modification from the template previously shown:
|
|
```
|
|
version: '2'
|
|
|
|
services:
|
|
mariadb:
|
|
image: 'bitnami/mariadb:latest'
|
|
volumes:
|
|
- '/path/to/your/local/mariadb_data:/bitnami/mariadb'
|
|
application:
|
|
image: bitnami/ghost:latest
|
|
ports:
|
|
- '80:2368'
|
|
volumes:
|
|
- '/path/to/your/local/ghost_data:/bitnami/ghost'
|
|
depends_on:
|
|
- mariadb
|
|
```
|
|
|
|
### Mount persistent folders manually
|
|
|
|
In this case you need to specify the directories to mount on the run command. The process is the same than the one previously shown:
|
|
|
|
1. If you haven't done this before, create a new network for the application and the database:
|
|
|
|
```
|
|
$ docker network create ghost_network
|
|
```
|
|
|
|
2. Start a MariaDB database in the previous network:
|
|
|
|
```
|
|
$ docker run -d --name mariadb -v /your/local/path/bitnami/mariadb/data:/bitnami/mariadb/data -v /your/local/path/bitnami/mariadb/conf:/bitnami/mariadb/conf --network=ghost_network bitnami/mariadb
|
|
```
|
|
|
|
*Note:* You need to give the container a name in order to Ghost to resolve the host
|
|
|
|
3. Run the Ghost container:
|
|
|
|
```
|
|
$ docker run -d -p 80:2368 --name ghost -v /your/local/path/bitnami/ghost:/bitnami/ghost --network=ghost_network bitnami/ghost
|
|
```
|
|
|
|
# Upgrade this application
|
|
|
|
Bitnami provides up-to-date versions of MariaDB and Ghost, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Ghost container. For the MariaDB upgrade see https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image
|
|
|
|
1. Get the updated images:
|
|
|
|
```
|
|
$ docker pull bitnami/ghost:latest
|
|
```
|
|
|
|
2. Stop your container
|
|
|
|
* For docker-compose: `$ docker-compose stop ghost`
|
|
* For manual execution: `$ docker stop ghost`
|
|
|
|
3. (For non-compose execution only) Create a [backup](#backing-up-your-application) if you have not mounted the ghost folder in the host.
|
|
|
|
4. Remove the currently running container
|
|
|
|
* For docker-compose: `$ docker-compose rm ghost`
|
|
* For manual execution: `$ docker rm ghost`
|
|
|
|
5. Run the new image
|
|
|
|
* For docker-compose: `$ docker-compose start ghost`
|
|
* For manual execution ([mount](#mount-persistent-folders-manually) the directories if needed): `docker run --name ghost bitnami/ghost:latest`
|
|
|
|
# Configuration
|
|
## Environment variables
|
|
When you start the ghost image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:
|
|
|
|
* For docker-compose add the variable name and value under the application section:
|
|
```
|
|
application:
|
|
image: bitnami/ghost:latest
|
|
ports:
|
|
- 80:2368
|
|
environment:
|
|
- GHOST_HOST=my_host
|
|
```
|
|
|
|
* For manual execution add a `-e` option with each variable and value:
|
|
|
|
```
|
|
$ docker run -d -e GHOST_PASSWORD=my_password -p 80:2368 --name ghost -v /your/local/path/bitnami/ghost:/bitnami/ghost --network=ghost_network bitnami/ghost
|
|
```
|
|
|
|
Available variables:
|
|
- `GHOST_HOST`: Hostname for Ghost.
|
|
- `GHOST_PORT`: Ghost application port. Default: **80**
|
|
- `GHOST_USERNAME`: Ghost application username. Default: **user**
|
|
- `GHOST_PASSWORD`: Ghost application password. Default: **bitnami1**
|
|
- `GHOST_EMAIL`: Ghost application email. Default: **user@example.com**
|
|
- `BLOG_TITLE`: Ghost blog title. Default: **User's Blog**
|
|
- `MARIADB_USER`: Root password for the MariaDB.
|
|
- `MARIADB_HOST`: Hostname for MariaDB server. Default: **mariadb**
|
|
- `MARIADB_PORT`: Port used by MariaDB server. Default: **3306**
|
|
### SMTP Configuration
|
|
|
|
To configure Ghost to send email using SMTP you can set the following environment variables:
|
|
- `SMTP_HOST`: SMTP host.
|
|
- `SMTP_PORT`: SMTP port.
|
|
- `SMTP_USER`: SMTP account user.
|
|
- `SMTP_PASSWORD`: SMTP account password.
|
|
- `SMTP_SERVICE`: SMTP service to use.
|
|
|
|
This would be an example of SMTP configuration using a GMail account:
|
|
|
|
* docker-compose:
|
|
|
|
```
|
|
application:
|
|
image: bitnami/ghost:latest
|
|
ports:
|
|
- 80:2368
|
|
environment:
|
|
- SMTP_HOST=smtp.gmail.com
|
|
- SMTP_USER=your_email@gmail.com
|
|
- SMTP_PASSWORD=your_password
|
|
- SMTP_SERVICE=GMail
|
|
```
|
|
|
|
* For manual execution:
|
|
|
|
```
|
|
$ docker run -d -e SMTP_HOST=smtp.gmail.com -e SMTP_SERVICE=GMail -e SMTP_USER=your_email@gmail.com -e SMTP_PASSWORD=your_password -p 80:2368 --name ghost -v /your/local/path/bitnami/ghost:/bitnami/ghost --network=ghost_network bitnami/ghost
|
|
```
|
|
|
|
# Backing up your application
|
|
|
|
To backup your application data follow these steps:
|
|
|
|
1. Stop the running container:
|
|
|
|
* For docker-compose: `$ docker-compose stop ghost`
|
|
* For manual execution: `$ docker stop ghost`
|
|
|
|
2. Copy the Ghost data folder in the host:
|
|
|
|
```
|
|
$ docker cp /your/local/path/bitnami:/bitnami/ghost
|
|
```
|
|
|
|
# Restoring a backup
|
|
|
|
To restore your application using backed up data simply mount the folder with Ghost data in the container. See [persisting your application](#persisting-your-application) section for more info.
|
|
|
|
# Contributing
|
|
|
|
We'd love for you to contribute to this container. You can request new features by creating an
|
|
[issue](https://github.com/bitnami/ghost/issues), or submit a
|
|
[pull request](https://github.com/bitnami/ghost/pulls) with your contribution.
|
|
|
|
# Issues
|
|
|
|
If you encountered a problem running this container, you can file an
|
|
[issue](https://github.com/bitnami/ghost/issues). For us to provide better support,
|
|
be sure to include the following information in your issue:
|
|
|
|
- Host OS and version
|
|
- Docker version (`docker version`)
|
|
- Output of `docker info`
|
|
- Version of this container (`echo $BITNAMI_APP_VERSION` inside the container)
|
|
- The command you used to run the container, and any relevant output you saw (masking any sensitive
|
|
information)
|
|
|
|
# License
|
|
|
|
Copyright 2016 Bitnami
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|