MongoHub installed on Mac OS X 10.6.8
program is having multiple problems (query, edit, add, delete) with database management.
anyone else experienced problems with MongoHub?
The original MongoHub 2.3.0 is no longer maintained and will crash on current versions of OS X.
The Fotonauts MongoHub fork (currently 2.7) that's mentioned on the official MongoDB site works as expected.
You can download Fotonaut's MongoHub.
If you use Eclipse, then you can try the MONJA who is an excellent plugin
Found robomongo. Absolute the best up until now. Has osx, linux and windows versions.
Related
I would like to be running the latest version of Apache on my MacBook PHP dev machine.
Since the upgrade to Sierra it is now at 2.4.23 which seems to be the most current. But that will likely change. When it does, is it possible to upgrade to the newest on the Mac? If so, how please?
Thanks
Mark
Update will come with the next upgrade of Mac OS. In this case, you can see this page: https://jason.pureconcepts.net/2016/09/update-apache-php-mysql-mac-os-x-sierra/
Apache is part of the OS and updates of this will be provided by App store of with software upgrades.
Alternative is using MacPorts. https://www.macports.org/
If you only want to stay up to date with the PHP part (and not Apache itself), you could take a look here: https://php-osx.liip.ch/
I can't install Xcode 4. I have some files that I need to open in Xcode 4. However, when I try to install it, it says "Xcode Install Assistant cannot be installed on this disk. The version of OS X is too new." How can I make it think I'm on Lion or Mountain Lion?
Here is a picture:
Download it in the App Store - it's the newest version and looks like the disc you have doesn't support Mavericks.
I feel tired of these preposterous answers. I think that if you want to stick to an older version of something, you should be able to. Also, I don't think software like XCode 4 are that old anyway.
But, to the point: I think XCode 4.6.3 is compatible with Mavericks. I am not sure about previous 4.6.X, but I think none of them work.
Any versions prior would require a previous operating system. I think you could try using pacifist to install the version you want, but I haven't found any guides.
If your problem is with project compatibility, in XCode 5 there is an option to save the project in a way it is compatible with XCode 4.6, and I suppose 4.6 offers a similar option to save in a version prior. Of course, you may need to adapt the code of the projects accordingly. Usually I try to stick with the Snow-Leopard-compatible code, because it compiles fine in all XCode 4.X and 5.X versions.
You can download any of these from the developer website.
I would try partitioning the disk and installing an older Mac OS X. I work with Snow Leopard and Mavericks in the same Mac. I usually do interface tasks in SL and the rest on Mavericks. The other advantage is that I have both XCode 4.2 and 3.2.6 in the same machine, so I can manage some backwards compatibility. =D
I had been using 2010 Macbook Pro for a while and had updated the Mac OSX to the latest version, and I had been suffering the slow speed for a long time. So last night I googled and do some cleanup , such as fix disk permissions, but the Mac was still slow. And someone suggest to re-install MacOSX.
I was thinking it was the new version of Mac OSX's problem, I had the same kind of problems happen on the 1st version IPad either.
After I reinstalled, the computer became much more faster. But I encountered the following problems:
JDK 7 DMG does not support OSX 10.6.8, but ONLY OSX 10.7+
Github official client does not support OSX 10.7+
Gooooooogled again and again, to solve the 1st problem, there are mainly to suggestions:
A. Using PackageMaker to remove the OSX version condition.
B. Using a tool Pacifist to open the pkg file inside the DMG file downloaded from official.
Since I have PackageMaker installed on Mac OSX, so I choosed A.
Open it with PackageMaker, remove the limitation, and build it again, I installed with the new pkg file successfully at:
/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home
And then set JAVA_HOME on ~/.bash_profile.
Then I download the glassfish 4.0 multi-language version, unzipped, and start-domain successfully. and finally the problem killed me for now.
After glassfish v4 started, I try to login into web console at:
http://localhost:4848
then glassfish server instance "dies", the java process of glassfish is still there, but without any response, the web console starting icon keeps rolling all the time. And there are no error logs created, and the "generated" directory is not generated.
2013-10-15 14:05:20.928 java[797:903] * NSInvocation: warning: object 0x1083c8390 of class 'ThreadUtilities' does not implement methodSignatureForSelector: -- trouble ahead
2013-10-15 14:05:20.930 java[797:903] * NSInvocation: warning: object 0x1083c8390 of class 'ThreadUtilities' does not implement doesNotRecognizeSelector: -- abort
Command start-domain failed.
That is the 1st problem.
The 2nd problem is about github. Since github official does not support OSX 10.6.8, I found an old installer with version 1.0.3. I installed this version, with one ONLY problem for now, I cannot login into github with username and password,no error responses, just no responding, I suffered this once I was on Windows. But I can work with clicking the "Clone into Desktop" button on github.com.
Can someone help me out? I am working on JDK7 based projects.
Why everybody is leaving Snow Leopard, and does not support it anymore, but old Mac computers should be die without working software after 2~3 years, just 2~3 years. And OS upgrade to nex t level will DOWNGrade the performance. Why this things happen?
Is it the oracle from god?
I had the same error (NSInvocation...), on my 2006 Macbook Pro (OS X 10.6.8), onto which I had installed JDK7 to develop a Java/GWT application in Eclipse Kepler. After searching around, I learned that one possible solution was to downgrade to JDK 1.7.0u25 (instead of update 40 or higher), so I installed that version alongside 1.7.0u45 (which I already had), and that fixed the problem. So I would recommend installing that version of the JDK and see if that fixes your problem.
I'm planning to buy Mac OS Lion, but I would like to know some informations.
- Are Snow Leopard's apps compatible with Lion?
- Are apps compiled with Xcode for Lion compatible with Snow Leopard? What if these app uses popovers/fullscreen which are features of Lion?
xCode requires a full download (the full 5*ish GB) and if you are a Java guy you will have to re download Java as it is not included (this was my experience when opening eclipse for the first time in Lion).
Some of Snow leopards apps are compatible, not all (ppc apps will not work). It is probably best to check with the software vendor first.
Another thing your Library folder disappears on an upgrade among some others where Lion is trying to 'Protect' its users. To get round this simply enter the command into terminal. (replace username with your username and foldertoreveal with the hidden foldername)
chflags nohidden /Users/Username/FolderToReveal
The upgrade process other wise has been fine. For reference I am an Obj C /C++ /C and Java developer. Hope this helps
Also will link you to this post about Developing Java on Lion:
Stack Overflow post on Java in Lion
A very good list of compatible applications is available at RoaringApps. I highly recommend checking for your favorite editors/IDEs/etc there.
Of note:
TextMate: "Works fine," but there are some issues
BBEdit: "Works fine"
iTerm2: "Works fine" (minor interface bugs)
And of course, Apple's tools require an upgrade to XCode 4.1.
As far as developing with the new APIs in Lion, you can explicitly target a specific version of OS X for compatibility. When building for 10.6, those new APIs will not be exposed during compilation and you will get warnings about unrecognized selectors if you try to use them.
So far what I've noticed :
- make sure you install XCode 4.1 (not the same as 4.0, it's a free separate download), which fixes the Python includes mess
- go to terminal and type "java", this will trigger the download of the Java runtime
But I chose to avoid the burden of fixing all libs by going with a clean install of Lion (from a USB key)
cvs stopped working for me, but downloading Xcode seemed like an unnecessarily heavyweight fix. Adding /Developer/usr/bin to my PATH fixed it for me.
I've spent some time today playing with getting the source for python 3.1.1 to build on my MacBook Pro using the --enable-framework and --enable-universalsdk options with no success. I will humbly admit that I have no real clue why I can't compile 3.1.1 on Snow Leopard, I did make sure to get the new Xcode version for Snow Leopard, and made sure I also installed the 10.4u SDK. It seems to be choking on the 10.4 SDK during the make stage, and has several error regarding headers for wchar, cursor, and ncursor during the configure stage. I have been able to get a make from a plain configure, and most the test pass, but that just isn't challenging enough. Has anyone else attempted to build python 3.1.1 on a Mac running Snow Leopard
There is an automated installer here: http://python.org/ftp/python/3.1.1/python-3.1.1.dmg
You need to set MACOSX_DEPLOYMENT_TARGET if you actually want to use an older SDK.
If you target 10.6, it may be that PPC building is not supported anymore, according to this bug report. In fact, that may be the case even if you target 10.4, using XCode 3.2 (haven't tried myself).
I don't have 10.6 installed yet so I can't say for sure it will work without issue but, in general, if you want to build a batteries-included framework build optimized for 10.6 of Python on OS X, you're best off using the installer build script in the source tree at Mac/BuildScript/build-installer.py after applying the patch in the bug report Martin referred to. Something like this should work [untested]:
./build-installer.py --sdk-path=/Developer/SDKs/MacOSX10.6.sdk --universal-archs=intel --dep-target=10.6 --src-dir=... --build-dir=...
That will build everything including dependent third-party libraries and the documentation but, be forewarned, you'll probably have to tweak things until you get it right and a few things aren't supported yet in 64-bit, most notably, tkinter. As mentioned above, the standard python.org 3.1.1 installer should likely work OK as long as you don't need 64-bit support.
[EDIT: I should clarify that, WRT 64-bit support, the problem isn't in tkinter, rather that the Apple-supplied versions of Tk in 10.5 and earlier were 32-bit only and so there was code in setup.py to prevent attempting to build a 64-bit version of tkinter on OSX. Perhaps that check can be removed now if the 10.6 Tk is 64-bit.]
Kenneth Reitz's soluton doesn't work for me. In fact, the install works fine but my default PATH still points to /usr/bin/python (v2.6.1.). I vaguely recall that we should be modifying our ~/.profile to point to /.../Frameworks and I expected the installer to do this for me (nope).
Anyway, /Library/Frameworks/Python.framework/Versions/3.1/bin exists so we could add it.
But I'm curious why the python bin in there does a crash and burn on me.
No time to resolve this now. Bye.