Resolve “No Github API authentication” errorsĪfter making an edit, Jekyll auto-rebuilds the site. there is three version of rough on aur & community: community/ruby-rouge 3.0.0-1, aur/ruby-rouge-1 1.11.1-2 and aur/ruby-rouge-2.0 2.0.7-2, the last one package actually meet the requirement 1.7 the official gemspec file shows that ruby-rouge > 1.7 and < 4 is okay here is 3.6. (Make sure you include the / at the end.) Go to the preview address in the browser.Browse to the directory where you downloaded the Documentation theme for Jekyll.The vanilla Jekyll site you create through jekyll new my-awesome-site doesn’t have a Gemfile, but many other themes (including the Documentation theme for Jekyll) do have a Gemfile. (To learn more about Bundler, see About Ruby Gems. If you have a gem that depends on other gems to work, Bundler will go out and retrieve all of the dependencies as well.
All other applications that need to use Bundler will likely not have the needed permissions to run.īundler goes out and retreives all the gems that are specified in a Jekyll project’s Gemfile. If you use shell.nix in your development workflow, you will need to run nix-shell default.nix instead of just running nix-shell.If you’re prompted to switch to superuser mode ( sudo) to get the correct permissions to install Bundler in that directory, avoid doing this. Changing the Gemfile to require 1.10.10, gem "nokogiri", "~> 1.10.10" and then clearing out the Gemfile.lock and rerunning bundler and bundix should fix it. Other Things to NoteĪs of writing this blog, Nokogiri 1.11 and up has an issue with trying to compile within the nix-shell environment. To run it, you would type nix-shell algolia.nix. If you want Jekyll to automatically run the web server each time you go into nix-shell, change your default.nix to resemble this: with ( import /bin/jekyll algolia to have it index your posts and name it a different file like algolia.nix. Nix-shell -p bundler -p bundix -run 'bundler update bundler lock bundler package -no-install -path vendor bundix rm -rf vendor'
0 kommentar(er)
