43.8.1
Powered by

  Playground

You can showcase, clone, and develop a few Pagy apps without needing to set anything up on your side!

$ pagy --help

  Apps

We have a few single-file apps ready to run in your browser for various purposes. Most of them are used to run the E2E Test workflow.

You can use this app as a starting point to try Pagy or reproduce issues to get support or file bug reports.

pagy clone repro

You should find the ./repro.ru cloned app file in the current directory. Feel free to rename or move it as you wish.

This command runs your rackup app with a puma server.

pagy path/to/your-repro.ru

Use it to reproduce Rails-related Pagy issues.

pagy clone rails
pagy ./rails.ru

The interactive showcase for the :rails_active_search paginator, in active and passive modes.

pagy active_search

The interactive showcase for all the pagy helpers and CSS styles.

pagy demo

The interactive showcase and reproduction tool for the :calendar paginator.

pagy calendar

The interactive showcases/repros for the :keyset and :keynav_js paginators with ActiveRecord or Sequel sets, and for multiple independent :keynav_js instances (keynav+root_key):

pagy --help | grep key
  keynav+root_key    Showcase the Keynav pagination with independent instances
  keynav             Showcase the Keynav pagination (ActiveRecord example)
  keyset             Showcase the Keyset pagination (ActiveRecord example)
  keyset_sequel      Showcase the Keyset pagination (Sequel example)

pagy keynav
pagy keynav+root_key
pagy keyset
pagy keyset_sequel

All the pagy apps use bundler/inline, which should be able to install all the gems automatically at app startup.

Depending on your environment, you might get this message for some gem:

You have already activated GEMNAME v1, but your Gemfile requires GEMNAME v2.
Prepending `bundle exec` to your command may solve this.

If bundle exec doesn't solve it, then try bundle update and gem cleanup. If you encounter another error after that:

... `find_spec_for_exe': can't find gem GEMNAME (>= 0.x) with executable EXEC (Gem::GemNotFoundException)

then gem pristine GEMNAME should solve the problem.