Photish

Photish is a simple, convention based (but configurable) static photo site generator. Photish allows you to group your photo collections by folder. Metadata can be written alongside the photo in a YAML file with the same name as the photo.

Photish will crawl through your directory of photos and metadata, and render the information in your website templates. Photish supports all template engines implemented by Tilt (currently over 30 formats). It will also read your configuration and automatically convert your images to your configured size, dimensions, colourscheme, etc using ImageMagick or GraphicsMagick. Using this information, Photish creates a complete static website that can be hosted on an NGINX, Apache HTTP Server, or even on Github Pages.

Photish has been created with speed and efficiency in mind. Threads are used to parallelize image transcoding to achieve maximum utilization of your CPU during generation. A cache file is then used to ensure that unless the image has changed, it is not needlessly regenerated. This results in a responsive and fast local development environment, making it easy to perfect the design of your photo based website without having to wait for regeneration.

Example

Photish Montage - A quick mockup to show what can be done with Photish. Source here.

Getting Started

It is strongly recommended to read through the Installation and Usage sections before seriously using Photish, however to get up and running:

1. Ensure ImageMagick (or GraphicsMagick) and Exiftool are installed (see Dependencies)
2. Install Photish with gem install photish or with a native installer
3. Create a base project with photish init --example
4. Generate the HTML using photish generate
5. Run a local HTTP server to view the site with photish host
6. View your photo site at http://localhost:9876

Project Health

