jade-site

Jade Systems Inc web site.

Development

This is the third and a half implementation of the modern site, in Jekyll. We now prefer to use Docker in development for the Jekyll part.

With Docker, use my Rails app and the included compose.yml file:

docker compose up -d
docker compose exec jekyll foreman start

To see draft blog posts, too:

docker compose up -d
docker compose exec jekyll foreman -f Procfile.drafts start

I used to use a standard Docker Jekyll container:

JEKYLL_VERSION=4.2.2 # Or whichever version you want
docker run --rm -p 4000:4000 --volume="$PWD:/srv/jekyll" --name jekyll jekyll/jekyll:$JEKYLL_VERSION jekyll serve

But that doesn't seem to work very well anymore.

If you're doing Jekyll upgrades or anything else that requires experimenting with new gems, you may find it more convenient to start a shell in the container and run jekyll serve from there. This lets you quit the server and install or remove the gems you want, without restarting the container, which has to re-install all the gems.

Even with a minimal set of gems, bundle install from scratch for jekyll takes enough time to be annoying.

Deploy

With FileZilla, copy the contents of _site to the destination.

HostPapa does SFTP, but I'm not sure we can securely script it:

sftp -rC -o "PreferredAuthentications=password" $SITE_USERNAME@ftp.$SITE_DOMAIN
put -P _site/* public_html
exit

To deploy to a location that accepts rsync (not HostPapa):

rsync -r _site/ $SITE_USERNAME@$SITE_DOMAIN:/var/www/$SITE_DOMAIN/html

(May need a more privileged user, or have rsync log you in as the user who owns the html directory.)

This will change soon

Need jekyll-assets gem. It's quite confusing what I'm actually going to get with it, but the basics seems to imply a Sprockets-based asset pipeline, which is attractive, because I can then simply include the boostrap-rubygem. [Yes. I just had to use bootstrap-rubygem.]

I made an assets/css folder and put the application.scss in it. It got built, but not included because it was built to the new location. Had to specify the sass_dir to be assets/css in _config.yml and put all the SASS files in assets/css.

Once I had that figured out, I just removed the link to Bootstrap from the CDN, and added @import "bootstrap"; to the end of application.scss. It took a few heartbeats to compile, but then everything was fine.

Oops. It looks like I should have put the source SASS in _assets.

Okay. Now on to Javascript. Using the Rails gem (jquery-rails) didn't seem to work, but simply copying the jquery-3.1.1.js file into the _assets/js directory and changing its name to jquery3 seems to have worked. (I could have also changed the file name in application.js instead).

This won't change. Historical info

Using the importer to get all the blog posts from blogger was pleasantly easy. Figuring out how to show them in anything other than a long list is still an unsolved problem. The jekyll-archives gem solves some of the problem, but it didn't seem to really be what I wanted, so I dropped it for now. The Jekyll documentation shows a variety of examples of various approaches. This may be one of those problems that are general enough that a gem or plug-in isn't a useful approach.

Historical Development Notes

• January, 2021, removed the search coffescript.