This assumes a running setup.
-
Enter into database container:
docker exec \ --interactive \ --username=nano \ --tty kemono-db psql \ kemonodb
-
Check the contents of the
posts
table.SELECT * FROM posts;
Most likely it has
0
rows.
-
Move contents of
booru_posts
➞posts
INSERT INTO posts SELECT * FROM booru_posts ON CONFLICT DO NOTHING;
-
Restart the archiver.
docker restart kemono-archiver
If you see a bunch of log entries from
kemono-db
,
then this indicates that the archiver is doing it's job.
-
In case the frontend still doesn't show
the artists / posts, clear the redis cache.docker exec \ kemono-redis \ redis-cli \ FLUSHALL
This assumes you haven't cloned the repository recursively.
-
Initiate the submodules
git submodule init git submodule update \ --recursive \ --init
-
Switch to the archiver folder and
add your fork to the remotes list.cd archiver git remote add <remote_name> <your_fork_link>
-
Now you can interact with Kitsune repo the same
way you do as if it was outside of project folder.
-
Retrieve a database dump.
-
Run the following in the folder of said dump.
cat db-filename.dump \ | gunzip \ | docker exec \ --interactive kemono-db psql \ --username=nano kemonodb
-
Restart the archiver to trigger migrations.
docker restart kemono-archiver
If that didn't start the migrations, refer
toMy Dump Doesn't Migrate
section.
-
Retrieve the files in required folder structure.
-
Copy them into nginx image.
docker \ cp ./ kemono-nginx:/storage
-
Add required permissions to that folder.
docker \ exec kemono-nginx \ chown --recursive \ nginx /storage