I think "schemas":["urn:scim:schemas:core:1.0"] is missing into your body request no ?

Btw when the error "*cflinuxfs2 stack not found" come ? At the staging level ? do you have some log?* *Which buildpack are you using and so on ..*

What cf stacks command give you ?

I mean which version are the DEA ? the stack do not live in the stemcell ... The stack are install during the deployment

Are you sure all you DEA are at the same version ? I think so but I don't know maybe rare case.

Not sure yet .. I am still thinking about that .. But anyway if ERS is too hard I will use the bosh way :) wrote:

DB is setup by a config file, no enviroment variable or other. I was thinking about adding a new component to the buildpack (fork..) to setup this file ..

Hi everyone, I wonder if someone succeed or tried to run Jira into cloudfoundry (ERS). It's not that difficult with bosh but for Cloudfoundry the difficult part is to configure the DB. Thanks

Simon I know what you want todo :) I am shinji62 lol I am jsut afraid that you want to customize the platform and you will be stuck with because other don't support custom header. wrote:

So if you move to Heroku you will be able to change the platform ??? I don't think so.. So you can put the new header from your app or at least the runtime buildpack or docker. Your application should

I am guessing a problem in your yaml file and the spring profile shoud be 'saml,default,fileMetadata' for saml no ? But I am not sure about the exact format

It seems the routers and Haproxy works as you get the 404 from the routers "404 Not Found: Requested route ('api.subdomain.domain') does not exist." Maybe something wrong in the manifest especially ar

I merge it. This repos since unmaintained since some month.

It depends, but what James suggest is to use an external service for PUB/SUB. All your application listen on it and they will get notifify.

I guess , It can run with 3 nodes but it seems it not doing well with the 3 nodes on the same zone. wrote:

Or just DIY... cloudcontroller are pretty well documented.

I am going everytime mostly :) anyway next time will come to you.

Yes you can find the version based on the cf-release version here http://apidocs.cloudfoundry.org/212/ For the pro/cons I don t really know, I just contributed to the go-cfclient so I don't really kno

humm, Most simple is to call the Cloudcontroller API.... like we do here https://github.com/cloudfoundry-community/go-cfclient

No is not related, so you private registry have no user or password ?