Steps to fix deployment #2

Closed
opened 2020-03-31 12:41:47 +00:00 by decentral1se · 1 comment
Owner

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
Author
Owner

Jekyll is being unreasonably difficult to deploy...

Jekyll is being unreasonably difficult to deploy...
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: autonomic-cooperative/autonomic.zone#2
No description provided.