![]() ![]() Once you see that the server has started, open and run the setup wizard. Copy the MySQL Connector into the JIRA lib directory:.You can test it from the same tab and save your settings once you have a working database connection. In the second tab, configure the database as needed.This opens up a little swing app with a bunch of configuration options. In /var/atlassian/jira/current/bin, run config.sh.Since you already created the database itself, all you need to do is tell JIRA how to connect to it: Edit the file jira-application.properties and set the value of to /var/atlassian/jira/home.Go to /var/atlassian/jira/current/atlassian-jira/WEB-INF/classes/.This is identical to what is in the above Atlassian guide 8: That way, JIRA is always installed at /var/atlassian/jira/current, and when I upgrade I always know where it is and I can keep the previous application directory around in case I need to grab customized files. In my case, I unpacked it in /var/atlassian/atlassian-jira-6.3.13-standalone and created a symlink called current in the same directory. ![]() Here's what I did: Download and Unpack JIRA If your operating system is *nix-based (for example, Linux or Solaris), type the following in a console: $ sudo /usr/sbin/useradd -create-home -comment "Account for running JIRA" -shell /bin/bash jira If your operating system is Windows. It reads like the generic install overview was almost, kinda, updated for the Mac, but there are still sections like this: ![]() There is a guide for Installing JIRA on Mac OS X from Atlassian. % mkdir -p atlassian/jira/home atlassian/confluence/home 4 Install it, then set its path as your JAVA_HOME environment variable. Presuming you only have the default version of Java 6 (1.6.0_65) at /Library/Java/Home, go download the latest Java 7 or Java 8 SDK from Oracle. In addition, while you don't need to install MySQL as you may opt to use the local HSQL for both applications, I like being able to use the mysql client to see the data I'm using, and this makes it closer to my production setup. I'm (still) running OS X 10.9 Mavericks, so I can't guarantee these steps will work on Yosemite 3. There are no decent, authoritative guides out there on the Interwebs, so I thought I'd publish one myself. This setup works, but I incur a relatively high memory/CPU penalty, as well as the nutso overhead of resuming a VM, syncing the local clock each time, etc. I, on the other hand, was activley running both in separate ubuntu VMs in Parallels 2. I was happy to hear that most of the engineering team are Mac users as well, and that while it's not a production-worthy setup 1 it's regularly used by many Atlassians. We had a very productive discussion, and I remarked that both he and his colleague were using Macs with Confluence and JIRA running natively despite the lack of "official" support. Recently our Atlassian TAM stopped by for his quarterly visit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |