On Fri, 26 Jul 2013 17:02:55 GMT, Sönke Ludwig wrote:

On Thu, 25 Jul 2013 15:28:25 GMT, Christoph Wendler wrote:

On Thu, 25 Jul 2013 15:04:07 GMT, Sönke Ludwig wrote:

On Thu, 25 Jul 2013 14:23:26 GMT, Christoph Wendler wrote:

I am new to vibe.d. I set up a test project on Linux which works fine. I'm thinking about using vibe.d for my homepage. The question now: How would I set vibe.d up on a provider's server (Linux)?

If you have a binary-compatible Linux PC, I would recommend to compile the project on the home computer and then just upload the final binary. In that case it's only necessary to have libevent 2.0.x and OpenSSL installed. This should work for any provider that allows execution of custom binaries as an ordinary user.

Thanks. This means it's a static block that cannot be changed online. How would people find it, by typing www.myhomepage.com? I would probably have to redirect requests on the server: address > binary

With binary I just meant the compiled executable. It can be replaced any time and can also use a local database or write to a file to deliver dynamic content.

If you don't have a server, yet. I would recommend to get a cheap virtual server and register a domain at the same provider (there was a thread on this some time ago). You can then install nginx, use the linked [configuration][1] and change the server name to the registered domain. If you then let your vibe.d app listen on port 1234, it should be available using the registered domain name.

To have the site run on port 80, in this case it would be necessary to put it behind a reverse proxy, such as nginx. Apache will work fine, too. Putting the site behind a reverse proxy makes sense also for improving robustness against DoS attacks or to setup a cache.

In this case the site could theoretically be edited and recompiled, given that vibe.d supports this (see Zero-downtime changes) and the provider allows such operations.

Since the [vibedist project][2] (which is meant to provide vibe.d's zero-downtime changes) is still largely work in progress, for now, you will have to manually recompile and upload the new executable. If you then have a watchdog script running, you can just kill you app using "killall <executable-name>" to have it immediately be restarted. All of this can relatively easily be automated using a shell script, but that depends on how much one is into shell scripting (e.g. using [inotify][3]).

[1]: https://github.com/rejectedsoftware/vibe.d/wiki/Setting-up-Nginx-as-a-reverse-proxy
[2]: https://github.com/rejectedsoftware/vibedist
[3]: https://gist.github.com/Dav1dde/5564367

Thanks a million. VPS sounds interesting, I only hope that it doesn't mean an increased work-load for me.