We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hint the end user about related apps he can install
For CNB / MU: he shall be advised Twake Sync
Twake Sync
For Linagora: Twake Sync, Twake chat and why not LinShare
Twake chat
LinShare
For TWP: Twake chat
=> We see that this app grid is deployment dependant
So this means the back needs to be configured for it, and info carried over to the front.
Add a section in /.well-known/linagora-ecosystem:
/.well-known/linagora-ecosystem
"mobileApps": { "Twake Chat": { "logoURL": "https://xyz", "appId": "abc" }, "Twake Drive": { "logoURL": "https://xyz", "webLink": "https://tdrive.linagora.com" }, ... }
Should be configurable...
The text was updated successfully, but these errors were encountered:
pr #1347
Sorry, something went wrong.
vttranlina
Successfully merging a pull request may close this issue.
Why
Hint the end user about related apps he can install
For CNB / MU: he shall be advised
Twake Sync
For Linagora:
Twake Sync
,Twake chat
and why notLinShare
For TWP:
Twake chat
=> We see that this app grid is deployment dependant
So this means the back needs to be configured for it, and info carried over to the front.
What
Add a section in
/.well-known/linagora-ecosystem
:Should be configurable...
The text was updated successfully, but these errors were encountered: