Let's talk about one of the most crucial aspects of website management that often gets overlooked: digital asset management (DAM). If you’re running into storage limits with your Git repository or noticing slower build times, it might be time to level up your asset management game with CloudCannon’s DAM integrations.
Git is great. But here’s the thing about Git repositories — they typically max out around 2GB of storage. If you’re working with lots of images, videos, or other media files, you can hit that limit pretty quickly. Plus, having all those assets in your repo can seriously slow down your builds. Not fun!
CloudCannon has made it easy to connect with various digital asset management services. Currently, we support:
What’s great about these DAM services is that they do more than just store files. Many of them can add metadata to your assets, provide advanced sorting capabilities, perform on-the-fly image transformations, or serve your assets through a CDN for better performance.
On cloudcannon.com, we use imgix, an image and video processing tool that integrates with your Amazon S3 DAM and CloudCannon. This lets us improve our build times, use the same assets across a range of sites with different Git repositories, serve optimally sized assets depending on a user's device and network connection, and keep our assets private.
Setting up a DAM with CloudCannon is pretty straightforward. Here’s the basic flow:
Now, when you add an image in CloudCannon, you can choose to upload a new image to your DAM, or explore existing images within your DAM.
Here's what it looks like to browse our DAM and add an existing image:
Want to prevent massive file uploads? You can set a maximum file size limit in bytes. For example, to cap uploads at 1GB, set it to 1,000,000,000 bytes. Your storage budget will thank you.
One of my favorite features is the ability to customize where — and how — your assets get stored. You can set up smart paths like:
paths:
dam_uploads: raw/{date|year}-{date|month}-{date|day}This organizes uploads by date automatically — super handy for keeping things tidy!
Need different asset sources for different parts of your site? You can use the allowed_sources configuration to control which DAMs (and site files) are available in specific editing interfaces. It’s great for maintaining organized workflows.
Here are some practical tips for working with DAMs in CloudCannon:
uploads_use_relative_path if you want your asset references to be relative to the content file they're used in. This can make your content more portable.Moving your assets to a DAM might seem like a big step, but it’s really worth considering if you’re approaching Git storage limits, need better asset organization, want faster build times, or require advanced asset transformation features.
CloudCannon’s integrations make the whole process pretty painless. If you haven’t tried it yet, I’d definitely recommend giving it a shot. And if you want to use a DAM provider that isn’t currently supported, don't hesitate to reach out to us — we’re always looking to expand our integrations!
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。