Gathering Interest

Make three environments—dev, test, and live—standard for RAMP hosted installations

I have always been taught that best practice for any website/application/service is to have at least three server environments: dev, test, and live. Every web host we've used in the last decade or more has provided these environments (our current host lets us spin up additional environments at will, tied to branches in our git repo, but I digress). The lack of a dev environment on RAMP has frequently caused problems, especially during version upgrades. Tessitura should encourage developers to follow best practices by including dev environments, for both the application and TNEW, on all RAMP installations. 

Jeremy Stoller

  • This has definitely been a sore spot for our organization. We needed to create an entirely different Tessitura environment with another live and test, so that we could have a dev environment. Unfortunately, this means that still not everything is available everywhere. We use the "dev" prod so we can test analytics, since this isn't available in test, while our main test environment is for TNEW and client app testing. We can't get TNEW synced in both environments, because this is not supported, so there's still no dev environment for that. The whole thing is very convoluted.