How We Deploy Python Code

#1

Post by spang » Thu, Jul 09, 2015, 10:30 PM UTC

How We Deploy Python Code
nylas.com

Re: How We Deploy Python Code

#2

Post by kbar13 » Thu, Jul 09, 2015, 10:41 PM UTC

http://pythonwheels.com/ solves the problem of building c extensions on installation.

Re: How We Deploy Python Code

#3

Post by Cieplak » Thu, Jul 09, 2015, 10:43 PM UTC

Highly recommend FPM for creating packages (deb, rpm, osx .pkg, tar) from gems, python modules, and pears.

https://github.com/jordansissel/fpm

Re: How We Deploy Python Code

#4

Post by ah- » Thu, Jul 09, 2015, 10:55 PM UTC

conda works pretty well.

Re: How We Deploy Python Code

#5

Post by sandGorgon » Thu, Jul 09, 2015, 10:59 PM UTC

The fact that we had a weird combination of python and libraries took us towards Docker. And we have never looked back.

For someone trying out building python deployment packages using deb, rpm, etc. I really recommend Docker.

Re: How We Deploy Python Code

#6

Post by sandGorgon » Thu, Jul 09, 2015, 10:59 PM UTC

The fact that we had a weird combination of python and libraries took us towards Docker. And we have never looked back.

For someone trying out building python deployment packages using deb, rpm, etc. I really recommend Docker.

Re: How We Deploy Python Code

#7

Post by daryltucker » Thu, Jul 09, 2015, 11:00 PM UTC

I see your issue of complexity. Glad I haven't ever reached the point where some good git hooks no longer work.

Re: How We Deploy Python Code

#8

Post by jedberg » Thu, Jul 09, 2015, 11:03 PM UTC

sandGorgon wrote: post #5

The fact that we had a weird combination of python and libraries took us towards Docker. And we have never looked back. For someone trying out building python deployment packages using deb, rpm, etc. I really recommend Docker.

There was a whole paragraph in the article about why Docker didn't work for them.

Re: How We Deploy Python Code

#9

Post by sophacles » Thu, Jul 09, 2015, 11:05 PM UTC

We use a devpi server, and just push the new package version, including wheels built for our server environment, for distribution.

On the app end we just build a new virtualenv, and launch. If something fails, we switch back to the old virtualenv. This is managed by a simple fabric script.

Re: How We Deploy Python Code

#10

Post by jlees » Thu, Jul 09, 2015, 11:06 PM UTC

Cieplak wrote: post #3

Highly recommend FPM for creating packages (deb, rpm, osx .pkg, tar) from gems, python modules, and pears. https://github.com/jordansissel/fpm

That seems like a neat tool. I wonder if you could combine it with the sandboxing that dh-virtualenv provides to get the best of both worlds?