Multimedia story telling for the web.
For a high level introduction and example Pageflow stories see pageflow.io.
In addition to this README, there is also a Getting Started Wiki page to guide you through the steps of setting up a Rails application with Pageflow on your development machine.
For instructions on how to update from a prior version of the gem see the Updating Pageflow wiki page.
Pageflow is a Rails engine which roughly consists of the following components:
- A full MVC stack to manage and display Pageflow stories
- User and permission management with support for isolated accounts and user collaboration
- A client side application for live preview editing of stories
- Background jobs to process and encode images, audios and videos
- Generators to quickly bootstrap a new Rails application
Pageflow assumes the following choice of libraries:
- Devise for authentication
- CanCan for authorization
- ActiveAdmin for administration
- Resque for background jobs
- FriendlyId for pretty URLs
- Paperclip for attachment handling
- Backbone Marionette for client side development
Pageflow runs in environments with:
- Ruby >= 1.9.3 and < 2.2.0 because of ActiveAdmin
- Rails 4.0 or 4.1
- Redis server (for Resque)
- A database server supported by Active Record (tested with MySQL)
- ImageMagick
Accounts of the following cloud services have to be registered:
- Amazon Web Services for S3 file storage and (optionally) Cloudfront content delivery
- Zencoder for video/audio encoding
Generate a new Rails application using the MySQL database adapter:
$ rails new my_pageflow --database=mysql
$ cd my_pageflow
Do not name your application "pageflow" since it will cause conflicts
which constant names created by Pageflow itself.
Enter valid MySQL credentials inside config/database.yml and create
the database:
$ rake db:create
Add this line to your application's Gemfile:
# Gemfile
gem 'pageflow'
At the moment, Pageflow depends on a frozen version of Active Admin
since, back when development started, no Rails 4 compatible version of
Active Admin was available as a gem. You therefore need to bundle the
rails4 branch that we have forked into our github organization:
# Gemfile
gem 'activeadmin', git: 'https://github.com/codevise/active_admin.git', branch: 'rails4'
gem 'ransack'
gem 'inherited_resources', '1.4.1'
gem 'formtastic', '2.3.0'
# Only required for Rails 4.1:
gem 'state_machine', git: 'https://github.com/codevise/state_machine.git'
Run bundler to install dependencies:
$ bundle install
Now you can run the generator to setup Pageflow and its dependencies:
$ rails generate pageflow:install
The generator will invoke Active Admin and Devise generators in turn
and apply some configuration changes. When asked to overwrite the
db/seeds.rb file, choose yes.
To better understand Pageflow's configuration choices, you can run the
single steps of the install generator one by one. See the wiki page
The Install Generator in Detail
for more. If you'd rather not look behind the scenes for now, you can
safely read on.
Devise migration name fix: In some cases, the Devise generator creates a migration file without file extension. This needs to be fixed manually at the moment:
$ rename 's/$/.rb/' db/migrate/*_devise_create_users
Now you can migrate the database.
$ rake db:migrate
Finally, you can populate the database with some example data, so things do not look too blank in development mode.
$ rake db:seed
Pageflow stores files in S3 buckets also in development mode. Otherwise there's no way to have Zencoder encode them. See the wiki page Setting up external services.
The host application can utilize environment variables to configure the API keys for S3 and Zencoder. The variables can be found in the generated Pageflow initializer.
For available configuration options and examples see the inline docs
in config/initializers/pageflow.rb in your generated rails app.
Ensure you have defined default url options in your environments
files. Here is an example of default_url_options appropriate for a
development environment in config/environments/development.rb:
config.action_mailer.default_url_options = {host: 'localhost:3000'}
In production, :host should be set to the actual host of your
application.
In addition to the Rails server, you need to start two Rake tasks for the background job processing. First, start a Resque worker which handles jobs from all queues:
$ QUEUE=* rake resque:work
Image and video processing are examples of jobs that are executes by these workers.
Some jobs need to be executed repeatedly. For example, while videos are being encoded by Zencoder, there is a job that runs every few seconds to fetch the current progress. This delayed invocation of jobs is handled by the Resque Scheduler Rake task:
$ QUEUE=* rake resque:scheduler
Consider using the foreman gem to start all of these processes (including the Rails server) with a single command in your development environment.
If you run into problems during the installation of Pageflow, please refer to the Troubleshooting wiki page. If that doesn't help, consider filing an issue.