How do I get really rid of postgres.app and related DBs & Users on yosemite?
I uninstalled completely, also related libraries.
After reinstalling the postgres.app 9.4.2.0the users, templates, tables are still there?!
Background:
I totally messed up and need to start the DB and Users from scratch.
But after re-installing postgres.app I still do see my messed up templates and schema?!
Ideas?
Found a "solution"
Since I messed up with brew and a direct install afterwards, brew also removed some relevant things... (as always). I re-installed with brew and will check my paths later, for now its working and rails stopped screwing things up.
Related
I was trying to install tensorflow, but it said it was already installed in anaconda, and I haven't been using anaconda navigator at all. I had installed anaconda a while ago, but I deleted it a while ago so wasn't sure why it was still there, guess I didn't delete it correctly. So I uninstalled it, and my entire Documents was gone on my computer. My theory is that the whole time I was in the anaconda virtualenv and didn't realize, so when I uninstalled it and all of it's dependencies it deleted my whole file system. Does anyone know how I could recover it?
Please explain how to fix this as you would explain to a 6month old child.
I tried redownloading anaconda hoping it would come back but it didn't. I don't mind using anaconda from here on forward but mainly just want my files back.
I'm trying to learn MySQL for a database course in which we use MAMP to set up the server. Everything was fine at first, but a few days ago I couldn't connect to MySQL with MAMP. In trying to solve this I removed both MAMP and MAMP PRO from my PC completely (instead of using the provided uninstaller). As a result I cannot reinstall MAMP as the installer still detects that I installed MAMP earlier and tries to uninstall it. In trying to fix my mistake I found that I still have references (I think they are .exe files) to MAMP and MAMP PRO in the windows apps section (. However when I try to remove them I get an error bar saying:
-) C:/MAMP/unins000.exe
and
-) cannot find file C:/MAMP/unins000.exe.
So I cannot remove said files, meaning that I cannot reinstall MAMP
I tried the MicrosoftProgram_Install_and_Uninstall and ccleaner first to install MAMP, however this resulted in the same error.
I also found some threads that show how to restore a file's directory through the command line, yet the problem with this is that I cannot find the directory of the remaining MAMP files.
As I'm not really into this field I have no idea of where to look to solve this. I'm however intrigued by this problem I would like to understand how this is possible and how to solve this.
In the end I would like to remove those MAMP references so I can reinstall MAMP.
Or (only if I really can't fix this) someone knows a similar program that works as well or better.
Due to my own idiocracy I have managed to run two versions of Apache on my Mac OS. Since a late update to Sierra my webserver has fallen into decay. I feel it is only a matter of time, until the whole environment breaks down and the OS is doomed for reincarnation.
For now I have managed to get my system side Apache running. However I have found that my "apachectl" command has been replaced with the brew version of apache. Since I am not strong with cmd line I want to ask how I can revert this? For now I am starting system side apache with "/usr/sbin/apachectl start".
If anyone could give me some advice how to keep the two versions from colliding, I would be more than grateful: keep brew apache from autoloading, check for which httpd processes are running and where they are rooted, put brew apache in a dumpster in the middle of the night etc.
I also have brew versions of php installed but I dare not to uninstall due to dependencies... any advide here would be appreciated as well.
IF ANY NEWCOMER READS THIS THREAD: Since I updated my Mac OS to the new Sierra my whole Apache configurations have gone mad. Unfortunately I have followed a very, very bad tutorial a few updates ago (https://www.getgrav.org/blog/macos-sierra-apache-multiple-php-versions) to configure my web development environment. I RECOMMEND EVERYONE TO AVOID THIS TUTORIAL! The blogger writes that his tutorial is only for advanced developers, however the tutorial itself is a total mess: there are no hints for any backup files and the configurations are all in bad style... I would advise anyone to double check on custom configurations in apache and always backup every file you change! For me it is too late and I feel only a hard reset of the system will suffice. Dark days on the horizon...
When you upgraded to the new OS, it does change your default apache config. The good thing is it does save a copy and renames it to httpd.conf~previous also creates a folder under etc/apache2/original for the previous default version. Just copy them back over and you're good to go.
Also you can throw homebrew in the dumpster using their own script
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"
Hope that helps.
I fool-hardily removed my system installation of gem. I was trying to get rbenv to work and was having some problems so I thought I could easily re-install all my Ruby stuff and start from scratch. This however is clearly not the case.
Any ideas short of breaking out the system disk would be appreciated.
I have tried uninstalling and reinstalling Xcode so it should behave normally but it keep open up with my last project and crash. No matter how many times i uninstall and reinstall. Is there a fix for this?? Please help i need to get this thing fix soon.
At the time of crash it says internal logic error. I read somewhere that i should restart my system after installing the new Xcode of it will crash again but as it gets installed it reopen automatically.
Thanks,
This might not be the optimal solution but I have talked to other people who have had problems like this and the solution they ended up doing was to create a new user on the Macintosh where they were having trouble and then Xcode worked perfectly fine.
Try that and see if you have any good luck.
I suspect there's some cached settings that aren't being cleared out with uninstalls & reinstalls.