[
https://issues.apache.org/jira/browse/DAFFODIL-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2595.
-----------------------------------
Verified the specified commit (commit 456ee18b44ea3ef76a97425c59310e0f42889503)
is included in the latest pull from the daffodil-site repository.
Verified changes identified in commit comment were implemented.
Installed podman and docker onto test machine.
- Verified using podman command from daffodil-site README.md file that a
podman container is created and running.
- Verified the podman container contained the daffodil-site by using the
http://localhost:4000 in firefox to browse.
- Verified using docker command from daffodil-site README.md file that a
docker container is created and running.
- Verified the docker container contained the daffodil-site by using the
http://localhost:4000 in firefox to browse.
> Create podman/docker container for maintaining daffodil-site
> ------------------------------------------------------------
>
> Key: DAFFODIL-2595
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2595
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Mike Beckerle
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 3.3.0
>
>
> It takes hours to get ruby, rubygems, jekyll, etc. all working again when you
> haven't used it in a while.
> Many people use this infrastructure only for maintaining the daffodil-site
> content, which only changes occasionally.
> Various platform upgrades and security updates on a developer workstations
> break this stuff.
> A podman/docker container with a known good configuration of these ruby and
> jekyll tools would massively smooth the release process.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
