How to Deploy On LeapCell or else??

[Vicky-Developer28]

Portfolio Website — Rust/TopCoat Backend & Deployment Suggestions

I’m planning to build my own portfolio website to showcase:

• About me and my technical journey
• Blogs where I share my knowledge, experiments, and research
• Research papers and technical articles
• Projects built with TopCoat (Rust)

Backend Architecture

I’m planning to build the backend primarily with Rust and TopCoat, including:

• TopCoat as the web framework
• Tuasy ORM for database operations
• CRUD operations
• Tower for middleware and request handling
• My own Visitor Management plugin/library
• My own SEO Management plugin
• Admin dashboard with visitor analytics and website statistics
• Authentication and other backend services as the project evolves

The goal is to make this more than just a static portfolio — I want it to be a real-world Rust web application that I can continue expanding.

Deployment / Hosting

I’m currently considering Leapcell for deployment, but I’m not sure whether it would be the best option for this architecture.

I’d like to hear from people experienced with deploying Rust web applications:

• Is Leapcell a good choice for hosting a TopCoat-based Rust backend?
• What database would you recommend for this type of project?
• Would you recommend deploying the frontend and backend together or separately?
• Are there better alternatives to Leapcell for a Rust application?
• What would be a good production architecture for this kind of portfolio?
• Are there any important considerations for SEO, analytics, caching, security, and scalability?

I’m especially interested in simple, affordable, and reliable deployment options that are suitable for a personal project but can scale if the website grows.

Any recommendations, deployment experiences, or architecture suggestions would be greatly appreciated!

[imronreviady]

Leapcell should be fine for this. I wouldn't overcomplicate the first deployment.

Topcoat builds to a normal Rust binary, so something like cargo build --release and ./target/release/your-app should work. One thing to watch: Topcoat defaults to 127.0.0.1:3000, so on Leapcell you'll want HOST=0.0.0.0 and PORT set to the port configured for the service.

For the database I'd use Postgres, preferably managed. I wouldn't keep anything important on the app filesystem.

I also wouldn't split the frontend and backend yet. Topcoat is already server-rendered, so for a portfolio I'd keep it as one service plus Postgres. Add object storage later if you need uploads.

If the app eventually needs workers, long-running jobs, or persistent connections, that's when I'd reconsider the hosting setup. But for a portfolio/blog/admin dashboard, this is a pretty reasonable place to start.