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
For installation and usage improvement, how about implementing / documenting workflow using sqlite ? It might be good enough for most usage, and would require less setup effort.
For example have the file path in the config, and let gryphon automatically create it. Security will be managed by the user, via file permissions, so no DB knowledge needed.
Sounds nice to me, but what is everyone thinking about it ? Can there be some potential drawbacks ?
The text was updated successfully, but these errors were encountered:
This is a great idea if it works and might simple to implement for an enterprising contributor!
The only thought off the top of my head is whether sqllite will be a perfect drop-in replacement for mysql. I haven't worked with sqllite before so I don't have an intuition on this, there are some places where gryphon makes raw sql queries or uses some second-level features of mysql, I'd want to have some way of making sure that functionality still works. Maybe this would just mean shipping sqllite functionality with a new db unit test suite.
I thought I'd start with the simple one, and I had a quick shot at changing the dashboard DB with sqlite. Just a few changes are needed (parameters for sqlalchemy engine initialization) but that is pretty much it. I ll try to understand tests and I ll send a PR for this DB first.
For installation and usage improvement, how about implementing / documenting workflow using sqlite ? It might be good enough for most usage, and would require less setup effort.
For example have the file path in the config, and let gryphon automatically create it. Security will be managed by the user, via file permissions, so no DB knowledge needed.
Sounds nice to me, but what is everyone thinking about it ? Can there be some potential drawbacks ?
The text was updated successfully, but these errors were encountered: