RejectedSoftware Forums

On Fri, 05 Apr 2013 09:37:34 GMT
"Dicebot" m.strashun@gmail.com wrote:

I have been doing some lazy writing on vibe.d topic. Aim is to get
series of articles that can get reader familiar with vibe.d idioms
and highlight use cases currently not presented properly in
documentation (or hard to find there). Found myself in quite
paradoxical situation though - while being quite familiar with vibe.d
sources and behavior, I don't to any practical web development on my
own and lack real-world use cases to highlight. After some
introduction articles, I have done a small overview of REST module
and working with MongoDB is planned next (those two I have used
extensively during my experiments). But I'd like to hear suggestions
on other idiomatic small applications that are worth writing about,
preferably something that is not obvious from vibe.d/examples/

This may be proposed later via pull request as an official doc
improvement.

First introductory articles can be found here :
http://dicebot.blogspot.com/ , improvement suggestions for old stuff
are also welcome.

I haven't really looked through much of vibe.d's examples, but I'd say
maybe a basic form submission complete with validation and re-entering
the user's data back into the form when validation fails. You could
start with the example I posted in the "vibe.d / Open-Transactions /
Untraceable digital cash" thread, or something like it.

Then maybe expand that into a basic comment-posting system.

On Fri, 5 Apr 2013 12:04:53 -0400, Nick Sabalausky wrote:

Another idea would be setting up a Vibe.d program behind an Nginx or
Apache reverse proxy. Or setting up a vibe.d program as a linux
daemon. Those would likely be common needs. I've done both, so I could
help you out with any questions.

What is the issue with nginx reverse proxy? It worked with default proxy_pass approach for me.

On Fri, 5 Apr 2013 11:36:11 -0400, Nick Sabalausky wrote:

I haven't really looked through much of vibe.d's examples, but I'd say
maybe a basic form submission complete with validation and re-entering
the user's data back into the form when validation fails. You could
start with the example I posted in the "vibe.d / Open-Transactions /
Untraceable digital cash" thread, or something like it.

Have used your proposal two write two newbie-level articles:

Environment: http://dicebot.blogspot.de/2013/07/setting-up-simple-vibed-application.html
Application: http://dicebot.blogspot.de/2013/07/setting-up-simple-vibed-application-app.html

Review is really appreciated.