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
I'm setting up a cloned repo of SQLPage for myself very soon. Expect a few basic PR from me - mostly focusing on documentation first but maybe later a custom mermaid.js component or sample API calls. I consider myself more of a database guy with zero rust knowledge but I have a lot of system integration and architecture experience that might be helpful for your project.
Also my wishlist is just a subjective list of one person - with priorities based on my own use-case scenarios. I hope that more users will come forward with their own list. Once there is enough data a proper development roadmap can be built by combining the most requested features.
This also leads to another important point: Architecturally SQLPage is probably not in its final form. There are a few missing elements, such as include directives, that can be implemented many ways but needs to be decided to ensure consistency.
Several of these points have already come up in discussions with other users. The next big things on my list are OIDC authentication and multi database. For the latter, I'm still not sure how it should work...
Multi database is purposely not on my list - I think this is a problem that can be solved leveraging the capabilities of the database server and no need to overcomplicate SQLPage with an inferior workaround.
I already have a working solution to pull PostgreSQL server data via my MSSQL. I'll try to remove the company specifics and turn it into a some sort of documentation for SQLPage.
I already have a working solution to pull PostgreSQL server data via my MSSQL. I'll try to remove the company specifics and turn it into a some sort of documentation for SQLPage.
To tag on to this - is there a way for MSSQL to use windows authentication instead of passing a username/password? So any domain pre-authorized users can just open the pages and it works without using a specific username/password for the app
Could the CLI be more classical with options, instead of defaulting to starting the HTTP server? sqlpage --help, --version
So maybe sqlpage start | check | ...
Could you display the full urls like does miniserve (for instance) ?
Useful for shell clickable URL ;-) !
> miniserve .
miniserve v0.22.0
Bound to [::]:8080, 0.0.0.0:8080
Serving path /path/to/sqlpage
Available at (non-exhaustive list):
http://127.0.0.1:8080
http://<IP>:8080
http://[::1]:8080
Quit by pressing CTRL-C
Activity
lovasoa commentedon Aug 22, 2023
Wow, that's a great list ! Would you be interested in me guiding you to making your first contributions to sqlpage ?
f8dca commentedon Aug 23, 2023
I'm setting up a cloned repo of SQLPage for myself very soon. Expect a few basic PR from me - mostly focusing on documentation first but maybe later a custom mermaid.js component or sample API calls. I consider myself more of a database guy with zero rust knowledge but I have a lot of system integration and architecture experience that might be helpful for your project.
Also my wishlist is just a subjective list of one person - with priorities based on my own use-case scenarios. I hope that more users will come forward with their own list. Once there is enough data a proper development roadmap can be built by combining the most requested features.
This also leads to another important point: Architecturally SQLPage is probably not in its final form. There are a few missing elements, such as include directives, that can be implemented many ways but needs to be decided to ensure consistency.
lovasoa commentedon Aug 23, 2023
Several of these points have already come up in discussions with other users. The next big things on my list are OIDC authentication and multi database. For the latter, I'm still not sure how it should work...
f8dca commentedon Aug 23, 2023
Multi database is purposely not on my list - I think this is a problem that can be solved leveraging the capabilities of the database server and no need to overcomplicate SQLPage with an inferior workaround.
I already have a working solution to pull PostgreSQL server data via my MSSQL. I'll try to remove the company specifics and turn it into a some sort of documentation for SQLPage.
lovasoa commentedon Aug 23, 2023
Ideally, I'd like to find a good design that would allow implementing multi-database and dynamic user selection as a part of the same feature.
lovasoa commentedon Aug 23, 2023
That would be great ! Any contribution, even small, to https://github.com/lovasoa/SQLpage/tree/main/examples is very welcome.
powderdba commentedon Aug 24, 2023
To tag on to this - is there a way for MSSQL to use windows authentication instead of passing a username/password? So any domain pre-authorized users can just open the pages and it works without using a specific username/password for the app
powderdba commentedon Aug 24, 2023
It might already do that and I just haven't seen how to do it :) I've tried looking though I swear 😁 Also - love SQLPage! perfect for me 😄
jgranduel commentedon Sep 13, 2023
Could the CLI be more classical with options, instead of defaulting to starting the HTTP server?
sqlpage --help, --versionSo maybe
sqlpage start | check | ...Could you display the full urls like does miniserve (for instance) ?
Useful for shell clickable URL ;-) !
lovasoa commentedon Sep 13, 2023
About pagination, I answered here: #84
lovasoa commentedon Sep 17, 2023
I'm moving this to a discussion, but keeping track of it !