This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

This ticket is no longer relevant.

In T981#15995, @Adityab wrote:

@vanmeeuwen I'm testing a 30-second timeout for attempting a MongoDB connection, following which Manticore would terminate gracefully. Which is necessary to have anyway in an environment where one runs Manticore directly without systemd.

@vanmeeuwen I'm testing a 30-second timeout for attempting a MongoDB connection, following which Manticore would terminate gracefully. Which is necessary to have anyway in an environment where one runs Manticore directly without systemd.

@Adityab it's been a while now, could you let us know what your assessment is?

@Adityab, assigning to you for an initial assessment on whether this can reasonably be achieved technically.

This may be more important when you know that phantomjs sometimes fail to open some document, then I observe:

Feb  5 12:12:18 localhost manticore: PhantomJS Log : will be back later...

two times per second, and it does not stop until I restart manticore.

So, the default behavior is to set 'Untitled Document' as the placeholder in the title widget. Just like the Manticore UI, you'd need to write your own placeholder logic in the Roundcube UI.

Fixed in ab9f1b8a34ad

Manticore itself should not depend on the mongodb-server package, but kolab-webclient can.

Do you mean that this works for you in your development setup, but not in the packaged version?

Joining the session is already implemented. I'd need more info about the free/busy interface.

Good catch. On it (once I get the session closed event working).

As Chwala uses kolab_auth plugin we can use kolab_auth_role_settings option for this. E.g.:

$config['kolab_auth_role_settings'] = array(
    'cn=contractor,%dc' => array(
        'fileapi_manticore' => array(
            'value' => null,
        ),
    ), 
);

In current implementation Manticore does not know the real file path, so the magic have to be done on Chwala side.

Oh, this happens only with Firebug console opened. It does not happen with built-in development tools. I'm closing this for now.

Implemented as fileapi_manticore option.

A couple of updates:

Update: @machniak informed me that it shall be simpler for Chwala to just 'register' the uuid to Manticore. Then, Manticore can send a request to retrieve that file when needed.

An update: Chwala may or may not store user login credentials for external storage based one what the administrator chooses. However, it becomes impractical to present a login dialog to Manticore users when they want to save a document.

So in Manticore's upcoming Chwala storage adapter,

I see this as a simple configuration option for Chwala that defines Manticore URL. That would then be passed to kolab_files as Chwala boolean capability.