Re: dub: how to update package?
On Saturday, 17 September 2016 at 07:37:23 UTC, Suliman wrote: On Saturday, 17 September 2016 at 07:25:29 UTC, Intersteller wrote: I have a dub project, is there a way to update to get the latest package? dub upgrade Ok, thanks. Thought that would upgrade dub for some reason.
Re: dub: how to update package?
On Saturday, 17 September 2016 at 07:37:23 UTC, Suliman wrote: On Saturday, 17 September 2016 at 07:25:29 UTC, Intersteller wrote: I have a dub project, is there a way to update to get the latest package? dub upgrade I mean, I would like to update the packages used by a project. Not dub itself. Specifically, I would like to update vibe.d from an older version to a newer one.
dub: how to update package?
I have a dub project, is there a way to update to get the latest package?
Vibe.d: Jade has become pug
Might want to update the docs!
Re: Can vibe d leverage existing web technologies?
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.
Aerpspike for vibe.d?
Anyone got any info on it?
Re: Can vibe d leverage existing web technologies?
On Wednesday, 14 September 2016 at 04:22:02 UTC, Brad Anderson 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. Sure. Just use res.write(executeShell(["php", "-f", "somephpscript.php"]).output); or something like that. But seriously, you probably don't want to do that. It's like asking if ruby on rails can leverage php. Sure, they can communicate over HTTP or whatever else they support but trying to execute PHP from within Rails or vice versa just isn't really all that beneficial. It is if you want to use pre-existing technologies. There are tons of php frameworks for doing things. Virtually nothing exists for vibe.d. e.g., any e-commerce stuff for vibe.d? I turned up one outdated, unfinished, and unmaintained package for d. There are hundreds, if not thousands for php. So are you suggesting I do not use vibe.d? It's not like ruby/rails because ruby/rails also has a larger set of technologies. You are comparing apples to oranges. vibe.d has nearly 0 while the others have nearly an infinite. If vibe.d had nearly an infinite I would be asking this question. Hopefully your solution works. Thanks.
Can vibe d leverage existing web technologies?
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.
