yea i already took a look at this solution, its a different approach to reach the same goal. Iam not sure if there is a way to merge this two different solutions but maybe if i have some time i will take a closer look an get in contact with Amian
Thanks for your feedback. I already thought about such implementation for specific folders in the Vault. But something like that would require a lot of more effort because you need some kind of backend system to administrate this access and rules, a session management, bruteforce prevention and so on… So to be honest, right at this moment i am not planing to implement this feature in the near future.
If you only want to restrict the access to the whole vault i would recommend some kind of infrastructure based authentication like .htaccess or mutual authentication or something like that.
You can make those web .md notes embedded with iframes from CryptPad and the user will only manually give access (read only) to those you want after a simple email registration. It’s really simple if the user is allowed to choose whether to embed certain .md notes from CryptPad (or other services) on the website, I think.
Thanks for your idea, but I don’t think this is easy to achieve. Perlite doesn’t just display provided .md files, so you can’t easily view them via iframe. Each .md is parsed by the PHP engine and the markdown is translated into HTML, so PHP without an interface (e.g. to CryptPad) does not know which user has access to the file or not.
Also keep in mind that the free CryptPad plan only gives you 1GB of storage.
Access restrictions, based on single .md files could be implemented, for example with some special prefix in the filename or content, but then the next question is, should the file name be displayed in the navigation? What about the parent folder? Also without a database in the backend you cant handle multiple useres or different access levels.
One way to create a private space would be: create two main folders or vaults, one private and one public, and then separate them with two perlite instances and two nginx vhosts, secure the vhost configuration for the private one with a client certificate authentication (mutal authentication). Then provide the certificate to the users you want to grant access to. Alternatively, extend the private Perlite instance with a simple http authentication.
But Perlite is open source, so feel free to fork it and implement any authentication or third-party service if you like.
Thanks for sharing your great work.
Is it possible to make Perlite work on Netlify or some alike services?
My programming skills are quite low, so I couldn’t get to make it work unfortunately. Is there a chance that we could get some more detailed instruction on installing and running Perlite?
Unfortunately I don’t know the system or provided information about Netilify, but I know Perlite does usually work on a shared Hosting service. I think best option would be to join the Perlite discord server and maybe we can help you there to get it running.