Category	Purpose	Badge
Package	RubyGem

         | Debian  | [![Download](https://api.bintray.com/packages/henrylawson/deb/photish/images/download.svg)](https://bintray.com/henrylawson/deb/photish/_latestVersion)
         | RPM     | [![Download](https://api.bintray.com/packages/henrylawson/rpm/photish/images/download.svg)](https://bintray.com/henrylawson/rpm/photish/_latestVersion)

CI/CD Pipeline | Main Build, Package and Release | | JRuby & Rubinius Builds | | Windows Build | Code Quality | Dependency Versions | | Code Climate GPA | | Test Coverage | | Quality Metrics |

Documentation

• Overview
• Latest Version
• Installation
  • Dependencies
  • Ruby Gem
  • Debian Package
  • RPM Package
  • Linux Binaries
  • Windows Binaries
• Usage
  • Initialize
    • Basic Photish Structure
    • Template Engines
    • Site Assets
    • Config File Options
    • Customizing Templates
      • Layout Template
      • Collection Template
      • Album Template
      • Photo Template
      • Template Helpers
    • Custom Rendered Content
      • Gallery Page
      • Asset Page
  • Generate
    • Execution Order
    • Image Conversion Tools
    • Workers and Threads
    • Caching
      • Automatic Rengeneration
      • Forced Regeneration
    • Crude Performance Measures
  • Host
  • Deploy
  • Rake Task
  • Plugins
    • Template Helper Plugins
    • Deployment Engine Plugins
    • Plugin Loading
• Development
  • Code Changes
  • Services
• Contributing
• Versioning
• License

Overview

Photish turns this:

./my_new_photo_site
├── config.yml
├── photos
│   ├── Big Dogs
│   │   ├── Tired Dogs.jpg
│   │   └── Winking Dog.jpg
│   └── Small Dogs
│       ├── Fluffy Dogs
│       │   ├── Exhausted Dogs.jpg
│       │   ├── Exhausted Dogs.yml
│       │   ├── Many Dogs.jpg
│       │   └── Many Dogs.yml
│       ├── Sleepy Dog.jpg
│       ├── Sleepy Dog.yml
│       └── Squishy Dogs
│           └── Big Ear Dog.jpg
└── site
    ├── _templates
    │   ├── album.slim
    │   ├── collection.slim
    │   ├── layout.slim
    │   └── photo.slim
    ├── custom.html
    ├── images
    │   └── crumbs.gif
    └── styles
        └── basic.css

Into this:

./my_new_photo_site
└── output
    ├── big-dogs
    │   ├── index.html
    │   ├── tired-dogs
    │   │   ├── images
    │   │   │   ├── tired-dogs-low.jpg
    │   │   │   └── tired-dogs-original.jpg
    │   │   └── index.html
    │   └── winking-dog
    │       ├── images
    │       │   ├── winking-dog-low.jpg
    │       │   └── winking-dog-original.jpg
    │       └── index.html
    ├── custom.html
    ├── index.html
    ├── small-dogs
    │   ├── fluffy-dogs
    │   │   ├── exhausted-dogs
    │   │   │   ├── images
    │   │   │   │   ├── exhausted-dogs-low.jpg
    │   │   │   │   └── exhausted-dogs-original.jpg
    │   │   │   └── index.html
    │   │   ├── index.html
    │   │   └── many-dogs
    │   │       ├── images
    │   │       │   ├── many-dogs-low.jpg
    │   │       │   └── many-dogs-original.jpg
    │   │       └── index.html
    │   ├── index.html
    │   ├── sleepy-dog
    │   │   ├── images
    │   │   │   ├── sleepy-dog-low.jpg
    │   │   │   └── sleepy-dog-original.jpg
    │   │   └── index.html
    │   └── squishy-dogs
    │       ├── big-ear-dog
    │       │   ├── images
    │       │   │   ├── big-ear-dog-low.jpg
    │       │   │   └── big-ear-dog-original.jpg
    │       │   └── index.html
    │       └── index.html
    ├── images
    │   └── crumbs.gif
    └── styles
        └── basic.css

A breakdown of the before and after is as follows:

1. For the Collection of photos in "Photos" an index.html was created
2. For each Album (that is a folder in the "Photos" collection), an index.html was created in a slugified sub folder
3. For each Photo (an image file in the album), another index.html was created in a slugified sub folder named after the original photo
4. For each of these Photos, a version of the Image was made in both "low" and "original" quality in a sub folder called images

The number of Images and the quality of each is completely configurable. Using the templating language of your choice you can easily generate a Photo collection driven website with all of your photos available in various qualities and formats.

Latest Version

Photish follows Semantic Versioning 2.0.0.

Releases happen regularly and automatically from Snap-CI.

The latest version is published with artifacts on GitHub.

Installation

Photish is available across all platforms as a Ruby Gem. The recommended installation is the Ruby Gem as not all features are currently available on the platform native packages.

For convenience Photish is also packaged in platform native installers. The platform native installers come with all the Ruby Gems and Ruby runtime bundled inside the package. This means you simply need to install the package and you can immediately use Photish without having to configure Ruby or any Gems, this is done using Travelling Ruby.

Instructions are provided for each platform native installation:

• Debian Package
• RPM Package
• Linux Binaries
• Windows Binaries

Dependencies

Photish has dependencies on certain software:

• ImageMagick or GraphicsMagick for image conversion
• Exiftool for image metadata retrieval

These packages are not listed as hard dependencies in any of the provided packages as it is only needed during runtime, and in the case of Exiftool, if Exif Metadata is not read during the generation of any templates, the dependency is not required.

On MacOSX, using Brew

$ brew install imagemagick # or brew install graphicsmagick
$ brew install exiftool

On Ubuntu or Debian

$ sudo apt-get install imagemagick # or sudo apt-get install graphicsmagick
$ sudo apt-get install libimage-exiftool-perl

On CentOS, RedHat, etc.

$ sudo yum install ImageMagick
$ sudo yum install perl-Image-ExifTool

On Windows

Please check the dependencies website for the latest Windows installation steps.

Ruby Gem

Photish supports multiple ruby versions:

The latest version and all releases of Photish are tested against the above ruby versions in the CI pipeline.

Before installing Photish, ensure you have the latest version of Bundler for your ruby version.

Install the gem locally by running:

$ gem install photish

Alternatively, use Bundler. Create a folder for your photo site so you can track the version of Photish you are building with:

$ mkdir my_new_photo_site
$ cd my_new_photo_site
$ bundle init
$ echo 'gem "photish"' >> Gemfile
$ bundle install

Debian Package

The latest Debian package for amd64 and i386 architectures is available on Bintray and uploaded to the latest Photish Github Release.

To be up to date with the latest version of Photish, we recommend you add our Debian repository and install using apt-get:

$ # add the repository and SSH key
$ echo "deb https://dl.bintray.com/henrylawson/deb all main" | sudo tee -a /etc/apt/sources.list
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F608A664B7DFFFEA
$
$ # update keys and latest packages
$ sudo apt-get update && sudo apt-key update
$
$ # install photish
$ sudo apt-get install photish

If you have downloaded the *.deb file, simply install it with dpkg:

$ sudo dpkg -i photish*.deb

RPM Package

The latest RPM package for x86_64 and i386 architectures is available on Bintray and uploaded to the latest Photish Github Release.

To be up to date with the latest version of Photish, we recommend you add our YUM repository and install using yum:

$ # add the repository and SSH key
$ wget https://bintray.com/henrylawson/rpm/rpm -O bintray-henrylawson-rpm.repo
$ sudo mv bintray-henrylawson-rpm.repo /etc/yum.repos.d/
$
$ # install photish
$ sudo yum install -y photish

If you have downloaded the *.rpm file, simply install it with rpm:

$ sudo rpm -Uh photish*.rpm

Linux Binaries

If you are using a distribution of Linux that we do not have a native package installer for, you can manually install Photish and use it by downloading the Photish x64 and x86 binaries from the Photish Github Release.

You can then extract the binaries to your desired location and use them.

$ tar -zxf photish-*-linux-*.tar.gz -C /destination

Windows Binaries

If you are using Windows, you can manually install Photish and use it by downloading the Photish x86 binaries from the Photish Github Release.

You can then extract the binaries to your desired location and use them.

Usage

Once you have photish installed. Get started with the following commands:

Initialize

A skeleton site can be created by running the below command inside the my_new_photo_site folder:

$ photish init --example

A barebones site can be created with:

$ photish init

Basic Photish Structure

Inside your my_new_photo_site folder, you will have a:

Template Engines

By default Photish uses Slim as the template language. The templates can be in any format supported by Tilt. To use a different template language:

1. Create a layout, collection, album and photo file in the site/_templates folder, with the file extension of the template engine you prefer, supported extensions are documented by Tilt
2. Update config.yml to reference your newly created template files
3. Re write the basic template code in your chosen language

Site Assets

Any content not starting with an _ (underscore) in the site folder will be copied to the output folder.

In the example in the Overview section. There are a few static asset files. These are:

1. site/styles/basic.css
2. site/images/crumbs.gif
3. site/custom.html

Both of these files were copied by Photish to the output folder, respecting their folder/file hierarchy:

1. output/styles/basic.css
2. site/custom.html

As documented in the Generate section, assets are copied before the site content is generated. If an asset has a conflicting name and path with a generated file, the generated file will clobber the asset.

Config File Options

The default way to express config is in the config.yml file. However config can also be overridden using the --config_override flag to any of the Photish commands. When using the --config_override flag, the config must be expressed as JSON. For example, to override logging when calling the Generate command, you can use:

$ photish generate --config_override='{"logging":{"colorize":false}}'

This method of config override is only recommended for cases where the value needs to be temporarily overridden, such as during a deployment or while debugging.

Below is a complete config.yml file, recommended practice is to only set the config values you need, otherwise just use the defaults, the file can be empty and Photish will still function:

port: 9876
qualities:
  - name: Original
    params: []
  - name: Low
    params: ['-resize', '200x200']
templates:
  layout: layout.slim
  collection: collection.slim
  album: album.slim
  photo: photo.slim
logging:
  colorize: true
  level: 'debug'
  output: ['stdout', 'file']
url:
  host: http://mydomain.com
  base: 'subdirectory'
  type: 'relative_uri'
workers: 4
threads: 2
force: false
plugins: ['ssh_deploy', 'other_plugin']
image_extensions: ['jpg', 'gif']
page_extension: 'slim'
dependencies:
  minimagick:
    cli: 'imagemagick'
    cli_path: '/usr/bin/convert'
    timeout: 3600
  miniexiftool:
    command: '/usr/bin/'

The meanings and purpose of each field is defined below:

Customizing Templates

Below is the documentation for the various data available inside each of the templates.

Note: {type} is a place holder depending on your chosen template engine the file extension will change. By default the template engine is Slim, so templates will end with the slim extension.

Layout Template

site/_templates/layout.{type}

Example:

doctype html
html
  head
    title Master Layout
  body
    == yield

The layout template is the base layout for all the other templates. The collection, album and photo templates will be rendered inside this layout. The layout template must include the yield statement to bind the sub template inside it. Below is an example Slim template, the other templates will be bound where the yield statement is:

Collection Template

site/_templates/collection.{type}

Example:

h1 Photo Collection
- albums.each do |album|
  div.album
    div.album-title
      a href=album.url
        | #{album.name}

The collection template becomes the index.html for the root of the website.

This template is passed the Collection model when rendered.

Album Template

site/_templates/album.{type}

Example:

h1 Album
h2
  a href=url
    | #{name}
div.album-photos
  - photos.each do |photo|
    div.album-photo
      a href=photo.url title=photo.name
        img src=photo.images.find{ |i|i.quality_name=='Low' }.url alt=photo.name

For each folder in the photos directory, a slugified album folder is created with an index.html in it.

This template is passed the Album model when rendered.

Photo Template

site/_templates/photo.{type}

Example:

h1 Photo
h2
  a href=url
    | #{name}
  div.album-photos
    - images.each do |image|
      div.album-photo
        a href=image.url title=image.name
          img src=image.url alt=image.quality_name

For each image in an Albums directory, a slugified photo folder is created with an index.html in it.

This template is passed the Photo model when rendered.

Template Helpers

A template helper is a simple method that is available in the template that can be called to render complex information.

For example in a template, the method breadcrumbs can be called:

div.content
  div.site-breadcrumbs
    == breadcrumbs

When rendered this will result in an unordered list of pages above the current page in the hierarchy:

<div class="content">
  <div class="site-breadcrumbs">
    <ul class="breadcrumbs">
      <li class="breadcrumb crumb-0 crumb-first">
        <a href="/index.html">Home</a>
      </li>
      <li class="breadcrumb crumb-1">
        <a href="/big-dogs/index.html">Big Dogs</a>
      </li>
      <li class="breadcrumb crumb-2 crumb-last">
        <a href="/big-dogs/tired-dogs/index.html">Tired Dogs</a>
      </li>
    </ul>
  </div>
</div>

Custom template helpers are supported through Plugins.

By default, Photish comes with the following helpers:

Custom Rendered Content

Gallery Page

A gallery page is a simple way to create a custom web page within the collection or album of your gallery that will render within your site's Layout Template.

For example, if you would like to create a "more details" page somewhere within an album, or the collection root, and you would like it rendered in the Layout Template to have a consistent look and feel, you can do it by creating a Gallery Page such as more-about.slim anywhere in your photos directory. The file extension is determined using the page_extension Config File Option. A Gallery Page can live anywhere and you can have as many of them as you like within the photos directory.

photos/**/*.{page_extension}

div.more-about-album
  h2 The More Details Page
  p Lorem ipsum...
  p Lorem ipsum...
  p Lorem ipsum...

As with other gallery generated content, a gallery page is accessible from the all_pages method within the Collection or Album template.

Asset Page

An Asset Page is a custom page that lives inside your site directory that is rendered using your template engine of choice. When an Asset Page template is rendered it is not rendered inside the site's Layout Template. Asset Page's are standalone templates. Like other assets, they maintain the same folder structure in the output directory that they have in the site directory. When rendered, the template is passed the Collection model, as such they have access to all attributes that a Collection Template does.

For example, if you would like to create an index page of all albums in your collection you can create the following file:

site/index/all_albums.html.{page_extension}

doctype html
html
  head
    title All Albums
  body
    ol
      - all_albums.each do |album|
        li #{album.name}

When rendered, the above Asset Page will be available at http://localhost:9876/index/all_albums.html.

It is important to note that once rendered, the template extension is removed and the basename is used for the final filename. This allows you to specify custom extensions before the page_extension such as TXT or XML. In the example above, HTML is specified.

An example usage of an Asset Page is in the include example site, it uses an Asset Page to create a sitemap.xml

Generate

The static HTML can be generated by running the below command inside the my_new_photo_site folder:

$ photish generate

All generated content will be written to the output folder by default.

Execution Order

The Generate command does the following:

1. Crawls the photos directory for photos and metadata
2. Creates a site structure of Collection, Album(s), Photo(s) and Image(s)
3. Copies all files in the site folder not beginning with an _ (underscore) to the output folder as these are viewed as "static" assets. That is, folders like _templates are ignored
4. Renders the HTML index file(s) for the Collection, Album(s), Photo(s) and Image(s) to the output folder
5. Converts all Photo(s) to the configured quality versions, writing various images to the output folder

Image Conversion Tools

Photish supports ImageMagick or GraphicsMagick for image conversion.

By default, Photish will assume ImageMagick is installed. To change this, ensure GraphicsMagick is installed and the utility is availabe on the PATH. Then ensure that the Config File Option dependencies/minimagick/cli is set to graphicsmagick. For example:

dependencies:
  minimagick:
    cli: graphicsmagick

If ImageMagick or GraphicsMagick is not available on the PATH you can manually specify it's location by setting dependencies/minimagick/cli_path. For example:

dependencies:
  minimagick:
    cli_path: '/usr/bin/convert'

Workers and Threads

In order to achieve maximum utilization of all processors on a computer during generation, Photish has the ability to create multiple workers and threads.

A worker is a spawned sub process created by the Generate command. The worker sub process is responsible for generating the HTML and Images for a subset of the collection.

Within each worker, threads are created when calling out to the Image Magick binary. During conversion, Image Magick often does not reach full processor utilization so rather then block the whole worker, it can be more performant to spawn multiple Image Magick processes at once.

For collections with a large number of images and HTML pages, multiple workers and threads can be used to rapidly speed up generation. However, if the collection has a small number of photos and pages, workers and threads will increase the generation time as loading a new ruby process and creating multiple threads may have a higher setup time then just generating everything in a single ruby process and thread.

The number of workers and threads is configurable in the config file with the workers and threads options. By default, Photish will spawn a thread for each processor detected on the computer. It will then run this on a single worker.

When configuring more than 1 worker, it is important to remember that each worker will spawn their own set of threads, if 4 workers are created, each with 2 threads, it means in total Photish will manage 8 threads and potentially run 8 Image Magick processes concurrently. When tweaking the number of workers and threads it is important to consider IO bottlenecks as this will most likely be the limiting factor in performance.

Caching

Photish caches the generation of images to avoid regeneration when the Generate command is run or the generate event is triggered while hosting a local version of Photish with the Host command.

The cache file is stored in the output_dir and is named .changes.yml.

Automatic Regeneration

Images are regenerated when a photo is modified, renamed or moved.

Changing the qualities option in the config file will also trigger a full regeneration of all images.

Forced Regeneration

To do a full regeneration, run the Generate command with the --force flag:

$ photish generate --force

The host command also supports the --force flag, to do a full regeneration on every change:

$ photish host --force

Crude Performance Measures

Below are some crude performance measures to get a ballpark idea of how Photish performs when generating for a large collection.

Benchmark Computer:

MacBook Pro (Retina, 13-inch, Early 2015)
2.7 GHz Intel Core i5 (4 processors)
8 GB 1867 MHz DDR3

It is interesting to note the 20-30 second difference between using 4 workers vs. 4 threads. The time difference is due to the setup time of creating a whole new ruby process for each worker.

Host

To test and view your changes locally, the host command can be used to run a local WEBrick server to serve the HTML files:

$ photish host

The local version of your website will be visible at http://localhost:9876/.

The Host command will also automatically regenerate the website on startup and when a file is added, removed or modified in the photo_dir or site_dir.

Note, when running in this mode any Image Conversion errors are swallowed and logged. This is done as it is quite common for image files to be moved while conversion is in progress. Rather then terminate the Host, the file move is recorded and regeneration will be triggered once the current generation completes.

Deploy

Photish provides a plugin type specifically for deployments, called the Deployment Engine. Once a deploy plugin is configured, it can be ran by passing the deploy plugins name as a value with the engine argument.

$ photish deploy --engine=name

To utilize a Deployment Engine Plugin someone in the community has written, take a look at Plugin Loading for how to include it in your site.

If you would like to write a Deployment Engine Plugin instructions are available in the plugin section.

Rake Task

If you would prefer to use Photish as a task in Rake. A helper class is available to create custom rake tasks that call Photish. The helper class is defined in Photish::Rake::Task.

In your Rakefile, simply add the following to wrap the generate command:

Photish::Rake::Task.new(:generate, 'Compiles the project to HTML') do |t|
  t.options = "generate"
end

The above code will define a rake task called generate which can be ran by using rake generate. It is the equivalent of photish generate.

Plugins

Photish supports extension through the creation of plugins.

Template Helper Plugins

To create a template helper plugin you must:

1. Create a Ruby Module in the Photish::Plugin module namespace, if you are packaging the plugin as a Gem, you can implement your module one level deeper in the namespace to allow for the Gem namespace, e.g. Photish::Plugin::MyGemPlugin::MyTemplateHelper
2. Make the plugin available for loading
3. Implement the self.is_for?(type) method
4. Implement your custom helper method(s)

A simple plugin is bellow, this plugin is for all Photo Template's as the self.is_for?(type) method only returns true for Photish::Plugin::Type::Photo types. When the shout method is called inside the template, it will render the message in bold wrapped in the "I am shouting" text.

site/_plugins/shout.rb

module Photish::Plugin::Shout
  def self.is_for?(type)
    Photish::Plugin::Type::Photo == type
  end

  def shout(message)
    "<strong>I am shouting '#{message}'!!!</strong>"
  end
end

A Template Helper Plugin self.is_for?(type) method could potentially receive any of the below types, simply return true for the types the Template Helper Plugin supports:

1. Photish::Plugin::Type::Collection
2. Photish::Plugin::Type::Album
3. Photish::Plugin::Type::Photo
4. Photish::Plugin::Type::Image
5. Photish::Plugin::Type::Page

To use the Template Helper Plugin, simply call the custom method(s) in your template file. For the above example, it can be used by calling the shout method in a template file:

site/_templates/photo.slim

div.my-shouting-content
  == shout("HELLO")

Some "core" Template Helper plugins available in Photish by default are:

1. Breadcrumb
2. BuildUrl
3. Metadatable
4. Exifable

Deployment Engine Plugins

To create a deployment engine plugin you must:

1. Create a Ruby Class in the Photish::Plugin module namespace, if you are packaging the plugin as a Gem, you can implement your module one level deeper in the namespace to allow for the Gem namespace, e.g. Photish::Plugin::MyGemPlugin::MyDeployEngine
2. Make the plugin available for loading
3. Implement a self.is_for?(type) method and respond true when it receives the Photish::Plugin::Type::Deploy type
4. Implement a self.engine_name method and respond with the name of the engine, this needs to match the value the user will pass on the Deploy command
5. Implement a constructor, it should expect two argumnets initialize(config, log), a structure representing the config file and an instance of the logger
6. Finally the plugin should also implement a deploy_site method, this method will execute the actual deployment

A simple sample implementation is below:

site/_plugins/my_custom_deploy.rb

module Photish::Plugin::MyCustomDeploy
  def initialize(config, log)
    @config = config
    @log = log
  end

  def self.is_for?(type)
    Photish::Plugin::Type::Photo == type
  end

  def self.engine_name
    'my_custom_deploy'
  end

  def deploy_site
    @log.debug "Deploying using my plugin"
    FileUtils.cp(@config.output_dir, '/srv/www')
  end
end

Some reference implementations of deploy plugins are:

1. Photish SSH Deploy
2. Tmp Dir Deploy

Plugin Loading

Photish supports the following methods of Plugin loading.

Site Folder Loading

By default, Photish will automatically load all files in the site/_plugins directory. This is the most simple way and is recommended if you just want to write a simple helper specific to your site.

The example site created when running photish generate --example uses this method to load plugins.

Explicit Gem Loading

This is recommended method if you want to utilize a plugin created by someone else in the community - rather than simply copy pasting their code to your site/_plugins directory. It is done by including a Gem in your Photish site's Gemfile and listing the require path of the Gem in the plugins Config File Option.

An example of Explicit Gem Loading is provided by the Photish Montage demo that explicitly loads the Photish::Plugin::Sshdeploy Gem.

To load a Gem as a plugin, first of all add the Gem to your Gemfile:

Gemfile

gem 'photish-plugin-sshdeploy'

And in your Photish config, ensure it is listed in your plugins Config File Option.

config.yml

plugins: ['photish/plugin/sshdeploy']

Then run bundle install.

To confirm that it is installed correctly, when you run the photish generate command, you should see the plugin load:

log/photish.log or STDOUT

...
... Photish::Plugin::Repository: Found plugin Photish::Plugin::Sshdeploy::Deploy
...

Note the 'photish-plugin-sshdeploy' Gem has other install steps documented in it's README.

Development

Code Changes

If you would like to contribute to Photish by creating a new feature or fixing bugs, you are more then welcome!

To develop:

$ git clone [email protected]:henrylawson/photish.git
$ cd photish
$ ./bin/setup     # installs dependencies mentioned in output
$ rake            # runs the tests
$ vim             # open up the project and begin contributing
$ ./bin/console   # for an interactive prompt

To release:

$ rake dev:bump       # update version, create commit when prompted

The Snap CI will then detect that this is a tagged commit on MASTER and it will generate a build and release it.

If you need ideas on how to help, checkout our TODO list.

Services

Photish uses a range of services. Before contributing it is worth browsing through these services to understand how Photish is configured and is using them:

1. Snap CI is used as the primary CI/CD server. All builds and tests are ran from Snap CI. Snap CI is also used to release new versions of Photish to Github and Bintray.
2. Github is used for source control. It is also used to record releases, issues, documentation and todos.
3. Travis CI is used for the testing of JRuby and Rubinius builds.
4. AppVeyor is used for testing and packaging of the Windows build.
5. Code Climate is used to monitor high test coverage and quality code.
6. Gemnasium is used to ensure all dependencies are up to date.
7. Bintray DEB & RPM binary install packages for Linux distributions.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/henrylawson/photish. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

License

The gem is available as open source under the terms of the MIT License.