A real free tier.
I doubt it. Perhaps you can you can use your home computer for hosting. That one time cost and minor addition to your shared electricity and internet bill.
The aim for Surfer is to be a quite slim static asset server. The current auth which is there was just trivial to add, since there was already the user-interface which was Cloudron auth enabled.
Thank you for this explanation.
I enjoy using it, and it filled in my need for static sites. I previously I used Github pages or Neltify.
Both had limitations and extra management that I avoid with surfer.
A different topic, but one feedback I had with surfer design was, I had to adop token based upload, with managing multiple sites from a single local computer. The global credential was security risk, when one of my site was private.
are you asking how to make a static web site which uses Google Sign-in ?
Yes, I was looking for that.
However since there is no session or active code on the server side to deal with this, all content protection logic has to be done on the client side, which I am then not sure what the benefit of it will be.
Yes, I wondered about this too. I didn't know how the client side library will authenticate if I can have direct link to a different path.
@nebulade - on this topic - surfer has password, and ACL authentication. What does it take to add an OAuth authentication to surfer? Is it possible? Is it desirable / or in roadmap? Your thoughts please.
Is there any other way to add a google oauth to a static pages hosted on surfer?
I believe https://github.com/cloudron-io/surfer/blob/master/src/auth.js is responsible for entire authentication verification before serving the content.
/_admin/using logout of admin file server.
Thanks again. My original question was answered and I find this functionality very useful for keeping my notes with credentials.
I know surfer is a static file server. I know, I can restrict the app with a username (ACL controlled by Cloudron).
If my static site is accessed controlled, and I disallow any indexing. can I be certain that content is public?
Use case I am thinking about.
I normally keep my notes in sphinx-build format. I build them and serve them locally and do not publish it.
I do that because, I want the convenience of copy pasting things, like Tokens, Credentials etc. It is a very important use-case to me. Even as I use both 1password and bitwarden.
With surfer, I am thinking that I will be publishing my notes to a ACL'ed remote location and I can still use my work-flow of copy-pasting tokens and credentials - mostly for system administration purposes.
Do you do this? Can I feel safe to do this with the ACL and password protection of the Surfer content?
If I had a convenient web-application that will do authentication and but serve my sphinx generated site, I will love that. To me, surfer seems to be that.