Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make a Dockerfile for OBOFoundry.github.io repo #557

Open
cmungall opened this issue Mar 13, 2018 · 6 comments · May be fixed by #1805
Open

Make a Dockerfile for OBOFoundry.github.io repo #557

cmungall opened this issue Mar 13, 2018 · 6 comments · May be fixed by #1805
Labels
attn: Technical WG Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools quality checks Issues related to global quality control (i.e., not specific to a particular ontology)

Comments

@cmungall
Copy link
Contributor

This will allow a wider range of the people the ability to

  • regenerate derived files using the Makefile (current reqs: python, jena)
  • run various reports in the makefile - e.g. sparql consistency (current reqs: python, SPARQLWrapper)
  • run jekyll locally to test website changes (current reqs: ruby, jekyll)

It will also make it easier to auto-run the generation of derived files if we go that route

Note: do not confuse with ticket for Dockerizing PURL infrastructure OBOFoundry/purl.obolibrary.org#415
@cmungall cmungall self-assigned this Mar 13, 2018
@cmungall cmungall mentioned this issue Dec 4, 2018
Closed
@nlharris nlharris added attn: Technical WG Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools quality checks Issues related to global quality control (i.e., not specific to a particular ontology) labels Mar 23, 2020
@nlharris
Copy link
Contributor

If this is still needed, can it be assigned to someone other than @cmungall?

@nlharris
Copy link
Contributor

is this something @jamesaoverton or @wdduncan might be able to do?

@jamesaoverton
Copy link
Member

I consider this just a "nice to have" feature. My team is not going to implement it. If Chris' team is not going to implement it, then this issue should be closed.

@jamesaoverton jamesaoverton mentioned this issue Aug 16, 2021
Closed
@matentzn matentzn linked a pull request Feb 18, 2022 that will close this issue
Draft
@nlharris
Copy link
Contributor

Looks like this can be closed when #1805 is finished and merged.

@nlharris
Copy link
Contributor

#1805 is still draft

@nlharris
Copy link
Contributor

another almost 2 years later, #1805 remains draft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
attn: Technical WG Issues pertinent to technical activities, such as maintenance of website, PURLs, and tools quality checks Issues related to global quality control (i.e., not specific to a particular ontology)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Draft docker deploy for OBO site OBOFoundry/OBOFoundry.github.io
3 participants
@cmungall @jamesaoverton @nlharris