The multitenant features going into version 1.3 will include branding. You
can already see the initial work in the trunk, by navigating to
/info/me.json. This includes information about the current (possibly
anonymous) user, and the tenant, or organization that owns the URL.
{
"username":"admin",
"roles":["ROLE_ADMIN","ROLE_OAUTH_USER","ROLE_USER"],
"org":{
"id":"mh_default_org",
"name":"Opencast Project",
"properties":{
"logo_small":"/img/OpencastLogo.png",
"logo_large":"/img/MatterhornLogo_large.png"
}
}
}
In other words, skinning customizations, just like security configurations
and workflow definitions, must be tenant specific. Most of these are
already reconfigurable at runtime, and the skinning addition must follow
suit. Thanks for the reminder, Hank.
Josh
On Mon, May 9, 2011 at 12:18 PM, Hank Magnuski <[email protected]> wrote:
>
> Adam suggested a way to customize the logos and html for the UI, but it
> involves rebuilding jar files, which seems like a lot of work just to change
> a jpeg.
>
> I proposed that a "customization directory" be added to config.properties
> and Adam asked me to copy that proposal to this list. See below.
>
> Hank
>
> On 5/9/11 11:31 AM, Hank Magnuski wrote:
>
>>
>> Hi Adam,
>>
>> Thanks for the hint. We'll do this for our demo.
>>
>> This is easy, from the point of view of a developer, but it:
>>
>> 1. Requires the maven build environment to be installed.
>> 2. Requires knowledge of how to rebuild a jar.
>> 3. Requires all the source code to rebuild that jar.
>> 4. etc.
>>
>> May I suggest, if possible, that a much simpler alternative would be to
>> have
>> one line in config.properties that points to an optional customization
>> directory where alternate logo images and index.html might be found, and
>> if
>> found they are used but otherwise default to the jar resources.
>>
>> So something like:
>>
>> # The path to a directory containing optional custom logos and html
>>
>> org.opencastproject.custom.rootdir=${org.opencastproject.storage.dir}/customize
>>
>>
>> The admin and ui services would look there first and then go to wherever
>> they are currently going if nothing was found.
>>
>> With that all you have to do is drop in your jpeg and that's it.
>>
>> Hank
>>
>>
>> On Mon, 9 May 2011, Adam Hochman wrote:
>>
>> > By portal, are you referring to Matterhorn's Media Module? >
>> http://demo.opencastproject.org/engage/ui/index.html
>> > It should be "trivial" to change.
>> > 1. Go to <version>/modules/matterhorn-engage-ui/src/main/resources/ui/
>> > 2. Open index.html, go to line 124, and change the image path to the
>> new > image. Put the new image in
>> > <version>/modules/matterhorn-engage-ui/src/main/resources/ui/img
>> > 3. Redeploy the module matterhorn-engage-ui using mvn.
>>
>> _______________________________________________
> Matterhorn-users mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
