https://github.com/alwaysblank/photos.alwaysblank.dev

Pictures I done took.
https://github.com/alwaysblank/photos.alwaysblank.dev

Last synced: 10 months ago
JSON representation

Pictures I done took.

• Host: GitHub
• URL: https://github.com/alwaysblank/photos.alwaysblank.dev
• Owner: alwaysblank
• Created: 2019-10-09T15:01:36.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2023-03-02T04:46:21.000Z (over 3 years ago)
• Last Synced: 2025-02-23T08:31:57.523Z (over 1 year ago)
• Language: CSS
• Homepage: https://photos.alwaysblank.org
• Size: 1.25 MB
• Stars: 3
• Watchers: 2
• Forks: 0
• Open Issues: 15
• Metadata Files:
  • Readme: README.adoc

Awesome Lists containing this project

README

          
= Photos

A site for my photos!

[link=https://app.netlify.com/sites/photos-alwaysblank/deploys]

image::https://api.netlify.com/api/v1/badges/09011dd3-9f9d-4f24-b183-9e77764ba437/deploy-status[]

== How's It Work?

Each roll defines an `album`, which is the path to a folder on my Cloudinary account.

When a build is run (only locally, currently) the script checks to see if a file containing data for that album exist; if it does, then it builds the site from that. 

If it doesn't, it pulls the necessary info from Cloudinary via the Admin API, saves it to a file, and then builds the site.

It does this for faster builds on old rolls, but also to keep from hitting the API a ton--the Admin API is rate-limited to around 500 calls an hour.

[WARNING]

====

Remember to create a `.env` file with your Cloudinary env var in it!

Otherwise you'll get a lot of mysterious errors.

====

== TODO

. Figure out a way to run builds on push and generate non-existant data files. Possible GitHub Actions implementation?

. Fill out content a bit (i.e. some more copy, license info, etc).