|
| 1 | +Runestone MonoRepo |
| 2 | +================== |
| 3 | + |
| 4 | +This repository collects together the various repositories related to |
| 5 | +the Runestone Academy software. The idea of combining several |
| 6 | +repositories into a single structure was motivated and inspired by the |
| 7 | +Python polylith tools and projects. |
| 8 | + |
| 9 | +As Runestone has grown over the years we have accreted a loads of new |
| 10 | +functionality without ever stopping to reconsider an architecture that |
| 11 | +would support easier implementation of new features while providing |
| 12 | +stability for fundamental parts of the project that need to scale. |
| 13 | +Docker was not invented at the time Runestone development started! |
| 14 | + |
| 15 | +The goal of this re-working of the Runestone code will provide us with a |
| 16 | +very docker friendly set of servers and services. we will use a polylith |
| 17 | +software architecture to develop and maintain this set of services. The |
| 18 | +following diagram shows what we are aiming at. |
| 19 | + |
| 20 | +.. image:: ../images/RunestoneArch.svg |
| 21 | + |
| 22 | +Each of the servers in the diagram above will become a project in this |
| 23 | +repo. |
| 24 | + |
| 25 | +- Each project is runnable from the top level |
| 26 | +- Each project builds its own docker image |
| 27 | +- The entire suite of services is orchestrated by the |
| 28 | + ``docker-compose.yml`` file |
| 29 | + |
| 30 | +Understanding the Code Structure |
| 31 | +-------------------------------- |
| 32 | + |
| 33 | +- projects - define the artifacts - Docker images or applications could |
| 34 | + be a web application or a command line application or whatever. |
| 35 | + |
| 36 | +- bases - contains the public facing API for a project |
| 37 | + |
| 38 | +- components - contains code that supports one or more projects/bases |
| 39 | + |
| 40 | +- development - experimental and early work. |
| 41 | + |
| 42 | +A Roadmap |
| 43 | +--------- |
| 44 | + |
| 45 | +Docs |
| 46 | +---- |
| 47 | + |
| 48 | +This setup uses poetry and two important plugins, the multi-project |
| 49 | +plugin and the polylith plugin. |
| 50 | + |
| 51 | +The official Polylith documentation: `high-level |
| 52 | +documentation <https://polylith.gitbook.io/polylith>`__ |
| 53 | + |
| 54 | +A Python implementation of the Polylith tool: |
| 55 | +`python-polylith <https://github.com/DavidVujic/python-polylith>`__ |
0 commit comments