Hi Stefan,
On Fri, Aug 22, 2014 at 2:03 PM, Stefan Seifert sseif...@pro-vision.de wrote:
System content:
Defines how a specific version of the system behaves.
Multiple system versions can coexist in a shared content repository
(as we demonstrated in [1], in a limited way)
this is for example
Hi,
On Mon, Aug 18, 2014 at 7:35 PM, Ruben Reusser r...@headwire.com wrote:
...looking at this it seems the same functionality would be handy for feature
flags, no?...
Not sure what you mean by that, can you explain more?
-Bertrand
hello betrand.
i try to find the bridge to the multitenancy scenarios i've described in [1]:
Deliverable content:
Displayed on a website or mobile app for example.
Can be global, shared between a group of tenants or tenant-specific.
this is what i've called content in the wiki page. may be page
Hi,
I'm working on various experiments (like [1]) related to continuous
deployment with Sling, and having a clearer definition of the various
roles of the content that a typical Sling applications manages would
help. I'm saying roles instead of types on purpose, to avoid
confusion with
Hi,
Is configuration part of application content or system content or both?
I can see that in a clustered environment you might want to have
configuration shared centrally amongst many versions of the running
application, but you might also need configuration local to a running
version, so that
Hi,
On Mon, Aug 18, 2014 at 2:56 PM, Ian Boston i...@tfd.co.uk wrote:
...
Is configuration part of application content or system content or both?
...
We probably need a more fine-grained definition for configs - for now
I see the following types of configuration:
a) Global system-level config,
looking at this it seems the same functionality would be handy for
feature flags, no?
Ruben
On 8/18/2014 6:19 AM, Bertrand Delacretaz wrote:
Hi,
On Mon, Aug 18, 2014 at 2:56 PM, Ian Boston i...@tfd.co.uk wrote:
...
Is configuration part of application content or system content or both?
...
