[FOLIO-2070] Merge "alternate install" branches of folio-install into mainline Created: 05/Jun/19 Updated: 03/Jun/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Wayne Schneider | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | platform-core | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
jroot, mark.stacy, Taras Spashchenko, and others have contributed alternate install documentation for installing FOLIO on a Kubernetes cluster. The work is mostly contained in the "kube-rancher" branch of folio-install. This needs to be merged into the mainline of the branch and linked from the README for better visibility and easier collaboration. |
| Comments |
| Comment by Wayne Schneider [ 05/Jun/19 ] |
|
Thinking about this while working on merging
Questions:
I'm sure there will be other questions. |
| Comment by David Crossley [ 06/Jun/19 ] |
|
Good idea to re-arrange. It has grown. I cannot foresee any problem for the single-server stuff. |
| Comment by David Crossley [ 12/Jun/19 ] |
|
The folio-install/pull/29 moved the "single-server" document and related resources into runbooks/single-server/ Added a link to the Kubernetes information, but left it as-is at ./alternative-install/ until people are sure about its directory structure. |