Ideally with a unique port each time I run an instance, the files stored locally in a `db_data` folder, and a simple CLI + maybe UI to read, edit, and delete the data.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Agree completely. This setup is my least favorite part of local dev
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
True, but now everyone needs to install Docker, have it’s service running, regularly clean up gigabytes of space, etc. Closer for sure, but not there yet.
- Show replies
-
-
-
Why isn't docker run -d postgres not good enough?
-
I should try it again, but my experience running a Docker-based app in production has been that it becomes yet another tool to manage. Everyone needs to install it, learn its CLI, clean up gigabytes of space from time to time, etc.
- Show replies
New conversation -
-
-
This is one of the reasons sqlite is so easy to use
-
Agreed, but I definitely want to use Postgres since that’s what I’m using in production.
- Show replies
New conversation -
-
-
Nixpkgs is pretty close to that: nix-shell -p postgresql export PGDATA=./db_data pg_ctl init pg_ctl start psql In a different project dir you could use, say, postgresql96 and they wouldn't conflict. Edit db_data/postgresql.conf to tweak ports and logging.
-
Interesting, thanks for sharing! The key point though is I don’t want my team to all install, learn, and maintain yet another tool.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.