“How to fix ‘Auto-regeneration infinine loop’ in Jekyll” - jekyll

How to fix ‘Auto-regeneration infinine loop’ error in Jekyll?
Installed newest version: Ruby, Gem.
Created new project's => Same error.
Regenerating: 7 file(s) changed at 2019-08-15 21:25:54
_site/404.html
_site/about/index.html
_site/index.html
_site/assets/main.css
_site/feed.xml
_sg. See the How to Ask page for help clarifying this question.g. See the How to Ask page for help clarifying this question.ite/2019/08/15/Testseite.html
_site/jekyll/update/2019/08/15/welcome-to-jekyll.html
Jekyll Feed: Generating feed for posts
...done in 0.1852189 seconds.
This output came over and over again.

I find out, the problem was a directory read-only story.

I solved this by commenting gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin] in Gemfile.

Related

How to solve Jekyll-Include-Cache issue?

I am currently trying to open an already created website made through Jekyll. I use the cd command through the terminal to get to the website file that I pulled from Github. Once I get to the file, I run bundle exec Jekyll serve and it shows this error message:
Dependency Error: Yikes! It looks like you don't have Jekyll-include-cache or one of its dependencies installed. In order to use Jekyll as currently configured, you'll need to install this gem. The full error message from Ruby is: 'cannot load such file -- Jekyll-include-cache' If you run into trouble, you can find helpful resources at https://jekyllrb.com/help/!
Jekyll 3.8.5 | Error: Jekyll-include-cache
So I then do gem install Jekyll-include-cache and the issue remains. Does anyone know how to fix this??
The error message means that Jekyll couldn't load the plugin properly.
Ensure that you have listed the plugin in your Gemfile:
# Gemfile
gem "jekyll-include-cache"

jekyll-docs failing after install

This is my first question, so be cool, mkay?
I have jekyll 3.3.1 installed, and jekyll-docs 3.3.0 seems to be the latest version. 'jekyll docs' fails with 'You must install the 'jekyll-docs' gem to use the 'jekyll docs' command.' I have installed jekyll-docs, so I'm not sure what the problem is. My research has indicated that jekyll and jekyll-docs need to be the same version in order to function properly.
Can anyone weigh in on this? Thank you!
SK

Getting an error with Jekyll serve

