Hello! Really enjoying D so far and have started to toy around
with Vibe.d.
I was just wondering if someone here has had any experience with
publishing vibe applications on the OpenShift Paas?
(https://www.openshift.com)

Please let me know how you did it, because I know it's possible
with the DIY-cartridge they provide you(atleast it should be).

On 24/07/2014 1:28 p.m., Rutger wrote:
> Hello! Really enjoying D so far and have started to toy around
> with Vibe.d.
> I was just wondering if someone here has had any experience with
> publishing vibe applications on the OpenShift Paas?
> (https://www.openshift.com)
>
> Please let me know how you did it, because I know it's possible
> with the DIY-cartridge they provide you(atleast it should be).

I was looking into it a while back. Its not so much the cartridges which are a problem. They are pretty easy to make. The issue is with the gears. 2gb is the max and most expensive.
But with D unless your very careful 1gb is more the norm. Atleast in my tests with Cmsed.
Also you will need to find a way to compile for their instances OS. Could be an issue as its most likely redhat (as its owned by them).

But they have a free plan. Might as well have a go.

On Thursday, 24 July 2014 at 01:47:43 UTC, Rikki Cattermole wrote:
> On 24/07/2014 1:28 p.m., Rutger wrote:
>> Hello! Really enjoying D so far and have started to toy around
>> with Vibe.d.
>> I was just wondering if someone here has had any experience with
>> publishing vibe applications on the OpenShift Paas?
>> (https://www.openshift.com)
>>
>> Please let me know how you did it, because I know it's possible
>> with the DIY-cartridge they provide you(atleast it should be).
>
> I was looking into it a while back. Its not so much the cartridges which are a problem. They are pretty easy to make. The issue is with the gears. 2gb is the max and most expensive.
> But with D unless your very careful 1gb is more the norm. Atleast in my tests with Cmsed.
> Also you will need to find a way to compile for their instances OS. Could be an issue as its most likely redhat (as its owned by them).
>
> But they have a free plan. Might as well have a go.


Right now I've managed to try and start the binary but it logs an
error because the required libraries can't be found. Also do you
know if it's possible to compile a binary on ubuntu that will be
compatible with RHEL/Fedora?

On 24/07/2014 2:48 p.m., Rutger wrote:
> On Thursday, 24 July 2014 at 01:47:43 UTC, Rikki Cattermole wrote:
>> On 24/07/2014 1:28 p.m., Rutger wrote:
>>> Hello! Really enjoying D so far and have started to toy around
>>> with Vibe.d.
>>> I was just wondering if someone here has had any experience with
>>> publishing vibe applications on the OpenShift Paas?
>>> (https://www.openshift.com)
>>>
>>> Please let me know how you did it, because I know it's possible
>>> with the DIY-cartridge they provide you(atleast it should be).
>>
>> I was looking into it a while back. Its not so much the cartridges
>> which are a problem. They are pretty easy to make. The issue is with
>> the gears. 2gb is the max and most expensive.
>> But with D unless your very careful 1gb is more the norm. Atleast in
>> my tests with Cmsed.
>> Also you will need to find a way to compile for their instances OS.
>> Could be an issue as its most likely redhat (as its owned by them).
>>
>> But they have a free plan. Might as well have a go.
>
>
> Right now I've managed to try and start the binary but it logs an
> error because the required libraries can't be found. Also do you
> know if it's possible to compile a binary on ubuntu that will be
> compatible with RHEL/Fedora?

Its possible, but not really worth it. Use a VM of some sort if you must.
You may need to distribute the dependency binaries with it.

> Please let me know how you did it, because I know it's possible
> with the DIY-cartridge they provide you(atleast it should be).

I tried it some time ago. It is possible but:
 - vibe.d requires a lot of memory for project compilation
 - it is hard to install additional libraries (it is not usual Linux distrib)

On 2014-07-24 3:45 AM, Nikolay wrote:
>
>> Please let me know how you did it, because I know it's possible
>> with the DIY-cartridge they provide you(atleast it should be).
>
> I tried it some time ago. It is possible but:
>   - vibe.d requires a lot of memory for project compilation
>   - it is hard to install additional libraries (it is not usual Linux
> distrib)
>

You should compile and test on a CentOS 6.3 machine first and then write the cartridge using the wget command to move the same libevent package and the compiled vibe.d binary. You won't be able to compile on a cartridge.

Your cartridge would look like this:

https://github.com/Filirom1/openshift-cartridge-nodejs/blob/master/bin/setup

On Thursday, 24 July 2014 at 02:48:45 UTC, Rutger wrote:
> On Thursday, 24 July 2014 at 01:47:43 UTC, Rikki Cattermole wrote:
>> On 24/07/2014 1:28 p.m., Rutger wrote:
>>> Hello! Really enjoying D so far and have started to toy around
>>> with Vibe.d.
>>> I was just wondering if someone here has had any experience with
>>> publishing vibe applications on the OpenShift Paas?
>>> (https://www.openshift.com)
>>>
>>> Please let me know how you did it, because I know it's possible
>>> with the DIY-cartridge they provide you(atleast it should be).
>>
>> I was looking into it a while back. Its not so much the cartridges which are a problem. They are pretty easy to make. The issue is with the gears. 2gb is the max and most expensive.
>> But with D unless your very careful 1gb is more the norm. Atleast in my tests with Cmsed.
>> Also you will need to find a way to compile for their instances OS. Could be an issue as its most likely redhat (as its owned by them).
>>
>> But they have a free plan. Might as well have a go.
>
>
> Right now I've managed to try and start the binary but it logs an
> error because the required libraries can't be found. Also do you
> know if it's possible to compile a binary on ubuntu that will be
> compatible with RHEL/Fedora?

Yes. However, you will probably have compatibility problems with the various shared libraries loaded by your executable, most prominently glibc.

>
> You should compile and test on a CentOS 6.3 machine first and then write the cartridge using the wget command to move the same libevent package and the compiled vibe.d binary. You won't be able to compile on a cartridge.
>

Yes but what if I use some additional libriaries? Every new library is challenge.