Byebye Buildout

[Grischa]

Hi All

I've been waiting for this day for a while, and now I am finally taking the plunge.

Buildout is going to disappear from the develop branch in the next few days. So, beware when you git pull or start a new installation from the develop branch.

I will post a set of deployment instructions and update the docs eventually, as well as the mytardis-salt scripts, all before it hits the master branch.

The biggest change will be that it is now wise to use a virtualenv.

I already tested this with supervisor and it works fine. If you use anything else to run gunicorn you may have to look up how to make it work with a virtualenv.

setup.py will also disappear, unless anyone shouts that they are using MyTardis as a library. The only installation I am aware of doing that is going to merge their app into MyTardis soon.

I will send another message with more details when the transition is complete. In the meantime feedback is welcome.

Cheers

[Steve Bennett]

Hooray!

Well, I'm not doing anything with MyTardis these days, but I'm still excited. Buildout sucked. :) What was it, you ended up needing Salt, Bootstrap, Buildout, Pip, Ezy Setup, and Setup Tools all to do different parts of the setup?

Steve

--
You received this message because you are subscribed to the Google Groups "tardis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tardis-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Grischa]

Hooray, it's done!

Yeah, it sucked, Steve, especially because we didn't really need all its complexity.

I replaced it with ... pip!

The new way to install dependencies is pip install -r requirements.txt

The new way to run django commands is python mytardis.py or ./mytardis.py if you chmod +x it.

The new way to test is python test.py

These tests are now run on Semaphore https://semaphoreapp.com/mytardis/mytardis because it uses Ubuntu 14.04.

The new way to deploy it is still in development. The file build.sh has a rough outline of what needs to be done.

I'll update the salt scripts over the next couple of weeks. I will also update the documentation then, too.

Please beware of those changes when updating your develop branch now, nothing will work as it used to. If anything doesn't work or I forgot to post instructions here, please shout!

[Carlo Hamalainen]

On 09/02/15 17:17, Grischa wrote:

The new way to install dependencies is pip install -r requirements.txt

I tried the pip install this morning but it gets stuck on 'compare':

No distributions matching the version for compare (from -r requirements.txt (line 11))
Exception information:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main
    status = self.run(options, args)
  File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 290, in run
    requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle)
  File "/usr/lib/python2.7/dist-packages/pip/req.py", line 1178, in prepare_files
    url = finder.find_requirement(req_to_install, upgrade=self.upgrade)
  File "/usr/lib/python2.7/dist-packages/pip/index.py", line 322, in find_requirement
    raise DistributionNotFound('No distributions matching the version for %s' % req)
DistributionNotFound: No distributions matching the version for compare (from -r requirements.txt (line 11))

I put the full log here: http://carlo-hamalainen.net/tmp/2015-03-04-1019-pip.log.txt

Any ideas?

-- Carlo

[Grischa Meyer]

I found that I need to update pip sometimes.

pip install -U pip

Does that fix it?

--

[Carlo Hamalainen]

On 04/03/15 10:26, Grischa Meyer wrote:
> I found that I need to update pip sometimes.
> pip install -U pip
>
> Does that fix it?

Yes, thanks.

-- Carlo