Experience: Developing Cloud Foundry applications with D

[Andre via Digitalmars-d]

On Tuesday, 6 October 2015 at 09:36:42 UTC, Marc Schütz wrote:
> On Tuesday, 6 October 2015 at 05:45:18 UTC, Andre wrote:
>> vagrant at vagrant-ubuntu-trusty-64:~/projects/tests/vibed_test$ 
>> dub
>> Target memutils 0.4.1 is up to date. Use --force to rebuild.
>> Target libasync 0.7.5 is up to date. Use --force to rebuild.
>> Target vibe-d 0.7.25 is up to date. Use --force to rebuild.
>> Building vibed_test ~master configuration "debug", build type 
>> debug.
>> Compiling using dmd...
>> Enhanced memory security is enabled.
>> Using Linux EPOLL for events
>> Linking...
>> Running ./bin/app
>> Listening for HTTP requests on :::8080
>> Listening for HTTP requests on 0.0.0.0:8080
>> E: Could not mlock 65536 bytes
>
> Does it keep running? AFAIK, the last line is just a warning 
> from the botan library that attempts to allocate non-swappable 
> memory for holding secret keys etc.

I got it working. *Argh* I forgot the command parameter in the 
cloud foundry manifest file. vibe-d is working fine, out of the 
box in cloud foundry with libasync :)