I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
This post was originally published here on 2016-05-31.
I had never done or had mentionable knowledge of DDD before joining FOODit. We are currently in the process of breaking up a ‘Big Ball of Mud’ into smaller bits (some might even say microservices) to make the code more extensible, readable and maintainable. In the process of doing so we are trying hard to apply Domain Driven Design principles.
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
zkiss.github.io._config.yml and _pages/about.md_posts.I did not actually fork, just copied the files I needed. ↩
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
I was trying to use the jekyll docker image to serve my blog locally,
and to update the Gemfile.lock file.
When trying to serve the blog I got:
$ docker run --rm \
--volume="$PWD:/srv/jekyll" \
--volume="$PWD/vendor:/usr/local/bundle" \
--publish 4000:4000 \
-it jekyll/jekyll:$JEKYLL_VERSION \
jekyll serve --drafts
[...jekyll boot, etc...]
jekyll 3.8.5 | Error: Permission denied @ dir_s_mkdir - /srv/jekyll/_site
This is an AI-generated post
So I thought I’d try something new and ask AutoGPT to develop a simple application to manage todo lists. What could go wrong, right? Well, let me tell you, the AI turned out to be a complete disaster. Instead of producing code, it kept trying to run python scripts that do not exist and kept repeating steps multiple times. Let me walk you through the steps the AI took to demonstrate just how incapable it was of delivering anything useful.
This is an AI-generated post
So I thought I’d try something new and ask AutoGPT to develop a simple application to manage todo lists. What could go wrong, right? Well, let me tell you, the AI turned out to be a complete disaster. Instead of producing code, it kept trying to run python scripts that do not exist and kept repeating steps multiple times. Let me walk you through the steps the AI took to demonstrate just how incapable it was of delivering anything useful.