#
Pagy Playground
You can showcase, clone and develop a few pagy APPs without the need to setup anything on your side!
$ pagy --help
bundle exec pagy
Depending on your environment you may need to prepend bundle exec
in all the examples shown.
#
Pagy Apps
We have a few single-file apps ready to run in your browser for various purposes: they are all tested and used to run the E2e Test workflow.
#
1. Repro App
You can use this app as a starting point to try pagy or reproduce issues, in order to get support or file bugs reports.
repro
app
pagy clone repro
You should find the ./repro.ru
cloned app file in the current dir. Feel free to rename or move it as you like.
This command runs your rackup
app with a puma
server, with rerun
that auto-restart it when it changes:
pagy path/to/your-repro.ru
Point a browser to http://0.0.0.0:8000
Edit it at will.
Tip
Bundler installs the required gems during the first run. After that you can skip the rubygem
checks by passing the --no-istall
flag
#
2. Rails App
You can use this app as a starting point to reproduce rails related pagy issues. It has the same usage as the
pagy clone rails
pagy ./rails.ru
#
3. Demo App
This is the interactive showcase for all the pagy helpers and CSS styles.
Try it now!
Run the interactive demo from your terminal:
pagy demo
# or bundle exec pagy demo (depending on your env)
...and point your browser to http://0.0.0.0:8000
Run pagy clone demo
to inspect the app file
If you want to see how your CSSs changes look, you can follow the same usage as the
#
4. Calendar App
This is the interactive showcase/repro for the calendar extra:
Try it now!
Run the interactive demo from your terminal:
pagy calendar
...and point your browser to http://0.0.0.0:8000
Run pagy clone calendar
to inspect the app file.
If you need to reproduce any calendar related issue, you can follow the same usage as the
#
Troubleshooting
All the pagy apps use bundler/inline.
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 after that you get into another error:
... `find_spec_for_exe': can't find gem GEMNAME (>= 0.x) with executable EXEC (Gem::GemNotFoundException)
then gem pristine GEMNAME
should solve the problem.
Rerun is used for restarting your app automatically during development.
That's very convenient, but it may still have some rough edges:
** ERROR: directory is already being watched! **
Your app is in a dir with looping simlinks, and the listen
gem cannot handle it.
Move your app in a different dir
On certain filesystems...
It might not work properly or it may require additional dependencies.
Pass the --no-rerun
option to work with rackup only.
pagy ./my-repro.ru --no-rerun