You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the early stages of our website development there was no need for separate hosting for binary static assets (paper PDFs, zipped archives, etc.). However, as time went by, the size of the repository grew significantly. Publishing/cloning process is quite slow and painful as well.
Unfortunately, git-lfs is not supported by Github Pages. In order to remedy repository growth, we should consider storing our binary static assets on a separate server (S3 bucket, Azure machine, etc.) and point a subdomain to this machine.
The uploading of said assets also has to require minimal manual intervention from user side (preferably, it has to happen during make publish run).
The text was updated successfully, but these errors were encountered:
In the early stages of our website development there was no need for separate hosting for binary static assets (paper PDFs, zipped archives, etc.). However, as time went by, the size of the repository grew significantly. Publishing/cloning process is quite slow and painful as well.
Unfortunately,
git-lfs
is not supported by Github Pages. In order to remedy repository growth, we should consider storing our binary static assets on a separate server (S3 bucket, Azure machine, etc.) and point a subdomain to this machine.The uploading of said assets also has to require minimal manual intervention from user side (preferably, it has to happen during
make publish
run).The text was updated successfully, but these errors were encountered: