Provide a "site" configuration

[pmuir]

Due to the distribution method we are suggesting for this editor - each user installs their own instance, it would be good to be able to provide "site" configuration. For example, we clone and branch the editor, provide the custom config, and then tell users to use that repo, with the custom config.

This config might be also editable via the gui, or not.

[LightGuard]

What settings do you have in mind? We're requiring GH user/pass and
upstream repo to fork. Are you talking about awestruct site.yml config?

On Wed, Jul 10, 2013 at 9:25 AM, Pete Muir [email protected] wrote:

Due to the distribution method we are suggesting for this editor - each
user installs their own instance, it would be good to be able to provide
"site" configuration. For example, we clone and branch the editor, provide
the custom config, and then tell users to use that repo, with the custom
config.

This config might be also editable via the gui, or not.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/32
.

Jason Porter
http://en.gravatar.com/lightguardjp

[pmuir]

No, I'm thinking of things like #30 - I would like to be able to preconfigure the (perhaps) defaults for this filter - this isn't something I want the user to have to do.

IOW, I want to create "team-specific" config of the web-editor. For example, I want to offer a mode which only displays certain files for the marketing team, and turn on the auto-commit mode from #31.