I think the real problem is that you can not access directly a file like document.md with an Nextcloud url. You always need the fileId. You can see this with browsing in Nextcloud Files. For internal links you maybe use the external url But i think you can not use the path / name.
nextcloud download link
Download
https://xiuty.com/2xw5Kz
Hi,
i just struggle with the same problem.
A little circle of colleagues in my company like to use external editors like vimwiki but the majority is only used to work with the nextcloud text-editor.
Please consider supporting simple relative path-syntax for file-linking.
Also not forcing the md-files to be opened in edit-mode would be great, as it would massively reduce useless news-feed in the activities-board.
I may be dumb but I searched a lot for this functionality. Somehow, a lot of strange answer came from search engines (even tried chatGPT that bullshited me as usual)...
You must actually understand a bit of webdav usage in nextcloud to come up with a working solution. So I think it is worth sharing
I'm always getting "Failed to create file system for ":webdav:": the remote url looks incorrect. Note that nextcloud chunked uploads require you to use the /dav/files/USER endpoint instead of /webdav. Please check 'rclone config show remotename' to verify that the url field ends in /dav/files/USERNAME"
nextcloud will let you mount samba shares as external sources, using the users username and password to access the shares. If you are using an AD or LDAP server for credentials, they can log in automatically to their samba shares. Next cloud can also use Samba to authenticate.
For the record you have an issue on GH for nextcloud and samba shares
github.com/nextcloud/server Issue: NC 12.0.3: Unable to mount SMB sharesopened by j-edon 2017-09-21Expected behaviorNextcloud should be able to mount external SMB shares.Current behaviorNextcloud seems not able to always mount an external SMB share,... 0. Needs triage bug feature: external storage
To set a quota set the "nextcloud_quota" property in the user's attributes. This can be set for individual users or a group of users, as long as the target user is a member of a group which has this attribute set.
After the provider is created, link it to an app. Go to Applications -> Applications. Create an application and choose the provider you just created. Make sure to take note of the application slug. You will need this later.
Note: For information on how to use the file storage (link Nextcloud user accounts at a user level, link files to a work package, view and download linked files, unlink files), please read our Nextcloud integration user guide.
Important: Deleting a file storage as an instance administrator will also delete all settings and links between work packages and Nextcloud files/folders. This means that should you want to reconnect your Nextcloud instance with OpenProject, will need complete the entire setup process once again.
Once the file storage is added and enabled for projects, your users are able to take full advantage of the integration between Nextcloud and OpenProject. For more information on how to link Nextcloud files to work packages in OpenProject and access linked work packages in Nextcloud, please refer to the Nextcloud integration guide.
I already got a tt-rss installation on a apache virtualhost and letsencrypt, but now I want to install second application nextcloud on another virtualhost. My contraints is that I have only one computer, one ip and one domain. I can't manage subdomain and I don't want to use different port. I would like to use path location too reach the two services separately like this:
https:\my_registered_domain\ttrsss\
https:\my_registered_domain\nextcloud\
I have nextcloud running on but since we will use nextcloud primarily for opening data to the public I would like that this nextcloud root url leads to a public nextcloud folder directly, e.g. to use this one: but so that the public would not need the url with the share sub-url but only type in where this public folder would be opened.As for logging in and synchronizing with nextcloud I would then like to use another sub url such as this for example:
I got nextcloud running with docker on a Ubuntu 20.04 Server. Since other services are running on this server too, I set up a reverse proxy solution all with docker too including these images: nginx, jwilder/docker-gen:0.7.3, jrcs/letsencrypt-nginx-proxy-companion which do the reverse proxy and also generate the config files for reverse proxy. The docker-compose.yml for all this is this:
What I have tried so far is pushing the html code of nextcloud into a subfolder and fiddling around with settings such as overwritewebroot or overwritehost in config.php and various experimentation on nginx reverse proxying, but it all failed so far.What I have tried to follow were discussions such as these for example:
Then opening
cloud.museumsstrasse.at with the browser would get redirected to
cloud.museumsstrasse.at/internal but in the meantime the code in /var/www/html/internal/ got deleted and overwritten with nextcloud code in /var/www/html/ which I then can not open because the browser would redirect me to
cloud.museumsstrasse.at/internal again.
However even if something with overwritewebroot were working, how could I avoid this redirection from
cloud.museumsstrasse.at to
cloud.museumsstrasse.at/internal? Because the former should be the public face and the latter our internal nextcloud side. Hence I want no redirection but two different urls for different purposes.
I assume if a pragmatic way would be to adapt nextcloud's docker image logic to point it to /var/www/html/internal/ and then adapt the this docker's internal apache to show
cloud.museumsstrasse.at while serving content from the public
foldercloud.museumsstrasse.at/s/Ytpcwos3o9o33kL ? However I'm at a loss of how to do this...
Until now, usage of Collabora Online in Nextcloud was restricted to users with a Nextcloud server account. Nextcloud 11 introduces a new feature of sharing links that allow viewing and editing of documents on a Nextcloud server.
f5d0e4f075