shimmie2/README.md

157 lines
5.3 KiB
Markdown
Raw Normal View History

```
2012-02-12 13:42:37 -06:00
_________.__ .__ .__ ________
/ _____/| |__ |__| _____ _____ |__| ____ \_____ \
\_____ \ | | \ | | / \ / \ | |_/ __ \ / ____/
/ \| Y \| || Y Y \| Y Y \| |\ ___/ / \
/_______ /|___| /|__||__|_| /|__|_| /|__| \___ >\_______ \
2014-04-26 16:52:31 -05:00
\/ \/ \/ \/ \/ \/
```
2012-02-12 13:40:38 -06:00
2014-04-26 16:52:31 -05:00
# Shimmie
[![Build Status](https://travis-ci.org/shish/shimmie2.svg?branch=master)](https://travis-ci.org/shish/shimmie2)
[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/shish/shimmie2/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/shish/shimmie2/?branch=master)
[![Code Coverage](https://scrutinizer-ci.com/g/shish/shimmie2/badges/coverage.png?b=master)](https://scrutinizer-ci.com/g/shish/shimmie2/?branch=master)
(master)
2014-04-26 16:52:31 -05:00
This is the main branch of Shimmie, if you know anything at all about running
websites, this is the version to use.
2014-04-26 16:47:14 -05:00
2014-04-26 16:52:31 -05:00
Alternatively if you want a version that will never have significant changes,
check out one of the versioned branches.
2014-04-26 16:52:31 -05:00
# Requirements
- 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](https://en.wikipedia.org/wiki/PHP#Release_history) (7.3+ as of writing)
- GD or ImageMagick
2014-04-26 16:52:31 -05:00
# Installation
1. Download the latest release under [Releases](https://github.com/shish/shimmie2/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)
2019-10-01 04:51:13 -05:00
1. Download shimmie via the "Download Zip" button on the [master](https://github.com/shish/shimmie2/tree/master) branch.
2016-06-18 22:55:32 -05:00
2. Unzip shimmie into a folder on the web host
3. Install [Composer](https://getcomposer.org/). (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.
2018-11-10 05:19:56 -06:00
# Docker
2019-01-06 05:55:08 -06:00
Useful for testing in a known-good environment, this command will build a
simple debian image and run all the unit tests inside it:
2018-11-10 05:19:56 -06:00
```
docker build -t shimmie .
```
2019-01-06 05:55:08 -06:00
Once you have an image which has passed all tests, you can then run it to get
a live system:
2018-11-10 05:19:56 -06:00
```
docker run -p 0.0.0.0:8123:8000 shimmie
```
Then you can visit your server on port 8123 to see the site.
2019-01-06 05:55:08 -06:00
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.
2018-11-10 05:19:56 -06:00
2014-04-26 16:52:31 -05:00
### Upgrade from earlier versions
2010-03-01 20:48:11 -06:00
I very much recommend going via each major release in turn (eg, 2.0.6
2014-04-26 16:47:14 -05:00
-> 2.1.3 -> 2.2.4 -> 2.3.0 rather than 2.0.6 -> 2.3.0).
2019-01-06 05:55:08 -06:00
While the basic database and file formats haven't changed *completely*, it's
different enough to be a pain.
2010-03-01 20:48:11 -06:00
2014-04-26 16:52:31 -05:00
## 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).
2019-06-12 17:35:32 -05:00
Take a look at `core/sys_config.php` for the available options that can
be used.
2014-04-26 16:52:31 -05:00
#### Custom User Classes
2014-04-26 16:52:31 -05:00
User classes can be added to or altered by placing them in
`data/config/user-classes.conf.php`.
2014-04-26 16:47:14 -05:00
2019-01-06 05:55:08 -06:00
For example, one can override the default anonymous "allow nothing"
permissions like so:
2012-03-19 06:27:01 -05:00
```php
2019-06-14 12:45:15 -05:00
new UserClass("anonymous", "base", [
2019-07-09 09:10:21 -05:00
Permissions::CREATE_COMMENT => True,
Permissions::EDIT_IMAGE_TAG => True,
Permissions::EDIT_IMAGE_SOURCE => True,
Permissions::CREATE_IMAGE_REPORT => True,
2019-06-14 12:45:15 -05:00
]);
```
2012-03-19 06:27:01 -05:00
2014-04-26 16:47:14 -05:00
For a moderator class, being a regular user who can delete images and comments:
2012-04-28 05:02:12 -05:00
```php
2019-06-14 12:45:15 -05:00
new UserClass("moderator", "user", [
2019-07-09 09:10:21 -05:00
Permissions::DELETE_IMAGE => True,
Permissions::DELETE_COMMENT => True,
2019-06-14 12:45:15 -05:00
]);
```
2012-04-28 05:02:12 -05:00
2019-07-09 09:10:21 -05:00
For a list of permissions, see `core/permissions.php`
2012-03-19 06:27:01 -05:00
2014-04-26 16:52:31 -05:00
# Development Info
2019-01-06 05:55:08 -06:00
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
2019-01-06 05:55:08 -06:00
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
2010-07-07 07:02:27 -05:00
Please tell me if those docs are lacking in any way, so that they can be
improved for the next person who uses them
2014-04-26 16:52:31 -05:00
# Contact
Email: webmaster at shishnet.org
Issue/Bug tracker: http://github.com/shish/shimmie2/issues
2014-04-26 16:52:31 -05:00
# Licence
All code is released under the [GNU GPL Version 2](http://www.gnu.org/licenses/gpl-2.0.html) 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.