How do you not overwhelm the user with a wall of content? When thinking about user experience, this question often comes to mind as we d...
UI/UX frontend SEOIf your idea of accessibility is making sure your site hits a specific WCAG score, you’re probably leaving out some users. Maybe accessib...
Accessibility UI/UX frontendAbout a year ago, RIMDev started a DevOps transformation. As part of that transformation, we started to use slots in Azure app services, ...
devops rimbot chatopsOver the previous year we’ve been working to improve our overall uptime. While we aren’t prepared to offer 99.999% availability in the wa...
Azure DevOpsOur starting point This past year we’ve been on a DevOps journey. While we haven’t been in a state of stagnation or chaos as a team, we’...
Azure DevOps TerraformOur team maintains a private package that contains our strategy for database migrations. It runs migrations using FluentMigrator as well ...
.NETASP.NET Core continues to improve on the legacy of the .NET Framework. Our team is impressed with its performance and excited about futur...
.NET ASP.NET Core CoreWe use Microsoft Azure Application Insights in our web applications. It logs tons of useful data about our applications, including web re...
.NETHere at RIMdev, we are unapologetic about our love for static websites. Folks, static sites are the future! That said, there are times we...
asp.net core staticWe use Microsoft Azure Application Insights in our web applications. It logs tons of useful data about our applications, including web re...
.NETURLs are the bridges that connect our little island of a website to the bigger continent known as the Internet. Preserving URL integrity ...
IIS Azure SEOWe are in the process of deprecating many smaller subdomain app services and serving the same content through our flagship site. This pos...
Windows AzureIf you build .NET Core apps on your Mac and install https certificates to your keychain for development purposes, it’s helpful to know th...
Keychain MacOS CertificatesStandard Polyfills for Front End Getting your JavaScript applications working across all browsers is challenging. If you are writing you...
JavaScript Webpack PolyfillsStatic site hosting is straightforward, and from our experience, less likely to have errors compared to a more dynamic site. While dynami...
Azure StaticSeveral months ago, Bill Boga and I, realized there was a performance enhancement we could make in our infrastructure. We were utilizing ...
.NET PerformanceThis post covers augmenting an authenticated User for use in middleware or when using the [Authorize]-attribute in an MVC-controller. The...
ASP.NET Core IdentitySever AuthenticationIf you’re like me, you aspire to write clean and consistent scss. We use the power of scss for everything from nesting our selectors, cre...
SASSFeature flags can be useful for changing the runtime behavior of an application with minimal impact. Having a UI to toggle the feature fl...
.NET asp.net coreIn order to avoid having large files in our Git history we’ve been using Git Large File Storage (LFS). It commits a marker in the Git repository and uploads files to a separate place.
On GitHub the billing for Git LFS is based on storage and bandwidth. While significant bandwidth can be used by each contributor pulling down all the files locally we’ve found a significant bandwidth contributor: Continuous Integration Builds Agents. Using AppVeyor to run out builds means each build is a full clone, which includes downloading all of the Git LFS assets needed to build the application. And, without any caching on the build server this is a full download of all necessary Git LFS assets for each build.
Here’s what you need in terms of AppVeyor configuration. This script could be adapted for services other than AppVeyor.
image: Visual Studio 2017
cache:
- .git\lfs\objects
clone_script: echo Skip AppVeyor Clone
install:
# Adapted from https://help.appveyor.com/discussions/problems/6274-git-lfs-and-build-cache#comment_43676282
- git init %APPVEYOR_BUILD_FOLDER%
- cd %APPVEYOR_BUILD_FOLDER%
- git remote add origin [email protected]:%APPVEYOR_REPO_NAME%.git # Updated to use SSH
- git fetch -q origin %APPVEYOR_REPO_COMMIT%
- git checkout -qf %APPVEYOR_REPO_COMMIT%
before_build:
- ps: git lfs prune | Out-Null
build_script:
- ps: ./build.ps1
test: off
AppVeyor typically handles the cloning of the repository for you. In this case, we want to remove that functionality by overriding the clone_script and taking care of it ourselves.
This was adapted from https://help.appveyor.com/discussions/problems/6274-git-lfs-and-build-cache#comment_43676282, so thanks to trevor.sandy for something to work from.
I hope this helps you reduce your GitHub bills!
