We have been asking folks to run jekyll import for a while, but it requires a Gemfile. Not everyone wants to have a Gemfile or knows how to set one up. I'd like to be a bit more independent of Jekyll and its not-always-entirely-working system for external subcommands.
This commit adds a new top-level 'jekyll-import' command so that this gem can handle importing without requiring a Gemfile with :jekyll_plugins.
The flow is still rather tedious:
Run jekyll-import to see subcommands
Run jekyll-import <subcommand> --help to see options
Run jekyll-import <subcommand> <options> but get a dependency-not-found error
Run gem install <dependency1> to install
Re-run jekyll-import <subcommand> <options> but get another dependency-not-found error.
Run gem install <dependency_N> to install. Repeat 5 and 6 until all dependencies are satisfied.
Finally, re-run jekyll-import <subcommand> <options> and observe your output site (assuming to bugs in the importer)
parkr
commented
9 months ago
We have been asking folks to run
jekyll importfor a while, but it requires aGemfile. Not everyone wants to have a Gemfile or knows how to set one up. I'd like to be a bit more independent of Jekyll and its not-always-entirely-working system for external subcommands.This commit adds a new top-level 'jekyll-import' command so that this gem can handle importing without requiring a Gemfile with
:jekyll_plugins.The flow is still rather tedious:
jekyll-importto see subcommandsjekyll-import <subcommand> --helpto see optionsjekyll-import <subcommand> <options>but get a dependency-not-found errorgem install <dependency1>to installjekyll-import <subcommand> <options>but get another dependency-not-found error.gem install <dependency_N>to install. Repeat 5 and 6 until all dependencies are satisfied.jekyll-import <subcommand> <options>and observe your output site (assuming to bugs in the importer)Fixes #530.