Have basically nothing but a _config.yml and index.md file, and when running jekyll serve I'm getting this:
D, [2015-07-08T10:33:29.810161 #14194] DEBUG -- : Celluloid 0.17.0 is running in BACKPORTED mode. [ http://git.io/vJf3J ]
jekyll 2.5.3 | Error: wrong number of arguments (2 for 1)
Please help!
I'm not 100% sure this is the answer for you since I wasn't using Jekyll but I had the same error when I was trying to use compass watch.
Rolling back both Celluloid and Listen did the trick for me.
I added the following to my gemfile:
gem 'listen', '<2.10.0'
gem 'compass', '<0.17.0'

Jekyll install on Windows error message

I think I'm just at the finish line for installing jekyll on windows, It's connecting fine, but I'm getting an error message:
Liquid exception: No such file or directory - python C:/Ruby193/lib/ruby/ms/1.9.1/gems/pygments.rb-0.6.3/lib/pygments/mentos.py in _posts/2015-06-09-welcome-to-jekyll.markdown<-[0m done.
Please add the following to your Gemfile to avoid polling for changes: gem 'wdm','>=0.1.0' if Gem.win_platform
I'm not sure what messages I can ignore and what I need to fix. What do you guys think?
If adding this to my gemfile is as simple as entering a cmd prompt, what do I need to enter to install it?
This was an issue that was addressed by me by another question a few days ago.This is the original question and my answer.
Basically the issue here is that you need to install Python to use Jekyll on Windows because the code highlighter Pygments is written in Python, hence requires Python to function. Pygments is alsothe default code highlighter currently. In the future versions of Jekyll will use the Rouge highlighter, which is written completely in Ruby. This issue is tracked on GitHub.
To solve your current problem, you just need to install Python 2.x, which the official linked guide from the Jekyll documentation provides very clear instructions there. You will also need to install pip. I have also included alternatives in the other SO answer I have given, so I will just provide you the link to it to reduce duplicate information and copy-paste.
Once you have Python 2.x and pip set up, and install pygments, your Jekyll install should be up and running with the site template!
Regarding the Gemfile
A summary of what a Gemfile is: A file that lists all the required Ruby gems for a particular program. For example, you wrote a ruby program that depends on 10 other gems, rather than ask the user of your new gem to go download the previous 10 gems, and then later wrestle with outdated gem issues, a Gemfile is used to keep track of what gems are needed and version. The Gemfile is used by Bundler, which is also a gem that automatically keeps track of what gems you need. In the case of Jekyll, you can use a Gemfile to dictate what you want added into your Jekyll install or removed. This is used by GitHub to keep local versions of Jekyll and other gems updated with the version used by Github Pages.
As for that notification, all you would need to do to avoid polling for changes is:
Open notepad or text editor of choice.
Add this line: gem 'wdm','>=0.1.0' if Gem.win_platform, just that line of text. You can later add gems by typing in gem 'nameOfGem in a separate line.
Save the file as Gemfile in your Jekyll site's folder. Notice that there is not .txt extension, which you can create a file with no extension in notepad by choosing 'All Files' instead of '.txt' under 'Save As'. Or, you could just edit the file extension to remove the .txt.
Install bundler by executing gem install bundler.
Run bundle install to update the gems. If you're using GitHub, add the Gemfile and the newly generated Gemfile.lock into git.

Problem deploying Rails 3 with Passenger: missing the mysql gem

I have a problem that seems very related to that in another post, but I don't understand the solution that was arrived at. I am new to Rails, and have put together a Rails 3 app. I am developing in Windows am trying to deploy it to my (shared) Redhat Linux server via git and capistrano, and using Passenger to serve the pages. The deployment process goes fine, but when I try to look at the webpage I get a Passenger error:
!!! Missing the mysql gem. Add it to your Gemfile: gem 'mysql', '2.8.1'.
In fact, I have added the corresponding line to my Gemfile, and doing a 'gem list' on the server shows that it is there.
In this post, the user helpfully noted exactly the same problem and observed that the Gemfile.lock has the gem for Windows, i.e.
mysql (2.8.1-x86-mingw32).
This is exactly the same in my Gemfile.lock, and so I imagine the same issue is happening for me; one can see that this is the gem in vendor/cache and vendor/bundle.
However, I don't understand how the proposed fix from that post is supposed to work. I can edit the mysql line in Gemfile.lock to be mysql (2.8.1), but then I get a different Passenger error that says
Can't find mysql-2.8.1 in any of the sources.
How can I fix this?
In case someone encounters the same problem, here are some things I did that made it work. I don't understand enough of what was going on to know exactly what did the trick.
First, in the Gemfile, I specified that we wanted both ruby and windows versions of the relevant gems.
gem 'sqlite3-ruby', "~> 1.2.5", :platforms => [:mswin, :ruby_18]
gem 'mysql', "2.8.1", :platforms => [:mswin, :ruby_18]
Then on the production server, after using "cap deploy", I removed the gem mysql-2.81-x86-mingw32 from both vendor/bundle and vendor/cache. My production server lets me 'gem install mysql' and 'gem install sqlite3-ruby' but puts it elsewhere in my home directory; I copied these into vendor/bundle and vendor/cache. I edited the Gemfile.lock to change the line 'mysql (2.8.1-x86-mingw32)' to 'mysql (2.8.1)'. 'bundle install' on the production server then seems to install the linux native gems (at least it says 'building native extensions').
After all this, it seems to work.
Run the command bundle install. I'm sure this will fix your issue.
Also, do not edit or move over the Gemfile.lock. Let bundler take care of that.