I recently created a site using Jekyll. And my site is up and running in github. In my local directory I have a folder called _sites. I changed the contents over there (my editing index.hmtl and other files), as per my wish.
I tried running :
jekyll --server
And I can see all my changes done in my local machine.
But when I commit and push. I couldn't able to see the changes in my site.
Am I missing something?
If you have plugins GitHub Pages will not serve your Jekyll powered site automatically.
Related
I am creating a jekyll blog using Jekyll. In the instructions I see that there is a command to build the site using the command jekyll build.
However, I noticed that when I make changes to my code/post and perform a git push origin master the content and changes are uploaded automatically. This makes me wonder why I would need to "build" the site.
Could someone help me understand what the difference is? I'm currently trying to add Google Analytics to my blog and I suspect that knowing the difference between the two will help me get it to work properly. Thanks.
to turn a Jekyll app source code into a site you view, it has to do that build step to create the HTML that is served.
Github pages automatically does the build step for you after the code is pushed (if the repo/brach is configured for Pages).
So, you are right. It is not necessary for you to run the command.
The reason you may want to run it is to run the site locally (using your computer as the server). Or if you want to deploy it to some generic static host other than Pages. Or if you want to just view the final compiled site for some reason.
There might seem to be other dupes like this, but this SO post is the closest with a hacky solution.
I got a theme that uses the tag plugin from here : http://charliepark.org/tags-in-jekyll/ Here is my site repo on github. It's hosted here : http://www.gideondsouza.com
Tags don't work online but work offline. On my local machine I see a _/site/tag/.. with folders for each tag. But this tag folder isn't generated on github? In fact I don't even see a _site folder, so maybe my understanding is off. Perhaps I need to install the github-pages gem?
I could probably fix it like in the SO post mentioned earlier, but this is hacky, I will always have to remember to copy the generated tags folder into the root.
Anything I'm missing?
Github pages only support selected plugins (see documentation here).
If you want to use your plugin, you have to generate locally and to push the _site content online.
Here are the links for the two sites and their code repositories:
Theme site
Theme GitHub repo
My site
My GitHub repo
I downloaded the theme site's repo as a ZIP file, unzipped it, then pushed it to my GitHub repo to create my site. Why are the two sites building differently? If you look at the code blocks, you can see that the HTML is being rendered differently. Does this have something to do with the Gemfile?
Notes:
This difference still exists without the _site folder that was added in the second repo.
My site, when served locally, builds the same as the theme site on GitHub Pages
Your template uses pygments for syntax highlighting https://github.com/briennakh/briennakh.github.io/blob/8d2d6479cb203e37cbc2223838b165c5cfba48cf/_config.yml#L18
However, Github Pages has switched to Rouge https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0
FWIW, they should be very compatible, Rouge emits the same output.
Looks like someone documented how they did it over here: http://idratherbewriting.com/2016/02/21/bug-with-kramdown-and-rouge-with-github-pages/
I tried to install Magento 2 on localhost using WAMP (php5.5, APACHE2.4.9 and MySQL5.6).
I added the required extension "intl" (by removing (;) in php.ini), but for some reason it didn't work - I had to copy the dll into the Apache bin folder.
I updated xdebug and had to create in php.ini an entry for xdebug.max_nesting_level = 50000;.
After all this I went to do the second phase of installation (database creation, etc...) and at the end it was successful. But upon trying to enter the Backend admin page, I get the error Page Not Found, and the Frontend was broken (no style).
So I installed the version with sample-date and the same thing happened, the only difference was the existence of the photos. I installed using the composer, and got the same error.
I think I did something wrong with the WAMP installation, but I'm not sure.
Another issue I encountered was on the themes in the installation with setup wizard: the app / design / frontend / magento folders are empty, while the github repository has two themes - why is that?
For broken styles and JS, please run php bin/magento setup:static-content:deploy. You might want to provide your specific language code as input; default is en_US
Re empty theme folder, there are several methods to deploy and install, based on your needs. The github version is meant for contributing devs, and hence there are themes present in the app/design/ folder. However, if you deployed via composer, or downloaded the zip file from magento.com, the app/design folder will be empty, since the themes are loaded via composer, from the vendor/magento folder.
I am using a vagrant machine, I have installed Jekyll and I am having trouble getting Jekyll to watch the files and refresh them, after search around I found that I needed to use the --force_polling tag which now means if I refresh the files are updated but watch does still not refresh the browser.
I can see the files being updated in my terminal window.
Cheers.
Jekyll watch will generate your static files when you make change to sources. It is not supposed to reload page in your browser.
In order to do this, you can try to use livereload. Take a look at Daniel Doezema blog for setup instructions