kentcio12 mvc development with media library

When developing an MVC application with Kentico, you should always have web farms enabled: https://docs.kentico.com/k12/configuring-kentico/setting-up-web-farms. Web farms ensure that several things are kept "synchronized" between the two environments, mainly cache and physical files (media, attachments, etc).

With web farms configured properly, when you upload a media file to the Kentico project it will automatically be added to the MVC project as well. You can then use our API to generate links to the media file: https://docs.kentico.com/k12/developing-websites/retrieving-content-in-mvc-applications/displaying-content-from-media-libraries.

If you are using page attachments, these are generally stored in the database so you don't need to worry about transferring the files- just use our API to display them. If you store attachments on the disk, web farms will still synchronize them.

Thanks for the reply. One more questions is that we should keep media library in front-end MVC project if we want to put admin interface CMS project behind firewall ?

By default, content of media libraries is synchronized via web farms and duplicated in the project directories of both the admin interface and MVC application. Therefore you should ensure that firewall settings would not prevent both projects from having access to each other.

Thanks for the response. According to your recommendation, we will keep media files in admin interface project but just want to clarify that in dancing goat MVC project, when we upload images via mvc widget , the images have been kept in front-end MVC project only. Can you please explain me about that as well?

We are middle of developing a custom mvc widget with a custom image upload-er control and need to decide it quickly whether we should keep in it admin interface or not. Thanks.