This week, I focused on two major milestones in the CodeAtlas project: implementing GitHub authentication and setting up monitoring for the key services. While I initially considered monitoring all services, I decided to start with a more practical approach to ensure stability and observability for the most critical components.

GitHub Authentication

One of the first things I tackled was integrating GitHub authentication into CodeAtlas.

Why GitHub Auth?
GitHub OAuth allows users to securely log in using their GitHub accounts. The advantages include:

• No need for a separate username/password system

• Users authenticate via a trusted, secure platform

• Access to GitHub APIs based on scopes for advanced functionality

Learning Resource:
I followed this tutorial: GitHub OAuth Tutorial. The process is similar to Google OAuth, but the key difference here is that we don’t need to maintain the access token manually—it’s generated on-the-fly and handled securely.

Implementation Highlights:

• Configured GitHub OAuth in the application

• Defined proper scopes (e.g., read user info, repo data)

• Ensured smooth login flow and token management

This implementation lays the foundation for future features where CodeAtlas can interact with GitHub repositories directly.

Monitoring Services

The practical solution I implemented:

Instead of monitoring all services, I focused on the two main ones:

• Repo Parser – handles repository data parsing

• AI Chat Service – handles chat functionality

Tech Stack Used:

• Grafana: Dashboards and visualization

• Loki: Log aggregation

• Prometheus: Metrics collection

This setup allows me to:

• Track logs and metrics for the most critical services

• Ensure stability and observability without overcomplicating the system

For the other services, I have ideas for monitoring. I plan to try them individually first and see how they work before scaling up.

source of Monitoring

Why This Matters

By combining GitHub authentication and targeted monitoring, CodeAtlas is becoming:

• Secure – via GitHub OAuth

• Observable – critical services can be monitored

• Scalable and maintainable – easier to debug and improve

Even though I didn’t go full central monitoring this week, this approach ensures that the most important parts of the system are reliable and visible.

What’s Next

In the coming weeks, I plan to focus on:

• Expanding GitHub OAuth scopes

• Creating routes to search repositories

• Implementing new monitoring ideas for the other services

🤝 Contributions

Ideas, improvements, and suggestions are always welcome.
You’re encouraged to submit issues or pull requests to help evolve the platform.

Github repo