Setup – Once you’re clear on the requirements and limitations, head to setup to learn how to connect your site and repository with Large Media. Requirements and limitations – Large Media changes how your Git repository works, so it’s important to review the requirements and limitations before getting started. With our image transformation service, you can serve the exact image size you need for each context, from thumbnail to retina, without having to save multiple versions or run repetitive resizing operations in your build.įind the information you need about Netlify Large Media. Uploads to our Large Media service run in parallel with the build, so both processes can run as efficiently as possible. Whether you’re cloning for local development, or our buildbot is cloning to run your build, smaller repositories mean faster clones. This saves local development time and speeds up builds in the following ways: Your designated Large Media files are uploaded directly to our media servers while Git tracks their versions with text pointer files in the repository. Netlify Large Media uses Git LFS to take advantage of the benefits of Git version tracking without bloating your repository. Git’s system of tracking diffs doesn’t work with these files, so it saves full copies of every version in your Git repository.
Storing your site content in a Git repository is great until you start adding large files that aren’t made up of text - files like images, ZIP files, and PDFs.
0 kommentar(er)
