_________.__ .__ .__ ________
/ _____/| |__ |__| _____ _____ |__| ____ \_____ \
\_____ \ | | \ | | / \ / \ | |_/ __ \ / ____/
/ \| Y \| || Y Y \| Y Y \| |\ ___/ / \
/_______ /|___| /|__||__|_| /|__|_| /|__| \___ >\_______ \
\/ \/ \/ \/ \/ \/
This is the main branch of Shimmie, if you know anything at all about running websites, this is the version to use.
Alternatively if you want a version that will never have significant changes, check out one of the versioned branches.
- These are generally based on "whatever is in Debian Stable", because that's conservative without being TOO painfully out of date, and is a nice target for the unit test Docker build.
- A database: PostgreSQL 11+ / MariaDB 10.3+ / SQLite 3.27+
- Stable PHP (7.3+ as of writing)
- GD or ImageMagick
- Download the latest release under Releases.
- Unzip shimmie into a folder on the web host
- Create a blank database
- Visit the folder with a web browser
- Enter the location of the database
- Click "install". Hopefully you'll end up at the welcome screen; if not, you should be given instructions on how to fix any errors~
- Download shimmie via the "Download Zip" button on the master branch.
- Unzip shimmie into a folder on the web host
- Install Composer. (If you don't already have it)
- Run
composer install
in the shimmie folder. - Follow instructions noted in "Installation" starting from step 3.
Useful for testing in a known-good environment, this command will build a simple debian image and run all the unit tests inside it:
docker build -t shimmie .
Once you have an image which has passed all tests, you can then run it to get a live system:
docker run -p 0.0.0.0:8123:8000 shimmie
Then you can visit your server on port 8123 to see the site.
Note that the docker image is entirely self-contained and has no persistence
(assuming you use the sqlite database); each docker run
will give a clean
un-installed image.
I very much recommend going via each major release in turn (eg, 2.0.6 -> 2.1.3 -> 2.2.4 -> 2.3.0 rather than 2.0.6 -> 2.3.0).
While the basic database and file formats haven't changed completely, it's different enough to be a pain.
Various aspects of Shimmie can be configured to suit your site specific needs
via the file data/config/shimmie.conf.php
(created after installation).
Take a look at core/sys_config.php
for the available options that can
be used.
User classes can be added to or altered by placing them in
data/config/user-classes.conf.php
.
For example, one can override the default anonymous "allow nothing" permissions like so:
new UserClass("anonymous", "base", [
Permissions::CREATE_COMMENT => True,
Permissions::EDIT_IMAGE_TAG => True,
Permissions::EDIT_IMAGE_SOURCE => True,
Permissions::CREATE_IMAGE_REPORT => True,
]);
For a moderator class, being a regular user who can delete images and comments:
new UserClass("moderator", "user", [
Permissions::DELETE_IMAGE => True,
Permissions::DELETE_COMMENT => True,
]);
For a list of permissions, see core/permissions.php
ui-* cookies are for the client-side scripts only; in some configurations (eg with varnish cache) they will be stripped before they reach the server
shm-* CSS classes are for javascript to hook into; if you're customising themes, be careful with these, and avoid styling them, eg:
- shm-thumb = outermost element of a thumbnail
- data-tags
- data-post-id
- shm-toggler = click this to toggle elements that match the selector
- data-toggle-sel
- shm-unlocker = click this to unlock elements that match the selector
- data-unlock-sel
- shm-clink = a link to a comment, flash the target element when clicked
- data-clink-sel
Please tell me if those docs are lacking in any way, so that they can be improved for the next person who uses them
Email: webmaster at shishnet.org
Issue/Bug tracker: http://github.com/shish/shimmie2/issues
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.