how does regular repo size and LFS size play together in bitbucket cloud?
The actual size of the repo should not exceed 1GB.
However, there is the LFS (1GB for a free user), where you can pay for additional 100GB+ of space reserved for "big files".
So from my understanding, if i pay for 100 GB LFS space and my regular repo size, say a unity project with comparably small files (scripts, meta files, settings...) will exceed the 1GB limit, i will still get trouble for using too much space.
Or will my overall repo size be able to grow up to the combined size of the storage i got (the regular 1GB for code/small files and whatever i got in LFS)?
// i already hinted it, i inquire because i want to set up a unity project in bitbucket cloud, and it got advertised for here:
Files uploaded to LFS only count against your LFS usage; they don't count against the repo size limit. Conversely, files uploaded to regular repo storage (that is, files that you didn't add to LFS) only count against the repo size limit; they don't count against LFS usage. The two storage pools are distinct from one another, and an overflow on one won't affect the other (for better or worse).
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs