Well done, Chandresh.
Hope you don't mind, i forked your Inertia project and used it for dogfooding trongate.cloud - https://trongate-inertia-2.trongate.dev/demo :)
8 days ago
#21
8 days ago
#22
Hey sasin91 — first off, no problem at all, I'm genuinely glad you forked it and I really appreciate you dogfooding it on trongate.cloud. That's actually the best kind of feedback a project like this can get at this stage 🙏
Just a heads-up though, there are a couple of major bugs still in there that need fixing before anything production-grade: the infinite scroll and the clear history props both have issues. So if you're not relying on those two features, you can absolutely use it without any security concerns — but I want to be upfront that the Inertia adapter itself is still very much in development, so please tread carefully if you're pushing it further.
On that note — DC, thanks for the offer about having Grady submit a pull request, but no need for it 🙂 Grady already solved the problem in his previous reply (the slowness on the Inertia frontend was being caused by usleep()), so that's sorted. Please pass on my thanks to him — really appreciate him digging into it.
And while I've got you both here: once the Inertia adapter is complete and free of bugs and security issues, would either of you — DC or Grady — be open to making it an official starter kit for Trongate? I think it'd be a genuinely valuable addition to the ecosystem, and I'd love to see it get that kind of backing once it's ready.
Thanks again both — really appreciate the support on this one.
Just a heads-up though, there are a couple of major bugs still in there that need fixing before anything production-grade: the infinite scroll and the clear history props both have issues. So if you're not relying on those two features, you can absolutely use it without any security concerns — but I want to be upfront that the Inertia adapter itself is still very much in development, so please tread carefully if you're pushing it further.
On that note — DC, thanks for the offer about having Grady submit a pull request, but no need for it 🙂 Grady already solved the problem in his previous reply (the slowness on the Inertia frontend was being caused by usleep()), so that's sorted. Please pass on my thanks to him — really appreciate him digging into it.
And while I've got you both here: once the Inertia adapter is complete and free of bugs and security issues, would either of you — DC or Grady — be open to making it an official starter kit for Trongate? I think it'd be a genuinely valuable addition to the ecosystem, and I'd love to see it get that kind of backing once it's ready.
Thanks again both — really appreciate the support on this one.
8 days ago
#23
Happy to see, that's fine, I just want to prove it's a breeze to deploy any variant of trongate (v2 primarily) but will keep an eye on it. :)
8 days ago
#24
Hi Chandresh,
First up, well done. Getting a working adapter together in a week is no small achievement, and it sounds like you're getting closer to what you need.
On the question of an official starter kit, though, I'll be straight with you. Speaking for myself, not for DC or the community, I don't see it happening, nor do I think it should.
You needed an Inertia.js connector for an existing React front end, with Laravel behind it that you wanted to replace. That's a migration problem rather than a gap in Trongate. Between MX, server-rendered views and the code generator, the framework already has ways to build dynamic interfaces. Inertia doesn't fill a capability gap in Trongate. It provides a bridge for people in your particular situation.
There's also a bigger picture here. Trongate has zero dependencies, no Composer and nothing bolted on. It stands on its own rather than being tied to someone else's roadmap. An official kit would mean the framework's own recommendation depended on React, Node, Vite and a protocol maintained elsewhere. It would also potentially leave DC chasing Inertia's next version, immediately after committing to no major upgrades for a year.
So, keep building it. Once it's ready, document the migration. I reckon the more valuable contribution would be sharing your journey of replacing Laravel with Trongate, especially if you take up DC's suggestion to turn it into a video. That would give others something practical to learn from.
Cheers!
First up, well done. Getting a working adapter together in a week is no small achievement, and it sounds like you're getting closer to what you need.
On the question of an official starter kit, though, I'll be straight with you. Speaking for myself, not for DC or the community, I don't see it happening, nor do I think it should.
You needed an Inertia.js connector for an existing React front end, with Laravel behind it that you wanted to replace. That's a migration problem rather than a gap in Trongate. Between MX, server-rendered views and the code generator, the framework already has ways to build dynamic interfaces. Inertia doesn't fill a capability gap in Trongate. It provides a bridge for people in your particular situation.
There's also a bigger picture here. Trongate has zero dependencies, no Composer and nothing bolted on. It stands on its own rather than being tied to someone else's roadmap. An official kit would mean the framework's own recommendation depended on React, Node, Vite and a protocol maintained elsewhere. It would also potentially leave DC chasing Inertia's next version, immediately after committing to no major upgrades for a year.
So, keep building it. Once it's ready, document the migration. I reckon the more valuable contribution would be sharing your journey of replacing Laravel with Trongate, especially if you take up DC's suggestion to turn it into a video. That would give others something practical to learn from.
Cheers!
8 days ago
#25
Hi,
I'm not even sure what a starter kit is, but Dafa speaks for the framework.
Whilst an official 'anything' is off the cards, just look at all the cool things you can have:
1. You can have your work showcased on the Trongate YouTube channel. If you're not willing to present it on camera, either I'll do it for you or (better still!) I'll find someone else who knows what they're talking about to do it.
2. You can leave links to your projects on this forum. We haven't got that feature yet, but I'm sure it won't be too much trouble to build. Would that be useful?
3. I have a couple of friends who use React. I may be able to talk one of them into producing a video tutorial. Just maybe!
It sounds like you've built something very cool, Chandresh. Congratulations!
DC
I'm not even sure what a starter kit is, but Dafa speaks for the framework.
Whilst an official 'anything' is off the cards, just look at all the cool things you can have:
1. You can have your work showcased on the Trongate YouTube channel. If you're not willing to present it on camera, either I'll do it for you or (better still!) I'll find someone else who knows what they're talking about to do it.
2. You can leave links to your projects on this forum. We haven't got that feature yet, but I'm sure it won't be too much trouble to build. Would that be useful?
3. I have a couple of friends who use React. I may be able to talk one of them into producing a video tutorial. Just maybe!
It sounds like you've built something very cool, Chandresh. Congratulations!
DC