Ticker-Rush is Live!

I'm excited to share that Ticker-Rush has finally hit production on March 19, 2026! It's been an intense journey of building, refining, and finally seeing it live.

Interestingly, I've managed to host the entire stack (Go backend, React frontend, Valkey, and PostgreSQL) on a single VM instance with only 2 GB of RAM. As it turns out, this is perfectly sufficient if you follow the right deployment strategies.

The 2GB Challenge

When I first started planning the deployment, I was skeptical if 2GB would be enough for a microservice-based architecture. However, by optimizing the resource distribution and using lightweight components like Valkey instead of full-blown Redis, the system remains responsive even under load.

Remote Management: Emacs to the Rescue

Managing a remote VM can sometimes feel disconnected, but I've been once again impressed by how TRAMP and vterm work when accessing the live instance via SSH with Emacs.

While it can be a bit quirky at times (like occasional connection hiccups), the combination makes handling the remote VM feel like working on my local machine.

It's a powerful reminder that these classic tools are far from obsolete.

Best Practice: Separation of Concerns

The most important takeaway from this process? Never use your production system as a build system.

Building Docker images, especially for the frontend, is extremely memory-intensive. Node.js and build tools (in this case Vite) can easily eat up all available RAM, causing the production services to swap or crash.

GitHub Actions to the Rescue

To keep the production environment lean and stable, I'm using GitHub Actions to handle the heavy lifting:

• Build: Images are built in the cloud.
• Registry: Pushed to the GitHub Container Registry (GHCR).
• Deploy: The production VM simply pulls the pre-built images and restarts the containers.

This ensures that the VM's RAM is dedicated solely to running the services, providing a smooth experience for users.

You can check out the live site now at tickerrush.com!

Roadmap & Future Improvements

While the project is live, the work is far from over. Here's what's next on the agenda:

API Documentation with Swagger

As the project enters Phase 3: AI-Driven Ecosystem, proper API documentation becomes critical. I plan to integrate Swagger to provide a clear, interactive interface for the Go backend.

Advanced Moderation & Admin Tools

Maintaining a healthy community is a priority. While I'm currently using the excellent go-away package for profanity filtering in Go, it doesn't catch everything (especially Russian profanity or clever transliterations).

To address this, I'll be implementing:

• Admin Dashboard: A set of capabilities to manually restrict or ban users who behave badly.

If you're interested in the tech stack or want to try the simulator yourself, check out the Ticker-Rush project page.