<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment on Caktus Group</title><link>https://www.caktusgroup.com/tags/deployment/</link><description>Recent content in Deployment on Caktus Group</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 22 Aug 2023 11:22:07 +0000</lastBuildDate><atom:link href="https://www.caktusgroup.com/tags/deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating a Django Project from a GPU to a Convenience Image on CircleCI</title><link>https://www.caktusgroup.com/blog/2023/08/22/migrating-django-project-gpu-convenience-image-circleci/</link><pubDate>Tue, 22 Aug 2023 11:22:07 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2023/08/22/migrating-django-project-gpu-convenience-image-circleci/</guid><description>&lt;p>Recently we learned that as of &lt;em>September 30th, 2023&lt;/em> &lt;a href="https://discuss.circleci.com/t/linux-cuda-deprecation-and-image-policy/48568?mkt_tok=NDg1LVpNSC02MjYAAAGM6em0j1c6QSwAzSPHBw_kbCD6VmHwcrtr74I_yJ4R5W6GlyyUFsm1Qtv7LLzkwkVqvCeh2UqgD4lY4ZjnezxuvYUcc9HgZ2xXuihHBlv_45J_" target="_blank" rel="noopener noreferrer">several linux
images will be
deprecated&lt;/a>,
including the one we used, &lt;code>ubuntu-2004:202111-02&lt;/code>. Therefore, after
September 30th, our pipelines would have failed. To avoid this, we
switched several machines in our Django project from Ubuntu GPU images
to convenience images; This writing details that switch.&lt;/p></description></item><item><title>How to Simplify Django Migrations and Deployment</title><link>https://www.caktusgroup.com/blog/2021/05/25/django-migrations-and-deployment/</link><pubDate>Tue, 25 May 2021 17:34:09 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2021/05/25/django-migrations-and-deployment/</guid><description>&lt;p>&lt;strong>When removing fields from Django models, or adding non-nullable
fields, it can be hard to avoid a mismatch between code running on some
servers and the database in use.&lt;/strong>&lt;/p></description></item><item><title>5 Ways to Deploy Your Python Web App in 2017 (PyCon 2017 Must-See Talk 4/6)</title><link>https://www.caktusgroup.com/blog/2017/06/26/5-ways-deploy-your-python-web-app-2017-pycon-2017-must-see-talks-46/</link><pubDate>Mon, 26 Jun 2017 13:30:00 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2017/06/26/5-ways-deploy-your-python-web-app-2017-pycon-2017-must-see-talks-46/</guid><description>&lt;p>&lt;em>Part four of six in the 2017 edition of our annual &lt;a href="https://www.caktusgroup.com/blog/tags/pycon-must-see-series/">PyCon Must-See Series&lt;/a>, highlighting the talks our staff especially loved at PyCon. While there were many great talks, this is our team&amp;rsquo;s shortlist.&lt;/em>&lt;/p></description></item><item><title>Hosting Django Sites on Amazon Elastic Beanstalk</title><link>https://www.caktusgroup.com/blog/2017/03/23/hosting-django-sites-amazon-elastic-beanstalk/</link><pubDate>Thu, 23 Mar 2017 15:45:00 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2017/03/23/hosting-django-sites-amazon-elastic-beanstalk/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Amazon Web Services (AWS)' &lt;a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/Welcome.html" target="_blank" rel="noopener noreferrer">Elastic
Beanstalk&lt;/a>
is a service that bundles up a number of their lower-level services to
manage many details for you when deploying a site. We particularly like
it for deploys and autoscaling.&lt;/p></description></item><item><title>AWS load balancers with Django</title><link>https://www.caktusgroup.com/blog/2015/08/10/aws-load-balancers-django/</link><pubDate>Mon, 10 Aug 2015 12:00:00 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2015/08/10/aws-load-balancers-django/</guid><description>&lt;p>We recently had occasion to reconfigure some of our existing servers to use Amazon Web Services Elastic Load Balancers in front of them. Setting this up isn&amp;rsquo;t hard, exactly, but there are a lot of moving parts that have to mesh correctly before things start to work, so I thought I&amp;rsquo;d write down what we did.&lt;/p></description></item><item><title>AngularJS to PyGame: Caktus’ 2nd ShipIt Day</title><link>https://www.caktusgroup.com/blog/2013/04/30/caktus-2nd-shipit-day/</link><pubDate>Tue, 30 Apr 2013 13:00:00 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2013/04/30/caktus-2nd-shipit-day/</guid><description>&lt;p>We had our 2nd ShipIt Day at Caktus last week. ShipIt (coined
by &lt;a href="http://www.atlassian.com/company/about/shipit" target="_blank" rel="noopener noreferrer">Atlassian&lt;/a>), in case
you don&amp;rsquo;t know, is an exercise that allows your team to work on
alternative projects in a 24-hour hackathon. We brainstorm ideas related
to Caktus, break into small groups and try to build a project by the end
of the day on Friday. It&amp;rsquo;s a lot of fun and provides an opportunity to
work on internal tools, try something new and collaborate together. \&lt;/p></description></item><item><title>Testing Web Server Configurations with Fabric and ApacheBench</title><link>https://www.caktusgroup.com/blog/2011/09/13/testing-web-server-configurations-fabric-and-apachebench/</link><pubDate>Tue, 13 Sep 2011 18:16:33 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2011/09/13/testing-web-server-configurations-fabric-and-apachebench/</guid><description>&lt;p>Load testing a site with ApacheBench is fairly straight forward.
Typically you'd just SSH to a machine on the same network as the one
you want to test, and run a command like this:&lt;/p></description></item><item><title>Managing Client Expectations Amid Shifting Deadlines</title><link>https://www.caktusgroup.com/blog/2011/08/11/managing-client-expectation-amid-shifting-deadlines/</link><pubDate>Thu, 11 Aug 2011 20:30:33 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2011/08/11/managing-client-expectation-amid-shifting-deadlines/</guid><description>&lt;p>Estimating development time is notoriously difficult, and when moving
deadlines are added to the mix, shift happens.&lt;/p>
&lt;p>Estimating development time for clients is difficult enough without
having to second guess deadlines. Yet despite the best efforts, if your
company has a healthy deal flow, it&amp;rsquo;s almost inevitable that you&amp;rsquo;ll
eventually have a project deadline shift.&lt;/p></description></item><item><title>Basic Django deployment with virtualenv, fabric, pip and rsync</title><link>https://www.caktusgroup.com/blog/2010/04/22/basic-django-deployment-with-virtualenv-fabric-pip-and-rsync/</link><pubDate>Fri, 23 Apr 2010 00:46:37 +0000</pubDate><guid>https://www.caktusgroup.com/blog/2010/04/22/basic-django-deployment-with-virtualenv-fabric-pip-and-rsync/</guid><description>&lt;p>Deployment is usually a tedious process with lots of tinkering until
everything is setup just right. We deploy quite a few Django sites on a
regular basis here at Caktus and still do tinkering, but we've
attempted to functionalize some of the core tasks to ease the process.
I've put together a basic example that outlines local and remote
environment setup. This is a simplified example and just one of many
ways to deploy a Django project (I learned a lot from Jacob
Kaplan-Moss'
&lt;a href="http://github.com/jacobian/django-deployment-workshop/" target="_blank" rel="noopener noreferrer">django-deployment-workshop&lt;/a>),
so I encourage you to browse around the Django community to learn more.
The entire source for this example project can be found in the
&lt;a href="http://www.bitbucket.org/copelco/caktus-deployment/src/tip/example-django-project/" target="_blank" rel="noopener noreferrer">caktus-deployment Bitbucket
repository&lt;/a>.&lt;/p></description></item></channel></rss>