I agree Ansible is a good fit for your situation. Since Ansible works from yaml files, you don't have to write any Python 2.x compatible code as you would with Fabric.
On Mon Nov 17 2014 at 8:24:24 AM Brian Schott <bfsch...@gmail.com> wrote: > Ansible is a good choice. > > Sent from my iPhone > > On Nov 17, 2014, at 11:07 AM, Cal Leeming [iops.io] <c...@iops.io> wrote: > > There isn't really such a thing as a "deployment plugin", there are many > aspects to deployment workflow that should be considered. > > It really depends on how you are intending on deploying your application, > if you are dockerizing it then your CI system should be building the images > and pushing to a repository of your choice (docker hub, S3 etc). If you are > snapshotting on the hosting provider, then you can use packer.io and a > bunch of shell scripts. Pushing code to a single server via SSH isn't > really a scalable way to do deployment, and if this is what you are doing > then you might as well run a tmux/screen session on the server instead. > > Sadly other than Amazon Beanstalk and Heroku, both of which are > horrifically expensive, there isn't much in the way of choices. You can > look at dokku and deis, both of which are not considered stable for > production but use the same build pack idea as Heroku. > > If you want to go super ghetto, you should use a shell script which SSHs > into your "single use" box, issue a "docker pull" then restart the running > container. All of these things require a lot of plumbing work. > > Another approach would be to install python 2.6 in a venv (assuming you > have the relevant system libs) and run Fabric with that instead... In fact > putting fabric in its own venv is probably better because having fabric > inside your application space anyway would be considered cross > contamination (e.g. deployment tooling mixed in with application code). > This may feel weird at first, but once you get into the concept of > separating plumbing from application code, it feels more normal. If you do > this, use virtualenvwrapper to save headaches. > > If you're a JS guy, there's also a bunch of SSH tooling for node too, but > I can't give any personal recommendation on those. > > Cal > > > > On Mon, Nov 17, 2014 at 11:28 AM, Andreas Kuhne < > andreas.ku...@suitopia.com> wrote: > >> Hi all, >> >> We are just about ready to release our newly rewritten website. It is >> based on Django 1.6 and Python 3. >> >> We have worked through all of the problems with using python 3 (migrated >> some plugins ourselves, other plugins were updated during the course of the >> project). The only problem we have left is a good deployment plugin, so >> that we easily can deploy new versions of our site. >> >> We previously used fabric, but that doesn't work with python 3. So I was >> wondering if anyone has any python 3 compatible fabric alternative that >> they are using? >> >> Regards, >> >> Andréas >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-users+unsubscr...@googlegroups.com. >> To post to this group, send email to django-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CALXYUb%3DTpr7RfejfXs2H5vryg6vGp45_bbE%2Bp8tm%3D8CgQN2hzw%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-users/CALXYUb%3DTpr7RfejfXs2H5vryg6vGp45_bbE%2Bp8tm%3D8CgQN2hzw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAHKQagGz1tNLfdF09%3DcFBJaAWfBWFNbWCP%3DTANonGVkZSbvGfg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CAHKQagGz1tNLfdF09%3DcFBJaAWfBWFNbWCP%3DTANonGVkZSbvGfg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/4679766C-BFEC-4A96-A1D2-BDBD316053EE%40gmail.com > <https://groups.google.com/d/msgid/django-users/4679766C-BFEC-4A96-A1D2-BDBD316053EE%40gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAMFpZrjyV6JC_kjO9fypkVxbC5Uw7he3Do3QJJQJWQDLE5Obog%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
