Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Say we want to run an actual Open edX site on a Raspberry Pi 4. The smallest plausible thing I could see working:

  • Raspberry Pi OS (64-bit) – we want arm64 for library compatibility reasons

  • Python running directly (using pyenv or some such, but not through Docker)

  • SQLite with WAL=True for the database

  • Redis, for both caching and as a celery backend

  • Port contentstore/SplitMongoKVS to use Django storages (or wait until Learning Core data models eat everything). Use local storage.

  • nginx proxy (or maybe caddy)?

    • edx-platform static assets

    • prebuilt MFE assets

Would this be feasible for Quince? Would anyone want it?

  • No labels