-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Fossil database features as part of archive "filesystem" or as objects in runtime. #40
Comments
I was working towards something like that. For example, Bootstrap-Vue was added to the binary. However, I've come to the realisation that putting all that in into jsish is not feasible. Instead I'm developing a separate project to provide that kind of functionality. Hopefully have something to show in a few weeks. |
I have a prototype that works as a technology demo using jsish + fossil repo. It serves up an AdminLTE (free Javscript UI template) that integrates with the Vue and uses npm build tools for integrating into a CI/CD pipeline. I was considering releasing to you as a separate 'application template' fossil, but i figure you have more time than i do, so here is it in its current state. The goal is to
Here is my demo: https://github.com/timoc/jsish-vue-element-admin Here is a cut-n-paste to running demo:
or if that does not work, check the original preview. |
Was away for a while so I've only glanced at it, but very cool! |
I have not had a chance to do more with it. Is there any extensive documentation or commented examples on how to use the web-server component? |
Jsish was originally developed for replacing Tcl in embedded devices. So no there is no other documentation. |
I would like to be able to use a fossil repository features when using a fossil archive, as out of the box user generated CMS capabilties. Essentially issues, wiki, chat & forums - as they can be used to capture feedback that can synchronized and fed back to the developer, or allow me to use jsish to glue-code fossil features to external issue trackers/3rd party tools etc.
The text was updated successfully, but these errors were encountered: