Open
Conversation
Only tested uv tool deps with postgres, can also be installed just fine with extras, e.g. `uv tool install sqlit-tui[ssh,postgres]`... In most cases it's probably preferred to use the extra, but can still be useful to install independently with `-w`, for example, if you want to build against system postgres libs (e.g. using `psycopg2` in place of `psycopg2-binary` for a command like `uv tool install sqlit-tui[ssh] -w psycopg2`). Not sure if setting SQLIT_CONFIG env will fully prevent `~/.sqlit` dir from cluttering up homedir, but seems to work well enough in my case. Should probably be codified as a default option for linux though.. I've never met anyone who wanted config dirs cluttering up their home dir. :)
Looked fine until I opened it up in web UI. :)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some basic instructions to use standard xdg-compatible config dirs, and a couple
uv tool installoptions. Realistically, I think it'd probably be good to just go for using~/.config/sqlitby default for linux anyways, even if not worrying too much about following the xdg spec to the letter. Some people get irrationally annoyed when projects dump stuff in their homedir (not me of course 😉) and it's always better to be ahead of it becomes a load-bearing barnacle, so to speak.Arch wiki even has a hall of shame, haha:
https://wiki.archlinux.org/title/XDG_Base_Directory
BTW, awesome project. I've been using the
dbclitools for years (litecli,pgcli, etc.) and this is probably gonna supplant that pretty quickly. Will be nice to fight less with the pager for sure...I think I may even be the first person to have pulled your new neovim plugin too, lol.In any case, feel free to use or not use this however you want! I just figured having this mentioned in the docs might save others from having to dig to get sqlit to stop dropping config in their home dir, and maybe also nudge you toward changing the defaults a bit. Thanks!!