forked from plume/documentation
e1b51db4df
Update everything (I may have forgotten a few details however) Split installation documentation in many parts, and make it so that you only read what you need to read. Left menu to quickly go to another page. Remove the i18n docs as it was outdated and it duplicated contribute.joinplu.me
1.5 KiB
1.5 KiB
| title |
|---|
| Installing with Docker |
You can use docker and docker-compose in order to manage your Plume instance
and have it isolated from your host.
If you don't have docker and docker-compose installed yet, here are their respective
installation documentation: docker and
docker-compose.
Then use these commands:
mkdir plume
cd plume
# Get the docker-compose configuration and Plume's configuration
curl https://docs.joinplu.me/docker-compose.sample.yml > docker-compose.yml
curl https://docs.joinplu.me/docker.sample.env > .env
You should edit the freshly created .env file as it contains the configuration
of your Plume instance. The two first options especially should be modified.
Once it's done, you can finalize the installation.
# Download the images
docker-compose pull
# Launch the database
docker-compose up -d postgres
# Setup the database (create it and run migrations)
docker-compose run --rm plume diesel database setup
# Setup your instance
docker-compose run --rm plume plm instance new
docker-compose run --rm plume plm users new --admin
docker-compose run --rm plume plm search init
# Launch your instance for good
docker-compose up -d
And that's it! You can now setup a reverse-proxy to access Plume from other machines than your server (which is probably what you want 😁).