You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hey, I'm quite a heavy PKM user and have been using Obsidian since ~ 2020; crossing my first one hundred thousand of words I came to the point sometimes, I need to share some thoughts with others pretty easily.
Yet I would like to see it shared in a custom way, maybe with different/own domain / deployment
Describe the solution you'd like
I saw deployment instructions and see it's not so trivial to run for oneself, even though I'm tech savvy person I can clearly say I don't have time to manage VPS :)
I would like to see noteshare leverage kind of serverless infrastructure with some KV storage for purpose storing just markdown files and some CSS customizations in some case.
Flow how I could anticipate could be people could have CloudFlare button to spin their own instance with Workers and Storage and voila. Later could be extended to use cf-r2 for media files?
For domain, doesn't matter now, CF provides workers and costs for hosting are free or close to cents for milion requests, doubt someone will make that much with notes?
Currently, it runs on a VPS I rent for about 7$/month. https://noteshare.space/funding
The storage requirements for hosting encrypted text data are incredible small; at the time of writing (28 September, 2022), Noteshare is storing 1,000 notes in a little over 7MB.
Quick share has already close to 4k downloads, I guess this could be an interesting extension to cut costs as they might be only growing quite.
The text was updated successfully, but these errors were encountered:
yangwao
changed the title
[Feature request]
[Feature request] Own serverless deployment with CloudFlare workers
Jan 11, 2023
I have worked with CloudFlare workers in the past for other projects, and when developing Noteshare I debated whether or not to host it with CF. In the end, I opted against it because it reduced portability for people who want to self-host without locking into the CF Workers platform. However, I agree the Noteshare architecture is perfect for Workers.
I understand that self-hosting is currently not that straight-forward, and am open to improving that use case since there is sufficient interest in self hosting.
Is your feature request related to a problem? Please describe.
Hey, I'm quite a heavy PKM user and have been using Obsidian since ~ 2020; crossing my first one hundred thousand of words I came to the point sometimes, I need to share some thoughts with others pretty easily.
Yet I would like to see it shared in a custom way, maybe with different/own domain / deployment
Describe the solution you'd like
I saw deployment instructions and see it's not so trivial to run for oneself, even though I'm tech savvy person I can clearly say I don't have time to manage VPS :)
I would like to see noteshare leverage kind of serverless infrastructure with some KV storage for purpose storing just markdown files and some CSS customizations in some case.
Flow how I could anticipate could be people could have CloudFlare button to spin their own instance with Workers and Storage and voila. Later could be extended to use cf-r2 for media files?
For domain, doesn't matter now, CF provides workers and costs for hosting are free or close to cents for milion requests, doubt someone will make that much with notes?
Docs
For media files
Funding
I'm happy to back some portion of development costs as a small donation ($300?) to make this happen and probably be the first user.
I can be reached at https://t.me/yangwao
Describe alternatives you've considered
sekund has some styling iirc, but some sense bit overcomplicated?
Additional context
https://github.com/mcndt/noteshare.space#deployment
Quick share has already close to 4k downloads, I guess this could be an interesting extension to cut costs as they might be only growing quite.
The text was updated successfully, but these errors were encountered: