Page Comparison

Let's finally sign off the content of the single server installation for the folio docs project .

Several of us have tested this content  by now; let's collect our thoughts and prepare a final version today.

Please fork https://github.com/folio-org/docs if you haven't done so, yet.

Edit

https://github.com/folio-org/docs/blob/master/content/en/docs/Getting%20started/Installation/singleserverwithcontainers.md

in your local branch.

Create a pull request.

Open question: Should two single server documents with almost the same content been maintained? See

Discussion

• Documentation not Let's dont keep documentation in 2 different places
• DevOps team could document in folio-org/docs (instead of in folio-org/folio-install)
•  folio-org/install and folio-org/docs could are subject to diverge in the future future
• responsibilty of DevOps team ?
• documentation should be made a priority !  
• long term perspective perspective ! Will this be maintained by the documentation wg ? For how long ? By dev ops team ?
• SysOps should be a piece of the puzzle, but not the sole solely responsible group
• SysOps can make pull requests
• Marcia's site is linked better; should be the main goto in the project
• single server site needs to be linked in
• involve teach leads; not force it on a specific group

single Single server without containers

• remove from the official documentation
• but keep in git repo, "alternative installs"
• unclear if package management solution works