As someone who has had to install the Ruby / Gem / Jekyll stack quite a few times in the past, I know the pain. There were always things that did not quite work out, and they caused hours of looking up cryptic messages in the Internet. Putting everything into a Docker image will guarantee consistency across setups and no need to always set up multiple versions. Just pull the Docker image and create a container that runs your build. There will no longer be version conflicts or consistency issues, due to the isolation at the container level.
I agree with everything you said Preslav. Discovering that the whole process could be consistent and more predictable was a powerful realization. Hopefully this makes barrier to entry a lot lower as well. I know the first time I tried to get Jekyll running on my machine. It felt so foreign to me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As someone who has had to install the Ruby / Gem / Jekyll stack quite a few times in the past, I know the pain. There were always things that did not quite work out, and they caused hours of looking up cryptic messages in the Internet. Putting everything into a Docker image will guarantee consistency across setups and no need to always set up multiple versions. Just pull the Docker image and create a container that runs your build. There will no longer be version conflicts or consistency issues, due to the isolation at the container level.
I agree with everything you said Preslav. Discovering that the whole process could be consistent and more predictable was a powerful realization. Hopefully this makes barrier to entry a lot lower as well. I know the first time I tried to get Jekyll running on my machine. It felt so foreign to me.