edshot99/eBooru
1
0
Fork 0
forked from e621ng/e621ng
Code Issues 11 Releases 1 Activity

[Docker] Use recommended compose syntax in readme

Browse Source 
The standalone version is deprecated
This commit is contained in:
Earlopain 2022-12-14 18:38:52 +01:00
parent 220ee8be16
commit af7a4d4bc9
No known key found for this signature in database
GPG Key ID: 6CFB948E15246897
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -24,27 +24,27 @@ To mitigate this you can install a WSL distribution and clone the project inside
1. Uncomment the `COMPOSE_PROFILES` variable if you wish to use solargraph. Doesn't work on Windows without WSL. 1. Uncomment the `COMPOSE_PROFILES` variable if you wish to use solargraph. Doesn't work on Windows without WSL.
1. Run the following commands: 1. Run the following commands:
``` ```
docker-compose run -e SEED_POST_COUNT=100 e621 /app/bin/setup docker compose run --rm -e SEED_POST_COUNT=100 e621 /app/bin/setup
docker-compose up docker compose up
``` ```
After running the commands once only `docker-compose up` is needed to bring up the containers. After running the commands once only `docker compose up` is needed to bring up the containers.
1. To confirm the installation worked, open the web browser of your choice and enter `http://localhost:3000` into the address bar and see if the website loads correctly. An admin account has been created automatically, the username and password are `admin` and `e621test` respectively. 1. To confirm the installation worked, open the web browser of your choice and enter `http://localhost:3000` into the address bar and see if the website loads correctly. An admin account has been created automatically, the username and password are `admin` and `e621test` respectively.
Note: When gems or js packages are updated you need to execute `docker-compose build` to reflect them in the container. Note: When gems or js packages are updated you need to execute `docker compose build` to reflect them in the container.
#### <a id="docker-troubleshooting"></a>I followed the above instructions but it doesn't work, what should I do? #### <a id="docker-troubleshooting"></a>I followed the above instructions but it doesn't work, what should I do?
Try this: Try this:
1. `docker-compose down -v` to remove all volumes. 1. `docker compose down -v` to remove all volumes.
1. `docker-compose build --no-cache` to rebuild the image from scratch. 1. `docker compose build --no-cache` to rebuild the image from scratch.
1. Follow the [instructions](#installation) starting from step 6. 1. Follow the [instructions](#installation) starting from step 6.
#### <a id="development-tools"></a>Things to aid you during development #### <a id="development-tools"></a>Things to aid you during development
`docker-compose run --rm tests` to execute the test suite. `docker compose run --rm tests` to execute the test suite.
`docker-compose run --rm rubocop` to run the linter. Run it against changed files only, there are too many existing violations at the moment. `docker compose run --rm rubocop` to run the linter. Run it against changed files only, there are too many existing violations at the moment.
The postgres server accepts outside connections which you can use to access it with a local client. Use `localhost:34517` to connect to a database named `danbooru2` with the user `danbooru`. Leave the password blank, anything will work. The postgres server accepts outside connections which you can use to access it with a local client. Use `localhost:34517` to connect to a database named `danbooru2` with the user `danbooru`. Leave the password blank, anything will work.