/dev post breaks things

master
Jay 2 years ago
parent 7abc4ea34c
commit 378f203c4e

@ -0,0 +1,6 @@
---
layout: post
title: "Bad Post?"
---
For some reason I'm having issues with the last /dev post not rendering. For starters, it's actually rendering Jekyll variables WITHIN a codeblock. This seems pretty counter to the point of codeblocks. Anyway...that post might be broken if you read it. I'll look in to it.

@ -29,6 +29,7 @@ But the problem for me, as someone with little web expierence, was getting all o
So I decided to try Jekyll. I won't say it was easier; but clearly something about it clicked since I'm using it. It has a similar organization to Hugo in how it handles files; which is going to take some getting used to. I have to navigate deeper in to folders than I want to create posts. I did concede that there's no real difference between "pages" and "posts" from a functional standpoint. Wordpress treated them differently. This was a problem for doing things in Jekyll like generating post lists. The thing I really didn't want is to have to treat this like a manual site and update links in pages every time I added a non-blog related page. In fact when I first started...I had this little bash script written up: So I decided to try Jekyll. I won't say it was easier; but clearly something about it clicked since I'm using it. It has a similar organization to Hugo in how it handles files; which is going to take some getting used to. I have to navigate deeper in to folders than I want to create posts. I did concede that there's no real difference between "pages" and "posts" from a functional standpoint. Wordpress treated them differently. This was a problem for doing things in Jekyll like generating post lists. The thing I really didn't want is to have to treat this like a manual site and update links in pages every time I added a non-blog related page. In fact when I first started...I had this little bash script written up:
``` ```
#!/bin/bash #!/bin/bash
POSTS=$(find . -type f -exec stat -c '%Y %n' {} \; | sort -nr | awk 'NR==1,NR==3 {print $2}') POSTS=$(find . -type f -exec stat -c '%Y %n' {} \; | sort -nr | awk 'NR==1,NR==3 {print $2}')
echo $POSTS echo $POSTS
@ -50,6 +51,7 @@ I won't go in to the details. There were a few hours of raging at the monitor be
Now the main thing I really started to like about Jekyll was the fact I could mix HTML in my markdown. I'd tried this in Hugo and it literally yelled at me. If I wanted to do HTML snippits...there was another way I had to do them. I'm not worried about sticking to the straight markdown format; sometimes I have just snippits of code I want to use. Jekyll will let me do that. For example; the front page of this theme was originally had the display of posts as part of the theme's layout: Now the main thing I really started to like about Jekyll was the fact I could mix HTML in my markdown. I'd tried this in Hugo and it literally yelled at me. If I wanted to do HTML snippits...there was another way I had to do them. I'm not worried about sticking to the straight markdown format; sometimes I have just snippits of code I want to use. Jekyll will let me do that. For example; the front page of this theme was originally had the display of posts as part of the theme's layout:
``` ```
--- ---
layout: default layout: default
--- ---
@ -68,11 +70,13 @@ layout: default
</ul> </ul>
{%- endif -%} {%- endif -%}
``` ```
Which is cool and all; but I'm the kind of person I want my index.md to be my ENTIRE index file. I wanted more flexibility in where I put things. Where as Hugo would have complianed had I tried to put that code in a markdown file; Jekyll let me do this: Which is cool and all; but I'm the kind of person I want my index.md to be my ENTIRE index file. I wanted more flexibility in where I put things. Where as Hugo would have complianed had I tried to put that code in a markdown file; Jekyll let me do this:
``` ```
# ***Recent Posts:*** # ***Recent Posts:***
<ul> <ul>
{% for post in site.posts limit:3 %} {% for post in site.posts limit:3 %}
@ -110,10 +114,12 @@ Let me show you something that cost me two hours:
``` ```
case $- in case $- in
*i*) ;; *i*) ;;
*) return;; *) return;;
esac esac
``` ```
@ -126,6 +132,7 @@ You see...I'd been spending a lot of time updating stuff on my GIT, writing Aast
Well...this is where my .bashrc file screwed me over. Ruby, gems, and jekyll aren't installed system wide; they're installed per-user. But I have root...so it's no problem for me to sudo su git and install all the stuff. Right? Actually right. That's not the problem. The problem were my flippin paths! Well...this is where my .bashrc file screwed me over. Ruby, gems, and jekyll aren't installed system wide; they're installed per-user. But I have root...so it's no problem for me to sudo su git and install all the stuff. Right? Actually right. That's not the problem. The problem were my flippin paths!
``` ```
# Install Ruby Gems to ~/gems # Install Ruby Gems to ~/gems
export GEM_HOME="$HOME/gems" export GEM_HOME="$HOME/gems"
export PATH="$HOME/gems/bin:$PATH" export PATH="$HOME/gems/bin:$PATH"
@ -137,6 +144,7 @@ These lines specify that all of this goes under your home directory. The problem
Anyway...after moving those lines to the TOP of the file; the githook works. Anyway...after moving those lines to the TOP of the file; the githook works.
``` ```
#!/bin/bash #!/bin/bash
GIT_REPO=$HOME/[REDACTED]/pickmy-dot-org-jekyll-site.git GIT_REPO=$HOME/[REDACTED]/pickmy-dot-org-jekyll-site.git

Loading…
Cancel
Save