Closed acviana closed 10 years ago
I realized that because I made the ticket you can't check the boxes. I'll think about if I want to change that or not because it also comes with other privileges such as push to the master branch which I wanted to restrict.
As for the build don't get the dev version, version 1.0 is the one you want: http://ssb.stsci.edu/ureka/1.0/
I forgot to mention, once you install ureka, install virtualenvwrapper -in- the ureka environment. Actually, do all your work in the ureka environment. Like this:
$ which python
$ echo $PATH
$ ur_setup
$ which python
$ echo $PATH
See the difference? Now run:
$ which virtualenvwrapper
$ pip install virtualenvwrapper --upgrade
$ which virtualenvwrapper
After installing virtualenvwrapper, run:
$ mkdir virtualenvs
$ cd virtualenvs
$ virtualenv mtpipeline-production
$ cd mtpipeline-production/
$ source bin/activate.csh
$ pip install numpy
$ git clone https://github.com/STScI-Citizen-Science/MTPipeline.git
$ cd MTPipeline/
$ python setup.py develop
I think we can close this ticket right?
Jim has not contacted me about MySQL yet. Tomorrow I will pass by the ITSD to solve this issue.
MySQL done! We can close this ticket now.
These are all the activities that are necessary to setup your machine for our project as well as some background reading. Please add any notes to the ticket you think might be useful for Kevin.
ITSD
mtpipe
unix group (support@stsci.edu). Cc: me so I can give them my approvalEnvironment
pip
to installvirtualenvwrapper
and read the docs (http://virtualenvwrapper.readthedocs.org/en/latest/). Use the following commands to do this:virtualenvwrapper
you can use this to build isolated development environments for you code. Let's say you're working on 2 features at the same time, Feature A and Feature B. Having a separate development environment ensures that your work on Feature A and Feature B stays separate until you merge them into the master branch (I'll explain all these terms soon). Let's go ahead and set up your first environment. We'll use this one for a copy of the production code: themaster
branch:Now check your
$PATH
variable as well as where yourpython
executable points as we did before to see what changed.master
branch let's put some code in it. Let's start by building our main dependency, cloning our github repository, and installing a development version of our code with the following commands:Background and Git Tutorial
git
tutorial: https://try.github.io/