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
My interest in Jsi oblique. I'm neither C or Javascript programmer, so I didn't come in by the front door. I arrived here in my quest to find or build the kind of self hosting website that suits my own peculiar blend of idiosyncratic abilities and interest. Fossil's all-in-one-including-batteries wrapped in a single small executable is a marvel. It has and does everything I want, but is not what I want.
Fossil wasn't built in order to be a web content management tool, but in service of it's primary goal that was accomplished, and handily. However since the CMS part is a sideline and it's developers have no aspirations for it to be anything other than that it doesn't have a many features that full-on CMS do. Things like post tags and categories, order by publishing date, breadcrumb trails, automatic backlinks between posts the reference other, and so on.
I spent a fair bit of time learning fossil and it's Th1 scripting language and even developed a crude prototype home page for markdown embedded docs. Then I ran face first into a thick glass wall: there is no way outside of horribly abusing skin headers and footers to use such a script, without diving into the C code and creating my own fork. An enterprise beyond my present means.
I then spend a number of evenings working up my own powershell and then a python markdown index generator. I wrote my own since all the available ones I looked at target html as output, or are huge. Only to have the realization dawn that this too would be a long path: you can't just blindly grab snips of content because fragmentary tags lead to broken rendering, e.g. strike out the goes forever. A single problem marker for the many challenges I would have to re-solve that people more experienced than me have already solved.
This lead to another round of fitful searching, and uncovering the wonder that is Jsish. Jsi is only one of two* applications besides fossil I've run across that take the one-file-to-deploy and one-file-for-all-your-data paradigm to heart and really do something with it. And, and, it doesn't have a glass tcl-ish wall!
So, there's my long why I am here story. It remains to be seen if this will be my Goldilocks bed. I'm deep in dark unknown woods and there be bears, but I intend to give it a serious try.
* (The 2nd is Litestore: https://github.com/h3rald/litestore/. But it stores binary data in base64, thereby increasing size automatically by 33% they say. They should use fossil instead. ;-) I found both Jsish and Litestore via the fossil forum: 1, 2 )
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello world ;-)
My interest in Jsi oblique. I'm neither C or Javascript programmer, so I didn't come in by the front door. I arrived here in my quest to find or build the kind of self hosting website that suits my own peculiar blend of idiosyncratic abilities and interest. Fossil's all-in-one-including-batteries wrapped in a single small executable is a marvel. It has and does everything I want, but is not what I want.
Fossil wasn't built in order to be a web content management tool, but in service of it's primary goal that was accomplished, and handily. However since the CMS part is a sideline and it's developers have no aspirations for it to be anything other than that it doesn't have a many features that full-on CMS do. Things like post tags and categories, order by publishing date, breadcrumb trails, automatic backlinks between posts the reference other, and so on.
I spent a fair bit of time learning fossil and it's Th1 scripting language and even developed a crude prototype home page for markdown embedded docs. Then I ran face first into a thick glass wall: there is no way outside of horribly abusing skin headers and footers to use such a script, without diving into the C code and creating my own fork. An enterprise beyond my present means.
I then spend a number of evenings working up my own powershell and then a python markdown index generator. I wrote my own since all the available ones I looked at target html as output, or are huge. Only to have the realization dawn that this too would be a long path: you can't just blindly grab snips of content because fragmentary tags lead to broken rendering, e.g.
strike out the goes forever. A single problem marker for the many challenges I would have to re-solve that people more experienced than me have already solved.This lead to another round of fitful searching, and uncovering the wonder that is Jsish. Jsi is only one of two* applications besides fossil I've run across that take the one-file-to-deploy and one-file-for-all-your-data paradigm to heart and really do something with it. And, and, it doesn't have a glass tcl-ish wall!
So, there's my long why I am here story. It remains to be seen if this will be my Goldilocks bed. I'm deep in dark unknown woods and there be bears, but I intend to give it a serious try.
* (The 2nd is Litestore: https://github.com/h3rald/litestore/. But it stores binary data in base64, thereby increasing size automatically by 33% they say. They should use fossil instead. ;-) I found both Jsish and Litestore via the fossil forum: 1, 2 )
Beta Was this translation helpful? Give feedback.
All reactions