I wanted to check on recommendations / best approaches on the below use case -
Use case: - Assets are consumed by online external web applications. When a new asset is uploaded or an existing asset is updated, these need to be tested by staging web application first before prod applications can use them . Once approved on the staging web application, assets should be available to the production application.
Possible soln -
a) Upload assets on staging env - > point staging app to stage publish to consume assets & Prod app to prod publish.
Issue - On every approval, user has to package assets and move to prod author and publish.
Pros : No customization
Cons : Manual thing. Will take time and prone to manual error & delays.
b) Customise workflow , on approval on stage add custom replication agent to replicate to prod author & publish.
Cons: Two env to be managed(Stage & prod) - no of authors 8 for now. Stage env is not true replica of Prod so testing may not be accurate .
Pros: External applications point to the same path to digital assets although the domain will be different.
Another approach could be - to maintain two folders on prod publish itself - like stage-ready & prod ready . Point staging extrenal web app to stage ready and once approved copy asset to prod-ready folder manually or via workflow
Cons - Too many folders on 1 env and duplicate assets when seraching.
Staging application & prod application would be pointing to slightly different paths .
Pros :- all external applications (stage & prod) refer to same env so testing is thorough with CDN etc in place.