Closed frankcollins3 closed 1 year ago
zsh: command not found: pg_ctl β ~ π β ~ pg_ctl -D /usr/local/var/postgres status
zsh: command not found: pg_ctl β ~
π β ~ pg_ctl -D /usr/local/var/postgres status // this chatGPT provided command did not do the trick but thank you AI
[1:06am]
calling it tight and removing version 15 to use version 14 right now after these short messages [1:07am]
think it could've been: an input during the installation process that asked to specify the location to which postgres installed.
I asked chat and it instructed the path to be: /usr/local/pgsql/data
// this path seemed legitimate.
[1:33am]
terminal is being a little iffy but otherwise executing:
$ brew update turned the iterm tab title to: brew git but it was doing nothing.
$ brew install postgresql@14 this command changed it to a few times to titles like: brew sw and another 2 or 3 letter word after brew updating Homebrew...
[1:44am]
installing it through brew that way wasn't working either. instead downloading 14.8 from the site.
as expected, ran npx kill-port 5432 as well through node which does nothing because psql is not connected to node [2:03am]
this computer is not the slowest but not the fastest and already noting the: "Verifying postgresql-14.8-2-osx" is going much faster than verison 15 [2:08pm]
the 2nd window is the one mentioned above. the /data/postgres path was empty chat provided that above mentioned path which is not this one.
[2:12am]
attempting to do: reiterate an already created application that depends on tools like: react-express, redux, graphQLExpress and finish it with NextJS, @redux/toolkit, graphql-apollo-server-micro
error:
proposed approach: could be this 09 imac with unsupported High Sierra (other imac blew doing a self-repair) // already considered just using the heroku connection string but that'd make testing routes and submitted data slower. // actually debating that now that I write that. if the data can't be seen from heroku dashboard there's no point. // would still prefer to have local postgres until the use of the connection string which will be sooner than later.
0: approach 0 which is the fallback approach is to just use postgres. not a bad idea since all routes work, just have to make them in NextJS
1: ask chatGPT
2: download 14.8 (already wanted to do that as well but went for it anyways) ... the other computer that blew was a 2012 with high sierra. it Blew when upgrading to Mojave to use nextjs with compatible packages.