Online training June 11, 12: Docker pa ckaging best practices for Python in production
"Itamar Turner-Trauring" <[email protected]> Fri, 22 May 2020 11:48:01 -0400
| Newsgroups | gmane.comp.python.org.uk |
|---|---|
| Message-ID | <[email protected]> |
--===============1620769913839202642==
Content-Type: multipart/alternative;
boundary=9952f0e7e778488d99f2b5855c960957
--9952f0e7e778488d99f2b5855c960957
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
You=E2=80=99re about to ship your Python application into production usi=
ng Docker: your images are going to be critical infrastructure.
And that means you need to follow best practices=E2=80=94if you don=E2=80=
=99t, you risk wasting quite a lot of money:
* You don=E2=80=99t want to waste hours every week waiting for slow bui=
lds.
* Or even worse, you might have a production outage or security breach,=
costing your company orders of magnitude more money.
So how can you ensure your Docker image packaging isn=E2=80=99t wasting =
your team=E2=80=99s time? How can you ensure you=E2=80=99re following be=
st practices, for security, efficiency, and debuggability?
*Live, online training on Docker best practices specifically for Python =
running in production*
Based on many years experience using Docker, and a over a year's worth o=
f research into best practices for Docker packaging of production Python=
applications <https://pythonspeed.com/docker/> (https://pythonspeed.com=
/docker/), I am teaching a live online class on Docker best practices fo=
r Python.
You'll learn:
* Security best practices.
* Make your images identifiable and builds reproducible.
* Python-specific details on packaging and debugging.
* Creating smaller images while still having fast builds.
* And much more!
The class involves plenty of hands-on activities!* *You'll be typing alo=
ng with me as I demonstrate live how everything works (and occasionally =
make a mistake, so you can see how I recover from it). You'll also get t=
o do hands-on exercises to help you solidify your understanding.
*The class will take place on two afternoons (UK time) on June 11th and =
12th. You can **learn more about the class on the event page* <https://w=
ww.eventbrite.com/e/production-ready-docker-packaging-for-python-develop=
ers-tickets-106092599822>* (*https://bit.ly/36kBhhN).
=E2=80=94Itamar
--9952f0e7e778488d99f2b5855c960957
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>You=E2=80=99=
re about to ship your Python application into production using Docker: y=
our images are going to be critical infrastructure.<br></div><div><br></=
div><div>And that means you need to follow best practices=E2=80=94if you=
don=E2=80=99t, you risk wasting quite a lot of money:<br></div><div cla=
ss=3D"has-user-generated-content"><div class=3D"structured-content-rich-=
text structured-content__module l-align-left l-mar-vert-6 l-sm-mar-vert-=
4 text-body-medium"><ul><li>You don=E2=80=99t want to waste hours every =
week waiting for slow builds.<br></li><li>Or even worse, you might have =
a production outage or security breach, costing your company orders of m=
agnitude more money.<br></li></ul><p>So
how can you ensure your Docker image packaging isn=E2=80=99t wasting yo=
ur=20
team=E2=80=99s time? How can you ensure you=E2=80=99re following best pr=
actices, for=20
security, efficiency, and debuggability?<br></p><h3><br></h3><div><b>Liv=
e, online training on Docker best practices specifically for Python runn=
ing in production</b><br></div><p>Based on many years experience using D=
ocker, and a over a year's worth of research into <a href=3D"https://pyt=
honspeed.com/docker/" target=3D"_blank" rel=3D"nofollow noopener norefer=
rer">best practices for Docker packaging of production Python applicatio=
ns</a> (https://pythonspeed.com/docker/), I am teaching a live online cl=
ass on Docker best practices for Python.<br></p><p>You'll learn:<br></p>=
<ul><li>Security best practices.<br></li><li>Make your images identifiab=
le and builds reproducible.<br></li><li>Python-specific details on packa=
ging and debugging.<br></li><li>Creating smaller images while still havi=
ng fast builds.<br></li><li>And much more!<br></li></ul><p>The class inv=
olves plenty of hands-on activities!<b> </b>You'll
be typing along with me as I demonstrate live how everything works (and=
occasionally make a mistake, so you can see how I recover from it).=20
You'll also get to do hands-on exercises to help you solidify your=20
understanding.<br></p><div><br></div></div></div><div><b>The class will =
take place on two afternoons (UK time) on June 11th and 12th. You can </=
b><a href=3D"https://www.eventbrite.com/e/production-ready-docker-packag=
ing-for-python-developers-tickets-106092599822"><b>learn more about the =
class on the event page</b></a><b> (</b><a href=3D"https://bit.ly/36kBhh=
N">https://bit.ly/36kBhhN</a>).<br></div><div><br></div><div>=E2=80=94It=
amar<br></div></body></html>
--9952f0e7e778488d99f2b5855c960957--
--===============1620769913839202642==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
python-uk mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-uk
--===============1620769913839202642==--