On Thursday, 15 September 2016 at 14:31:28 UTC, Martin
Tschierschke wrote:
On Tuesday, 13 September 2016 at 23:45:18 UTC, Intersteller
wrote:
vibe.d does not have much lateral support as the most commons
web technologies do. Can vibe.d leverage pre-existing techs
such as php, ruby/rails, etc? Starting from scratch and having
to build a robust and secure framework is really not the way
to go.
A good way to mix different technologies is to use a Apache or
nginx proxy on the same server, so you can start using vibe.d
for some parts and keep the rest at its place.
Regards mt.
How is this done? How can it be done smoothly? I'm not sure how
to partition the work load. While, say, some pages might be
served from php, and others from vibe2, etc, it seems like it
would be nightmare to maintain consistency and interactivity.
