The hosted platforms (jambonz.us and jambonz.xyz) have always used a different webapp, which was initially forked from jambonz-webapp. Now that the jambonz-webapp repo has been completely rewritten the hosted version is way behind and for that reason it is not possible to update the hosted platforms to the latest release.
Rather than update that older hosted repo, we should incorporate the differences into this repo to create a unified repo that can be run on a self-hosted jambonz, as it is today, but can also be deployed on a hosted jambonz system, like those mentioned above.
The main difference back when the split occurred was that jambonz-webapp did not support multiple users, which of course was needed for the hosted platform. Now we do. There are other differences as well -- the signup/register and stripe integration for instance that are only needed on the hosted platform.
So we need to create a branch in the jambonz-webapp repo here to start the work of integrating the features needed to run eventually on an updated jambonz.us and jambonz.xyz. These changes should of course be hidden behind a feature flag / env vars so that the default deployment is the current self-hosted model, but that it can also with those settings be deployed on the public server where people can sign up for accounts, start a free trial, upgrade to paid, etc etc.
The hosted platforms (jambonz.us and jambonz.xyz) have always used a different webapp, which was initially forked from jambonz-webapp. Now that the jambonz-webapp repo has been completely rewritten the hosted version is way behind and for that reason it is not possible to update the hosted platforms to the latest release.
Rather than update that older hosted repo, we should incorporate the differences into this repo to create a unified repo that can be run on a self-hosted jambonz, as it is today, but can also be deployed on a hosted jambonz system, like those mentioned above.
The main difference back when the split occurred was that jambonz-webapp did not support multiple users, which of course was needed for the hosted platform. Now we do. There are other differences as well -- the signup/register and stripe integration for instance that are only needed on the hosted platform.
So we need to create a branch in the jambonz-webapp repo here to start the work of integrating the features needed to run eventually on an updated jambonz.us and jambonz.xyz. These changes should of course be hidden behind a feature flag / env vars so that the default deployment is the current self-hosted model, but that it can also with those settings be deployed on the public server where people can sign up for accounts, start a free trial, upgrade to paid, etc etc.