I tried installing postgres on my mac using homebrew.
It's not working.
How do I remove what homebrew put in for me?
Thanks.
How about 'brew list' to see what you installed and 'brew remove [your-program]'? I guess this is all in the brew manpage. And even more info on this page about PostgreSQL on OS X.
Related
At the moment I need to install and run DeepSpeech on my local.
Can someone help me how with installing DeepSpeech on my Mac. I have already installed Python 3.10.0 but it seems like this version do not work with DeepSeech
I have problems installing Postgres on my MacBook M1
The Downloaded Installer is failing (Error in Postprocessing) from www.enterprisedb.com and when I try it with "Port" it is not working (it installs, but doesn't install executables like "pg_ctl")
Is there a solution?
(10 years ago I´ve downloaded the source and compiled it)
Nowadays I would suggest same like Calin's comment:
Install using Homebrew
brew install postgresql
As you can see on brew.sh when searching for formula postgresql it has binaries (Bottle) supporting:
Apple Silicon (M1) on macOS Monterey
See also:
Installing Postgres via Brew (OSX)
Installing Postgres with brew in 2 easy steps – An Integrated World
postgresql not installed but homebrew reports it is
I'm using MacOS Monterey 12.4 Intel chip, and trying Postgresql installation from
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads I think every version for Maos.
every installation attempt turned out the same, the program crashed as soon as it wanted to choose a password, while entering any character.
can anyone help me to install?
I am having the same issue on a 2020 M1 Macbook on MacOS Monterey 12.2.1 when I try to install 14.3. I get all the way to the Provide password for database superuser. Then once entering a password the program crashes. I'll probably end up using the postgresapp version until this is fixed. The latest version of the app (14.3) is universal so it should work with the m1s (if anyone else has this problem with m1). That is the best solution I've got so far.
Edit: You may want to try installing with Homebrew as well. https://formulae.brew.sh/formula/postgresql#default. I'm going to try this later.
Before upgrading to Mac OS Catalina. MAMP was working fine. After upgrading it to Mac OS Catalina, MAMP 5.5 stopped working. So I decided to uninstall and re-install. But When I tried to install it (fresh), The installation fails. Please somebody guide me to resolve this. Thank You.
This is specific for your pc and we don't have as much info as we would like.
You have to check these settings that thay mention on their docs before installing and follow their guide.
If that seems frustrating, i would suggest to use bitnami mamp that solves issues regarding the enviroments
Too few information to identify the problem, some suggestion you could try
1. Check if the software is fully uninstall, some software often remain some package or config
2. Using another server stack like Wamp, xamp, ampp ...
I am using rails 3.1rc4 with paperclip and i cannot upload any image file with. I keep getting this error
Image D:/Users/MOBILE/AppData/Local/Temp/stream20110612-3872-y7hmme-0.jpg is not recognized by the 'identify' command. I have imagemagic installed. But it works in <= rails 3.0.8rc4.
I'm on Mac and I had the exact same problem after I updated to Mac OS Lion,
in order to fix this error I had to reinstall imagemagick
This might help other Mac OS Lion users:
First make sure to download the latest XCode from the app store (4.1 atm I believe, it's free)
Using Homebrew:
brew uninstall imagemagick
brew update
if you get any errors, clean up files ending in .a or .la with "brew doctor",
then just do
brew install imagemagick
If you are using MacPorts do:
port uninstall imagemagick
port selfupdate
port install imagemagick
I am not sure if this will adress your specific issue but I found this and maybe its related:
https://github.com/thoughtbot/paperclip/issues/481
It states:
The paperclip:refresh:metadata rake task fails with Rails 3.1 as ActiveRecord no longer supports instance.save(false) - you must now use instance.save(:validate => false) instead.