In a previous post, we covered how to get your Jekyll blog working with Bluemix – that post was written in 2017 and if you followed the instructions now, you would find that you are unable to deploy your site since it fails. You will see an error as below on your command line.
E:\blog>cf push
Using manifest file manifest.yml
Using stack cflinuxfs2...
FAILED
Stack cflinuxfs2 not found
As it clearly tells us, this happens because the cflinuxfs2 StaticFile Buildpack that we were using then is no longer available from CloudFoundry. We need to upgrade to the cflinuxfs3 Staticfile Buildpack which seems to be almost the same but with newer versions of the dependencies.
Fortunately, the change is very small and very quick – you need to update your manifest.yml – this is what your current file looks like:
---
applications:
- name: xyz-123-blog
memory: 64M
host: xyz-123-production
path: _site/
buildpack: https://github.com/cloudfoundry/staticfile-buildpack.git
stack: cflinuxfs2Just update the last line (the ‘stack’) to use cflinuxfs3 instead so that it looks something like this:
---
applications:
- name: xyz-123-blog
memory: 64M
host: xyz-123-production
path: _site/
buildpack: https://github.com/cloudfoundry/staticfile-buildpack.git
stack: cflinuxfs3Now, we are ready to try again! Navigate to the root directory of your Jekyll site and build the site so that the output is created in _site – then, do cf push and wait for it to get done.
The first time you do this, you will notice a few things:
- The new buildpack takes a bit more time than before to show any status after the files are uploaded – be patient! This seems to be the new normal.
- You will see a warning that the Staticfile Buildpack version has changed. This is also to be expected, so there is no reason to panic. Note that this happens only the first time.
-----> Staticfile Buildpack version 1.5.3
**WARNING** buildpack version changed from 1.4.43 to 1.5.3
Most of the details from the previous post are still valid – so, you should take a look at that first.