Reduce the dependencies to only use actual dependencies about type-theme

[coltenkrauter]

I will note that I am not using jekyll serve in order to serve the site - I am using nginx in a docker container. So you may need a few more dependencies than I listed, but I noticed several other unnecessary themes were being installed. It is probably best to list the dependencies explicitly. 😃

[rohanchandra]

Thanks for bringing this up.

For development purposes, I'd prefer to keep my environment in sync with GitHub Pages, since this is where this theme is mostly used.

Context: I started looking into reducing the dependencies that are installed because I was tired of waiting for lengthy builds to complete.

Have you considered creating your own Docker image, which you can upload or build using a service like Docker Hub, with the dependencies pre-installed?

[coltenkrauter]

Certainly - I appreciate your speedy response.
I completely understand where you are coming from.

Have you considered creating your own Docker image, which you can upload or build using a service like Docker Hub, with the dependencies pre-installed?

A similar solution has crossed my mind. I plan on investigating a solution like that at some point, but my initial research makes me think it will be somewhat complex.

I sort of wish that the Jekyll build step (or bundle install) could be broken into two steps, 1 for installing dependencies and one for rendering the Jekyll site (templates and stuff) because then I could take advantage of docker caching. I do think this is possible, but again, my limited knowledge of Jekyll makes it seem complex.

[rohanchandra]

A similar solution has crossed my mind. I plan on investigating a solution like that at some point, but my initial research makes me think it will be somewhat complex.

Have a look at using a Dockerfile, it's likely only a couple lines of configuration to set-up (examples).

If you're using Docker Hub, you can also set it to automatically build and upload the image for you whenever you push to the repo with the Dockerfile.

I sort of wish that the Jekyll build step (or bundle install) could be broken into two steps, 1 for installing dependencies and one for rendering the Jekyll site (templates and stuff) because then I could take advantage of docker caching. I do think this is possible, but again, my limited knowledge of Jekyll makes it seem complex.

Does bundle install then jekyll build not work?

[coltenkrauter]

I appreciate the suggestion with Dockerhub - I actually have a private registry set up so I may do something like that...

Does bundle install then jekyll build not work?

I hadn't tried that.... it totally works! Thank you for the suggestion!
My builds were 50+ seconds. Now they are less than 30 seconds thanks to docker caching (of course the very first build takes a little longer) - I am very happy with that. 🎉

This is my current Dockerfile,

# Stage 1
FROM jekyll/jekyll as jekyll

WORKDIR /app

COPY Gemfile .

RUN chown -R jekyll:jekyll /app

RUN bundle install

COPY . .

RUN chown -R jekyll:jekyll /app

RUN jekyll build --trace

# Stage 2
FROM nginx

COPY --from=jekyll /app/_site /usr/share/nginx/html
COPY ./nginx.conf /etc/nginx/conf.d/default.conf

EXPOSE 80

[rohanchandra]

Great! Glad to hear that worked.