@joseph said in Request: Feature Parity between Surfer and Cloudron File Manager.:
files text editor should be put in Surfer
Yes
@imc67 said in Request: Feature Parity between Surfer and Cloudron File Manager.:
zip/unzip would be very convenient
Yes
Not sure you even need that, as I recall writing some JS for a list of redirects based on the incoming request which could send you anywhere else as part of the index.html on a Surfer App.
The main issue I think was URL cloaking so the address bar doesn't change, while the content of the page does.
do you happen do see any other error on the surfer server side app logs while trying the failing command? I wonder if something errors and the Invalid token message is just a side effect then.
@insuusvenerati if you use one of the automated DNS providers, you can keep your server completely private just like you have now as well. No change in setup needed, don't even have to open port 80/443 ...
@nebulon Yes - I was getting confused about the WebDAV API keys, what user name as needed, etc. The thing that helped the most was clicking on the SFTP dialog for the app, which makes it very clear what the login information is. Clicking on SFTP for the Surfer app shows:
[image: 1723582196179-f04ce061-ff35-4938-8219-ff57e38b8783-image.png]
Thanks for your help! One more app configured and migrated
Since it is a static site generator, I guess you could also generate the assets locally and then push to a surfer instance.
Otherwise, it may be similar to github pages, which build the static assets on git push and then just serve those. For this you would probably build a custom Cloudron app, which knows how to build the assets.
@nebulon said in Docs wrong?:
For the cli help, did you mean the /app/data/* -> /* ? If so that is also fixed but pending a cli release.
Yes, I was referring to the 4th example:
surfer put dir/* / # puts dir/* as /app/data/*
