This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
each canvas in our environment goes through initial dev; then a testing phase; then into production usage after completing testing & peer review.
Currently the server environment has no concept of progression or promotion so we have to set up our own Dev; UAT; and Prod gallery & server - this really is very clunky because assets have to be manually copied across.
What would be more effective is:
- Allow a single asset to have a lifecycle (like you do in GIT) - so that it can go through dev and testing as a branch of the main code
- Once ready - user then changes the lifecycle type to "testing" or "UAT" and pushes it to users
- Once signed off, the user then promotes this to a production flow, and it replaces the current production version
There are a few areas where we'd need to do some thinking (dependancy tracking; branching; changing connection details as you promote so that you can hit the prod data stores etc) - but fundamentally this would go a VERY long way towards eliminating much of the admin involved in running the gallery.