I just wanted to say thank you for vibe.d, Sönke and Kai (for the book). I use vibe.d for all new web projects, and it's great. Less and less JS, more and more D. It's also very fast.

The way we use it is that we set up little vibe.d servers behind the scenes and redirect to them.

On Friday, March 24, 2017 12:23:23 Chris via Digitalmars-d wrote:
> I just wanted to say thank you for vibe.d, Sönke and Kai (for the book). I use vibe.d for all new web projects, and it's great. Less and less JS, more and more D. It's also very fast.
>
> The way we use it is that we set up little vibe.d servers behind the scenes and redirect to them.

As in you use something like nginx on the outside and have it send requests on to vibe.d if they get past whatever blocking or whatever else you have set up with the external server? So, anyone talking the server sees nginx, but the actual website content or REST API or whatever is done by vibe.d?

- Jonathan M Davis

On Friday, 24 March 2017 at 21:37:22 UTC, Jonathan M Davis wrote:
> On Friday, March 24, 2017 12:23:23 Chris via Digitalmars-d wrote:
>> I just wanted to say thank you for vibe.d, Sönke and Kai (for the book). I use vibe.d for all new web projects, and it's great. Less and less JS, more and more D. It's also very fast.
>>
>> The way we use it is that we set up little vibe.d servers behind the scenes and redirect to them.
>
> As in you use something like nginx on the outside and have it send requests on to vibe.d if they get past whatever blocking or whatever else you have set up with the external server? So, anyone talking the server sees nginx, but the actual website content or REST API or whatever is done by vibe.d?
>
> - Jonathan M Davis

It's still all Apache.