-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
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
Add Uppy Companion to wopi example #6702
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
deployments/examples/ocis_wopi/.env
Outdated
COMPANION_DOMAIN= | ||
COMPANION_ONEDRIVE_KEY= | ||
COMPANION_ONEDRIVE_SECRET= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would this look like for the continuous deployments? How is ist related to WOPI / Office integration in oCIS?
To me it feels like this needs a dedicated example, which probably has no continuous deployment because of the missing secret management for our continuous deployments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I asked @micbar and he wanted me to add it to the wopi example, so it's "full featured".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But will it work when COMPANION_ONEDRIVE_SECRET and COMPANION_ONEDRIVE_KEY is unset?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, OneDrive integration obviously won't ... but e.g. https://uppy.io/docs/url/ would
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahh ok, would be nice to add this as comments to the parameters. I didn't know and thought it's needed to make it work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... we most likely will need to add a setting to enable certain integrations in the ui, but the way the import is configured is about to change anyway, so it's probably not worth adding it now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm yeah, well - I thought that was kinda self explanatory, no other variables in .env
have that kind of comment although they are empty and everything works
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i enabled only "Public Link".
@micbar I'd like to reference the wopi deployment example in the releasenotes, but would not drive documentation further for this feature. ok for you? |
I am still not decided if we should deploy it in the continouus deployments at all. It was a big effort doing it for the example deployment. |
We could also just deploy the public link provider... |
@micbar SonarCloud seems to be "unwilling" to continue, not only here. I tried before with a rebase and it "hung". I think the important two are green... |
Example is incomplete. Not sufficient. We need to check what we can do with the config file templating. |
This is highlighted in our release notes https://doc.owncloud.com/docs/next/ocis_release_notes.html and is still open. We should remove this from the release notes if there is no way for our customers to use this feature. |
I tried to deploy the Upload Companion in my test environment, but nothing changed on the Web Interface. I'm pretty sure I made everything correct. Is that working with v4.0.0+? |
I'm sorry, this PR was probably misleading. We changed the way the importer is configured after this PR was sent and then noone made a decision how to progress here, so it got stale and outdated. {
...
"external_apps": [
{
"id": "importer",
"path": "web-app-importer",
"config": {
"companionUrl": "https://your.companion.url/",
"webdavCloudType": "owncloud"
}
}
]
...
} |
@dschmidt can you fix that PR so it can be merged and the example becomes available? |
I can, but I need a decision we actually want that. Quoting @micbar :
|
This is somehow rediculous. |
@mmattel Like i said there is a technical blocker. |
Thanks @dschmidt ! |
In the Web dev setup we do it like this: https://github.com/owncloud/web/blob/b7f1c5dd5ddd7faa62e1fddbb8ae18e67093d011/docker-compose.yml#L16 so basically you need to mount it to your container and use the I'm sorry this is so hard right now... |
Thanks @dschmidt ! I successfully managed to deploy the Cloud Import Feature. I have an OwnCloud v10 remote instance and I tried to import files using a generated Public URL from it, but it didn't work. Please find the latest Companion container log lines below:
|
Cool, good to hear!
The error message comes from here: https://github.com/owncloud/uppy/blob/f3ce884e43d6dd8732a0cafb8d32ee8ba9a12d9b/packages/%40uppy/companion/src/server/provider/index.js#L118 -> https://github.com/owncloud/uppy/blob/f3ce884e43d6dd8732a0cafb8d32ee8ba9a12d9b/packages/%40uppy/companion/src/server/provider/index.js#L25 So apparently you don't seem to have |
Thanks again @dschmidt ! I'm still in doubt about how to solve this last error since I would like to import data from OwnCloud v10 to Infinite Scale v4, where my OwnCloud relies on EBS Volumes to store data while my Infinite Scale relies on S3 Buckets. On Companion docs, there are environment variables available for these services: How could I proceed? Or in this case, Uppy Companion won't be able to help me importing data from OwnCloud? |
We added a feature to uppy companion where you can import from an ownCloud 10 public link. It is not yet upstream. Isn't it @dschmidt ? |
Correct, upstream is working on it. I think they haven't decided whether they want to integrate it fully into their product, but they are working on providing the necessary apis at least. |
Note to myself: Maybe change the ocis config to make it configurable via ENV |
8935dfb
to
e2fb018
Compare
6a994fc
to
f0c7983
Compare
f0c7983
to
3860ed4
Compare
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Add Uppy Companion to wopi example
🎉 Thanks for taking this over the finish line |
Add Uppy Companion to wopi example
Description
Add Uppy Companion to wopi example, so cloud imports work as soon as the importer app is shipped with oC Web.
Related Issue
Motivation and Context
Cloud imports need the Uppy Companion microservice.
How Has This Been Tested?
Tested locally with my own build of oC Web.
Screenshots (if appropriate):
Types of changes
Checklist: