A fork of shimmie2 maintianed by cavemanon for our booru
Go to file
2019-05-29 18:23:29 +01:00
core more lint fixes 2019-05-29 18:23:29 +01:00
ext more lint fixes 2019-05-29 18:23:29 +01:00
tests PSR-2. I'm not a huge fan, but ugly consistency beats no consistency... 2019-05-28 17:59:38 +01:00
themes more lint fixes 2019-05-29 18:23:29 +01:00
.buildpath playing with eclipse... 2012-08-15 20:11:10 +01:00
.dockerignore A docker container for making testing easier 2018-11-07 00:43:01 +00:00
.editorconfig PSR-2. I'm not a huge fan, but ugly consistency beats no consistency... 2019-05-28 17:59:38 +01:00
.gitignore PSR-2. I'm not a huge fan, but ugly consistency beats no consistency... 2019-05-28 17:59:38 +01:00
.htaccess move images and thumbs to data/ 2018-11-07 16:06:10 +00:00
.php_cs.dist PSR-2. I'm not a huge fan, but ugly consistency beats no consistency... 2019-05-28 17:59:38 +01:00
.project playing with eclipse... 2012-08-15 20:11:10 +01:00
.scrutinizer.yml make handle_static its own extension 2018-11-11 17:38:32 +00:00
.travis.yml bump travis too 2019-05-28 19:20:21 +01:00
composer.json more lint fixes 2019-05-29 18:23:29 +01:00
composer.lock rebuild composer.lock with php7.0 instead of 7.1 2018-02-20 22:14:18 +00:00
Dockerfile specify DB in docker env 2019-02-02 12:06:30 +00:00
index.php more lint fixes 2019-05-29 18:23:29 +01:00
LICENSE.txt Create LICENSE.txt 2016-11-27 20:28:16 +00:00
README.markdown forgot that php isn't python 2019-05-28 15:16:22 +01:00

     _________.__     .__                   .__         ________   
    /   _____/|  |__  |__|  _____    _____  |__|  ____  \_____  \  
    \_____  \ |  |  \ |  | /     \  /     \ |  |_/ __ \  /  ____/  
    /        \|   Y  \|  ||  Y Y  \|  Y Y  \|  |\  ___/ /       \  
   /_______  /|___|  /|__||__|_|  /|__|_|  /|__| \___  >\_______ \ 
           \/      \/           \/       \/          \/         \/ 
                                                                

Shimmie

Build Status Scrutinizer Code Quality Code Coverage (master)

Build Status Scrutinizer Code Quality Code Coverage (develop)

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.

Requirements

  • MySQL/MariaDB 5.1+ (with experimental support for PostgreSQL 9+ and SQLite 3)
  • Stable PHP (7.1+ as of writing)
  • GD or ImageMagick

Installation

  1. Download the latest release under Releases.
  2. Unzip shimmie into a folder on the web host
  3. Create a blank database
  4. Visit the folder with a web browser
  5. Enter the location of the database
  6. Click "install". Hopefully you'll end up at the welcome screen; if not, you should be given instructions on how to fix any errors~

Installation (Development)

  1. Download shimmie via the "Download Zip" button on the develop branch.
  2. Unzip shimmie into a folder on the web host
  3. Install Composer. (If you don't already have it)
  4. Run composer install in the shimmie folder.
  5. Follow instructions noted in "Installation" starting from step 3.

Docker

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.

Upgrade from earlier versions

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.

Custom Configuration

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.inc.php for the available options that can be used.

Custom User Classes

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", array(
	"create_comment" => True,
	"edit_image_tag" => True,
	"edit_image_source" => True,
	"create_image_report" => True,
));

For a moderator class, being a regular user who can delete images and comments:

new UserClass("moderator", "user", array(
	"delete_image" => True,
	"delete_comment" => True,
));

For a list of permissions, see core/userclass.class.php

Development Info

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

Contact

Email: webmaster at shishnet.org

Issue/Bug tracker: http://github.com/shish/shimmie2/issues

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.