How to Manage Assets on multiple environments
Hello,
I have multiple environment like local, stage and production and all the images i upload are stored in assets folder by default. Now when i migrate the data from one environment to another the assets folder is overridden.
So i wanted to know what are the best practises of managing assets. should i use one common storage or different assists folder for each environment. if so i want to know detailed process or workflow for that.
Thank you
Environment
- Xperience by Kentico version: [30.0.1]
- .NET version: []
- Execution environment: [Private cloud (Azure/AWS/Virtual machine)]
Answers
Xperience's Continuous Deployment (CD) feature is intended to let developers promote database schema and data changes from their local environment up to production. It's not meant to synchronize marketer authored content between environments.
Sometimes content is initially authored by a developer but then ownership of that content is handed to marketers.
A set of logos or hero banners added to Xperience to demo design implementations is an example of this. Developers need the images to build their templates and Page Builder components, but after sign-off and go-live the marketing manages the images.
This kind of content can be promoted to production using Xperience's CD.
If a marketer uploads a large number of images or authors blog posts in a pre-production environment, you should not use CD to transfer these to a production environment. Instead, we currently recommend authoring content directly in production using workspaces, workflows, and web page permissions to manage content authoring.
We plan to release Content Sync in May, which is designed for marketers not developers. It will allow marketers to select content items in the Content hub (and later web pages in website channels) and sync them from a pre-production environment to production.
To answer this question, you have to login first.