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

[Misc] Tweak readme (again)

Browse Source 
Accidentally wrote over updated instructions.
This commit is contained in:
Cinder 2024-07-20 08:52:33 -07:00 committed by GitHub
parent 724508731f
commit 8dea243a58
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -38,11 +38,17 @@
1. Copy the sample environment file with `cp .env.sample .env`.
1. Run the following commands:
```
docker compose run --rm -e SEED_POST_COUNT=100 e621 /app/bin/setup
docker compose run --rm e621 /app/bin/setup
docker compose up
```
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 `qwerty` respectively.
1. By default, the site will lack any content. For testing purposes, you can generate some using the following command:
```
docker exec -it e621ng-e621-1 /app/bin/populate
```
The command can be run multiple times to generate more content.
Environmental variables are available to customize what kind of content is generated.
Note: When gems or js packages are updated you need to execute `docker compose build` to reflect them in the container.
@ -98,4 +104,4 @@ correct.
3) Test Nginx to make sure it's working correctly. You may need to
debug your Nginx configuration file.
4) Check all log files.
4) Check all log files.