Skip to content

Latest commit

 

History

History
93 lines (69 loc) · 8.38 KB

README.md

File metadata and controls

93 lines (69 loc) · 8.38 KB

GPhotos Albums

View a list of all your Google Photos Albums all in one place. Sort by name, number of items in each, or the default sort (which is usually most recently updated first but google will not confirm)

Overview

This project has several purposes (see About for details and current status). The main one is to provide a single page where every one of your google photos albums is listed. Surprisingly this is not something google provides in their photos apps nor in the web interface. Personally I have several hundred albums and find that the ability to browse item names enables more consistency with organizing and naming of albums

The project's latest tech stack currently includes

  • Node.js 20+
  • Next.js 14 with App Router
  • React 18
  • TypeScript 5
  • AuthJS (next-auth ver 5) for Google OAuth2 authentication and authorization for Google Photos.
  • Tailwind CSS 3
  • And a lot of bells and whistles for easier VS Code development and CI/CD
    • Vercel for easy next.js deployment and testing
    • Jest — Configured for unit testing
    • ESLint — Find and fix problems in your code, also will auto sort your imports
    • Prettier — Format your code consistently
    • Husky & Lint Staged — Run scripts on your staged files before they are committed
    • Conventional Commit Lint — Make sure you & your teammates follow conventional commit
    • Github Actions — Lint your code on PR
    • and more from Next.js + Tailwind CSS + TypeScript starter and boilerplate

The original version was built using node.js, express, and passport for Google OAuth.

Using

This uses Google OAuth2 authentication (google login with email) and authorization (ask for read only access to your google photos).

Start at either

Note when logging in with google, there will be several steps. A couple of the steps are mentioned below in order to make some people more at ease with this flow.

After choosing which google account to use, you will be presented with a screenshot like the following because my website app has not been officially verifited. It is OK and safe to proceed. Must click Advanced (which changes to Hide Advanced) and then click Go to gphotos-albums.vercel.app (unsafe). google-auth-unverified-unsafe-vercel

After that, you will be notified of the permissions requested. It's all readonly, and you can click continue. Here are the permissions explanded out: google-oauth-permissions-window-vercel

Setup

Feel free to fork https://github.com/chadn/gphotos-albums/

Want to make a change? make a PR - but reach out before doing too much work

About

Goals of the Project

  • Solve my personal need to list all my google photos albums in one place
  • Experiment with Google authentication and photos API
  • Demonstrate my coding skills
    • Making this available on github.com
    • Full stack skills demonstrated - see tech stack in Overview above
    • Focus on using the latest most popular Full stack and FED tech.
  • Demonstrate how a project can migrate in stages to React.js framework
    • React.js is a powerful library and can be daunting. In my case, I wanted to show how a project can be ported to React + Next.js in stages by preserving the javascript files that did much of the heavy lifting in my original express.js. So I planned for version 1.5 that had a bit of the old code working with new code, see versions below.

More background https://chadnorwood.com/2024/04/11/google-photos-api-and-flickr/

Versions

Summary of differences between versions. See CHANGELOG.md for details.

Tech v 1.0 v 1.5 v 2.0
node.js ✅ ✅ ✅
npm ✅
express.js ✅
passport auth ✅
handsontable.js ✅ ✅
jquery.js ✅ ✅
album-details.js ✅ ✅
pnpm ✅ ✅
react ✅ ✅
next.js ✅ ✅
typescript ✅ ✅
authjs 5 beta ✅
authjs 5 release ✅
Google Photos Library API ✅ ✅
Google Photos Picker API ✅

Note authjs is still in beta and some hacks are currently in the code, to be revisited after it is out of beta. Also note photos API is changing in 2025. Version 2.0 will address these issues.