An easy-to-install community image gallery (aka booru)
https://github.com/shish/shimmie2/
db0e788a67
Rather than ImageAddition triggering TagsSet/SourceSet/LockSet etc in one way, and ImageInfoSet triggering TagsSet/SourceSet/LockSet in a different way, why not have ImageAddition *just* deal with image addition, and then send a separate ImageInfoSet to deal with all of the metadata setting? |
||
---|---|---|
.devcontainer | ||
.docker | ||
.github | ||
core | ||
ext | ||
tests | ||
themes | ||
.dockerignore | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.htaccess | ||
.php-cs-fixer.dist.php | ||
composer.json | ||
composer.lock | ||
Dockerfile | ||
index.php | ||
LICENSE.txt | ||
README.md |
_________.__ .__ .__ ________
/ _____/| |__ |__| _____ _____ |__| ____ \_____ \
\_____ \ | | \ | | / \ / \ | |_/ __ \ / ____/
/ \| Y \| || Y Y \| Y Y \| |\ ___/ / \
/_______ /|___| /|__||__|_| /|__|_| /|__| \___ >\_______ \
\/ \/ \/ \/ \/ \/
Shimmie
Documentation
- Install straight on disk
- Install in docker container
- Upgrade process
- Basic settings
- Advanced config
- Developer notes
- High-performance notes
Licence
All code is released under the GNU GPL Version 2 unless mentioned otherwise.
If you give shimmie to someone else, you have to give them the source (which should be easy, as PHP is an interpreted language...). If you want to add customisations to your own site, then those customisations belong to you, and you can do what you want with them.