streamster VS sserver

Have two of these labor of love, don't really care if it takes off types of projects right now.

First is Sonic Postcards - a digital postcard and playlist of my favorite music for the week. Pretty much doing it as an excuse to find new music, learn about the artists, and keep a writing habit going.

https://www.sonicpostcards.io/

Second is Streamster. OSS lib designed to make working with natural resource related APIs easier. Main goal being to provide an easier way to get the data and have it returned in a more consistent format. Allow devs to leverage the data and not spend all their mental bandwidth wrangling with it.

https://github.com/streamster/streamster

did not abandoned it since i am using for myself but didn't put any effort into marketing either other than mentioning it on hn few times https://github.com/newbeelearn/sserver . It's hHeadless server for hosting courses and associated blog/static content from private github repository.

I am working on creating a hosting server that can cater to landing page+blog+selling digital content with minimal maintenance overhead.

Beta version is ready here https://github.com/newbeelearn/sserver

I am looking for following

working on adding e-commerce functionality to my simple hosting server https://newbeelearn.github.io/sserver/

if you want to self host, give my product a try https://github.com/newbeelearn/sserver. It will auto-sync your static site from git repo.

I built something that will take care of the publish part but not the static site generation part here https://github.com/newbeelearn/sserver. Right now it only has one user i.e. me :-)

./sserver -token "$GITHUB_AUTH" -repo "https://github.com/newbeelearn/sserver.git?ref=gh-pages"

My plan is to add e-commerce functionality to it so that users can sell digital content i.e. books/videos/courses etc. through single config file in their github repository where the content is stored without needing to change their workflow.

If you would like any specific feature please let me know in the comments or create issue in the repository. Looking forward for your feedback.