Introducing AUTONET - A Rust CLI That Finds the Right Local IP for Your Development Server

phravins — Sat, 31 Oct 2026 10:16:17 +0000

Ever switched between office Wi-Fi, home Wi-Fi, Ethernet, or a mobile hotspot and had to update your development server's IP address again?

That's the problem I'm trying to solve with AUTONET, an open-source, cross-platform networking tool built in Rust.

The Problem

When developing web or mobile applications, your machine can have multiple IP addresses from Wi-Fi, Ethernet, Docker, virtual machines, and VPNs.

Finding the correct address to access your local development server from another device can become frustrating.

For example, your application might be running on localhost:3000, but you want to test it from your phone.

Which IP address should you use?

What AUTONET Does

AUTONET inspects your machine's network interfaces and routing information to select a suitable IP address for local development.

Some of its capabilities include:

Automatic IP selection — Finds a suitable local network address.
Network change detection — Monitors changes between Wi-Fi, Ethernet, and other interfaces.
Docker and VPN awareness — Avoids selecting unsuitable virtual network addresses by default.
Developer integration — Provides environment variables for development applications.
Local hostname discovery — Supports .local hostname advertisement using mDNS.
QR code generation — Makes it easier to open development applications on mobile devices.
Network diagnostics — Helps identify potential connectivity problems.

Built with Rust

AUTONET uses a modular Rust architecture with separate components for network discovery, address selection, and CLI operations.

It uses native operating-system networking APIs to inspect interfaces and routes.

Linux support is implemented, while macOS and Windows implementations still need real-hardware validation.

Still Evolving

The project is open-source and under active development.

I'm particularly interested in feedback and contributions around:

Testing across Linux, macOS, and Windows
Network switching and connectivity edge cases
Improving address selection and diagnostics
Documentation and developer experience

If you're interested in Rust, networking, operating systems, or developer tools, feel free to explore the repository.

GitHub: https://github.com/phravins/AUTONET

I'd love to hear your thoughts on the approach.

How do you currently handle changing local IP addresses when testing applications across multiple devices?

Feedback, issues, and pull requests are always welcome!

QuantumBilling An Open-Source GST Billing Application Built with Elixir and Phoenix LiveView

phravins — Sat, 31 Oct 2026 10:04:16 +0000

Hi everyone!

I've been working on QuantumBilling, an open-source GST billing application designed for small and growing businesses in India.

The idea behind the project is to simplify everyday invoicing, billing, and GST-related workflows while exploring how Elixir and Phoenix can be used to build practical business applications.

What QuantumBilling includes

GST invoicing — CGST, SGST, and IGST calculations

Customer management — Manage clients and their billing information

Invoice customization — Customizable templates and PDF generation

Recurring billing — Automated recurring invoice workflows

Payments — UPI QR codes and Razorpay payment links

E-invoicing and E-Way Bills — Integration workflows for Indian GST requirements

Multi-business support — Separate PostgreSQL schemas for individual businesses

Reports and reminders — Billing reports and GST compliance reminders

Tech Stack

Elixir — Application and business logic

Phoenix LiveView — Interactive, real-time user interfaces

PostgreSQL + Ecto — Database and multi-business data management

Oban — Background jobs, scheduled tasks, and recurring workflows

One of the interesting technical challenges has been implementing multi-business architecture using separate PostgreSQL schemas while keeping user accounts and business memberships shared.

The project also uses Phoenix PubSub for real-time updates and Oban for background processing.

Current Status

QuantumBilling is still under active development. The core billing workflows are being developed and improved, while some external integrations currently use sandbox or simulated behavior.

There's still plenty of room for improvements in architecture, UI/UX, testing, documentation, and functionality.

Open to Community Contributions

I'm sharing this project here because I'd love to hear feedback from the Elixir community.

If something in the architecture could be improved, you've encountered similar challenges, or you have suggestions for making the application better, I'd be happy to discuss them.

The repository is public, and contributions through issues and pull requests are welcome.

GitHub Repository:

https://github.com/phravins/QuantumBilling

I'm particularly interested in hearing how others approach multi-tenant applications, background job processing, and complex business workflows using Elixir and Phoenix LiveView.