veyepar: Outsourcing your webapp maintenance to Debian

Author(s):	Francois Marier
Location	Room 329
Date	aug Fri 29	Days Raw Files
Start	14:30	First Raw Start	14:19
Duration	00:45:00	Offset	0:10:19
End	15:15	Last Raw End	15:19
Chapters	00:00
Total cuts_time	41 min.

https://summit.debconf.org/debconf14/meeting/16/outsourcing-your-webapp-maintenance-to-debian/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

assets release.pdf Outsourcing_your_webapp_maintenance_to_Debian.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Today's web applications often have a lot of external dependencies. Start off with a basic framework, sprinkle a couple of handy modules and finish with a generous serving of JavaScript front-end libraries.

What you end up is a gigantic mess of code from different sources which follow very different release schedules and policies. Language-specific package managers can automate much of the dependency resolution and package installation, but you're on your own in terms of integration and quality assurance. Also, the minute you start distributing someone else's code with your project, you become responsible for the security of that third-party code.

We moved away from statically-linked C/C++ programs a long time ago and now (mostly) live in a nicely-packaged shared library world. Can we leverage the power of Debian (i.e. the great work of the package maintainers and security team) to similarly reduce the burden of those who end up having to maintain our webapps?

This talk will examine the decision that the Libravatar project made to outsource much of its maintenance burden to Debian by using system packages for almost everything.

Comment:

production notes