First check that jekyll can be reached using localhost:4000 in the container just by doing a docker run -p 4000:4000 decentral1se/jekyll and things are working. Then the deployment can take care of the HTTPS certificates issue and debugging can go on...
For that to work, I need to:
Thread vars required in sbin/entrypoint.sh via pre-deploy.yml
Mount a directory with the certificates into the container in post-deploy
First check that jekyll can be reached using localhost:4000 in the container just by doing a `docker run -p 4000:4000 decentral1se/jekyll` and things are working. Then the deployment can take care of the HTTPS certificates issue and debugging can go on...
For that to work, I need to:
* Thread vars required in sbin/entrypoint.sh via pre-deploy.yml
* Mount a directory with the certificates into the container in post-deploy
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
First check that jekyll can be reached using localhost:4000 in the container just by doing a
docker run -p 4000:4000 decentral1se/jekylland things are working. Then the deployment can take care of the HTTPS certificates issue and debugging can go on...For that to work, I need to:
Jekyll is being unreasonably difficult to deploy...