MirrorMirror
/
riju
mirror of https://github.com/radian-software/riju.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
⚡ Extremely fast online playground for every programming language.
21 Commits 33 Branches 0 Tags 2.9 MiB
JavaScript 54.5%
Go 14.4%
Shell 10.2%
HCL 6%
Python 5.4%
Other 9.5%
Go to file
Radon Rosborough 938e41b1c6 Python can be run interactively 2020-12-25 12:19:09 -08:00
backend Python can be run interactively 2020-12-25 12:19:09 -08:00
bin Some initial progress 2020-12-17 19:04:02 -08:00
docker Get main application page rendering 2020-12-25 12:06:25 -08:00
frontend Get main application page rendering 2020-12-25 12:06:25 -08:00
langs Rearrange again, enable Docker-in-Docker-in-Docker 2020-12-24 09:35:05 -08:00
system Get main application page rendering 2020-12-25 12:06:25 -08:00
tf More Terraform updates 2020-12-22 19:41:08 -08:00
tools Import webserver and get it running 2020-12-24 21:49:26 -08:00
.dockerignore Import webserver and get it running 2020-12-24 21:49:26 -08:00
.gitignore Import webserver and get it running 2020-12-24 21:49:26 -08:00
Makefile Get main application page rendering 2020-12-25 12:06:25 -08:00
README.md Create some AWS resources 2020-12-22 15:56:21 -08:00
package.json Get main application page rendering 2020-12-25 12:06:25 -08:00
webpack.config.cjs Get main application page rendering 2020-12-25 12:06:25 -08:00
yarn.lock Get main application page rendering 2020-12-25 12:06:25 -08:00

README.md

Riju

For now, this README just has some miscellaneous notes about the build architecture that I'm planning to set up. Later, it will be converted back into a proper README.

Steps to build Riju from scratch locally:

  • Build the packaging Docker image.
  • Generate a Debian package for each language.
  • Build the runtime Docker image.
  • For each language, install its Debian package into a fresh copy of the runtime Docker image and run its tests.
  • Install every language's Debian package into a single copy of the runtime Docker image and run all the tests.

Build artifacts:

  • Packaging image
  • Runtime image
  • Debian packages
  • Application image

Steps to build Riju from cache locally:

  • To run: Pull application image.
  • To build application image: Pull runtime image and all Debian packages.
  • To build Debian packages: Pull packaging image.
  • To build runtime image: Build from scratch.
  • To build packaging image: Build from scratch.

To manipulate published artifacts we basically want to do atomic updates which keep the integration tests passing. Possible operations:

  • Rebuild packaging image: This can be done at any time.
  • Rebuild runtime image: Rebuild application image and verify integration tests are still passing. Do not rebuild any Debian packages.
  • Rebuild Debian package: Verify unit tests are passing. Rebuild application image and verify integration tests are still passing. If rebuilding multiple Debian packages, then we can run the integration tests only once. If rebuilding enough Debian packages, the probability that at least one will fail is very high. We can then trigger a more targeted update. This process could be automated.
  • CI: Rebuild packaging and runtime images if needed. Rebuild Debian packages for any changed languages. Fetch everything unchanged from registry. Rebuild application image and verify integration tests are still passing. If yes and operating on main branch, publish all artifacts and deploy.