aiocrafters/autoblog-python

1. This repository is a small Python command-line automation tool, not a long-running service. Its architecture is a sequence of one-off scripts that interact with Google’s OAuth 2.0 and Blogger API v3.

2. The repo has three functional entry points:

- get_blogger_token.py for initial OAuth authorization and refresh-token acquisition

- get_blog_id.py for discovering available Blogger blogs and their IDs

- publish_post.py for creating Blogger posts or drafts

3. The main external boundary is Google’s cloud APIs. The project depends on:

- Google OAuth 2.0 for user authorization

- Blogger API v3 for blog discovery and post creation

- Google account permissions tied to the user’s Blogger blog

4. Configuration is separated from code through a .env file. The runtime credentials boundary is:

- GOOGLE_CLIENT_ID

- GOOGLE_CLIENT_SECRET

- GOOGLE_REFRESH_TOKEN

- BLOGGER_BLOG_ID

This keeps secrets out of the scripts and makes the tooling account-specific.

5. The authentication flow is two-stage. First, the user runs get_blogger_token.py to perform a browser-based OAuth consent flow. That script exchanges the initial authorization for a refresh token, which is then reused for future runs without prompting the browser again.

6. get_blog_id.py is a discovery tool. It uses the authenticated Google session to call the Blogger API and list blogs associated with the account, exposing the blog title, URL, and numeric blog ID. That ID becomes a required input for publishing.

7. publish_post.py is the write path. It constructs a Blogger post from locally defined content fields such as title, body, and draft/publish mode, then sends the create-post request to the Blogger API using the selected blog ID and stored refresh token.

8. The data flow is linear and manual:

- Google Cloud OAuth client credentials are created externally

- The token script produces a refresh token

- The blog-id script discovers the target blog ID

- The publish script sends content to that blog

Each step feeds the next through .env or copied values.

9. The repository’s Python dependency layer is thin and focused on Google integration:

- google-auth, google-auth-oauthlib, and google-auth-httplib2 handle OAuth and credential refresh

- google-api-python-client talks to Blogger API v3

- python-dotenv loads .env configuration into the scripts

10. There is no database, queue, or internal API server. State is mostly externalized in Google account credentials and the .env file, with the only durable outputs being the refresh token, the blog ID, and the published Blogger posts themselves.

11. The operational boundary is local machine execution. The scripts assume a desktop-style OAuth client and a user running them manually from a Python environment, typically with a virtualenv.

12. For an architecture diagram, the key components are: local Python scripts, .env configuration, Google OAuth 2.0, and Blogger API v3. The primary arrows are from scripts to Google auth, then from authenticated scripts to Blogger API, with discovered identifiers and tokens stored back into .env for reuse.