I've released the new surfer version which has this fixed. The update is currently only available when checked for manually.

@nebulon Yeah, I think that would be informative. And actually I was expecting it to number the new file. Going down the road, now I know why some version control may be useful for the workflow. A pre-warning could help.

@nebulon thanks! Indeed the upload now succeeds with the new version. For the wrong timestamp i'll just touch the folder once before calling surfer. Maybe it eventually gets fixed in hugo itself.

@nebulon said in Does Surfer support symbolic links?: the filelisting is a different issue, hopefully I can rework the surfer UI this week to make that possible That would be great, good luck @nebulon said in Does Surfer support symbolic links?: webdav apparently does not support symlinks as such. Ah, yes, I'd worked that out, but had forgotten that when I was rsyncing I was doing so to a local folder mounted using webdav. That's obviously why it didn't work.

@nebulon awesome, just did. Thanks so much!

I have fixed this WebDAV/LDAP issue now with the just release app package. Please let me know if there is still some problem or if it works now.

@mehdi @nebulon it was the right URL, but that doesn't mean I'm not an idiot I forgot to actually update the app to the latest version with CORS compatibility After an update, all is working as expected! Appreciate the help and quick turn around! [can mark as resolved]

@masonbee The memory limit setting is the "maximum memory" before which the app is killed for over use. It is not "reserved memory" i.e it's not pre-allocated to the app and thus cannot be used by any other app. The "maximum memory" simply ensures that a single web app cannot bring down the whole system.

@girish Yes, I was using a capital in the username. Now I have access after creating a new user with no caps. Thanks.

Removing the root ala / does not work. I have to fix the code. The code is at https://git.cloudron.io/cloudron/surfer/-/tree/master/cli

@nebulon files are between 64B and 1.5MB each, so not big. I can try with a different browser, of course. What I would suggest is to put a <noscript> tag in there (with links to download file, and potentially filesname too) which would basically be shown if you don't have javascript. This would resolve the problem.

This was fixed in the release yesterday.

This is solved but I can't see anyway to mark it solved myself.

@msbt Ah, there we go! Quick and dirty solution, now that I know of the built-in redirections support but very flexible. Thanks!