DrupalCon Portland 2013

Cómo gestiona la universidad de Oregon sus más de 1.000 sitios creados con Drupal

Paul Lieberman  · 


PPT (pincha para descargar)



Extracto de la transcripción automática del vídeo realizada por YouTube.

good morning everybody thank you for getting up and awake and in here this morning this is a great turnout I am and welcome to Portland for those of you who haven't been here before so I'm Greg land Shay I am the track chair for the nonprofit government

and education track and so I am really excited to see this many people in here today this is this is fantastic so I'm here gonna introduce my friend Paul Lieberman here he is the lead developer and Drupal architect they get that right Paul okay good at

Oregon State University and he's been doing web stuff since well as long as there's been a web as a sysadmin and as a developer so I'm gonna turn the mic over to Paul and let him get started cuz he's much more interesting than I am so thank

you everybody good morning and welcome to Drupal con welcome to Portland I want to thank Greg for the introduction and also for his work and the drupal associations work in setting up this new track for government nonprofit and education a lot of us in education

been coming to Jubal con and attending bops and and there will be quite a few of those happening here I tend encourage you to attend but it's really nice to have this track for the first time dedicated to those of us in the public sector to have an opportunity

to share some of the things we're doing how's the volume back there okay thank you so you might have people are pointing to me yes okay I'm not in slideshow mode I'm not sure how that happened I thought I said do a slide show okay that's

better so as you might have gathered from Greg's introduction I've been doing this for quite a while and I'm actually I'm actually older than juries I don't know if you tell but I've been around long enough to know the DRI's didn't

actually invent the web the web was around before him what what juries brought to the table and Drupal brought to the table is a way for us to manage very large websites in in in a sane manner before that it really was chaos some of you that have been in education

for a while might remember what it was like it took some institutions about ten years just to convince the art department and the science department that they should use the same colors and that maybe we should use the same our school colors and use a a common

theme for the for the whole university that that was a struggle and fortunately we're beyond most of that now and with Drupal we have the tools to really move forward into a much much you know much better way of doing it so speaking of school colors that's

our our Drupal mascot there Oregon State where the Beavers and so we may be violating the Drupal Association of branding guidelines by using our color for the Drupal drop but but there it is and I want to apologize to the other OSU if there are any Buckeyes

in the audience when I say LSU I'm not talking about Ohio State I'm talking about Oregon State we are the Beavers I work for central web services at Oregon State University we provide Drupal hosting and custom application development and I have with

me today sheriff Anne and some of my other co-workers share does all of our Drupal training and user support and she's going to help with the questions that we'll have at the end I'm not going to stop her questions during the presentation I'm

going to just save those for the end also at Oregon State University I want to mention we host the the open source lab these open source lab have been doing his wonderful stuff in the open source world for quite a few years they host the mozilla foundation

the Apache foundation and the souther little group called drupal.org so drupal.org servers are right down in our server room right next to the servers that run our websites kind of a nice arrangement for us so well and the open source people are putting on

quite a few presentations here at Drupal con some of them are in the DevOps track one of them is right after this one so I would encourage you if you're interested in any of that to attend those sessions that way as well so what we're going to talk

about today is how su has been successful in deploying and managing Drupal a lot of our websites run on Drupal not all of them but certainly the majority so you know I think we've done quite well at it and but not everything you know his is really the

best way to be doing things we found things at work I'm going to talk about those things and then I'm going to talk about how we would like to be able to be doing some of it differently I'll we'll talk about what we're currently walking

working on and then some of the stuff we'll be looking at or that we have in development for the future it's supposed to be a technical session we're going to look at some snapshots of some code snippets I'm not going to get into any detail

on the code but all of the coders available for download following the links on the resources at the end of the slides so you'll be able to get the code take a look at it and death today I'm just mostly gonna skim over it pretty quickly because we

don't have time to really dive into that kind of stuff so we've done a lot of things right that have allowed us to scale what we've done is we've basically scaled I guess you could say scaled outward we have a lot of Drupal sites a lot of individual

Drupal sites some of them are quite large but we've mostly scaled by being able to support a large number of sites rather than put our emphasis on scaling a few really large sites although we're working on that now so in a lot of ways we've been

a victim of our own success in that it's been too easy just to create new Drupal sites whenever somebody wants them and eventually that catches up to you becomes more of a management nightmare and so some of the things we provide at Central web besides

the training we can do the site installs and the updates automated backup database backup we provide the support for Drupal here are the numbers once again this this this isn't really meaningful in the sense that this is you know great we have this many

Drupal sites we have this many Drupal sites we can support this many Drupal sites keep them updated keep them secure but we really don't want this many Drupal sites we got there because we created a system that supported that and it worked really well

and people wanted that everybody comes I want to do plus I'd sure here was a Drupal site we now we have to start having the conversation well aren't you really part of this other Drupal site over there we're just beginning to look at that kind

of thing we we collaborate within the university a lot of the colleges host their own infrastructure but they run our distribution of Drupal we communicate with our marketing excuse me we collaborate with our marketing and web communications team they have

designers and we have developers so we build the themes in conjunction with them and we have gotten it to where we have just a couple of very of standard themes that have our branding and that we're using across the whole Drupal environment so we put together

an application to manage this thing we call it web Manish it was written many years ago I wasn't involved it was written in an older version of Ruby on Rails and what it does is it lets us manage basically the departments we call them the site owners and

the authors and it creates the Apache V host configuration sets up the distribution directory sets up file permissions on the like sites default files or sites files handles the database creation and unremovable under you remove sites and handles the Drupal

installs and bucks and bulk site updates now we've talked this app is getting kind of old and you know we talked about should we put our development effort into maintaining this improving it making it better having to do all the things we would like it

to do and we decided against that that this was an in-house application suited our needs there wasn't the kind of thing that was going to really work for a much larger audience and so we're we decided to shelve this thing and let's put our development

effort in the community project and so that's where we're looking to go with it right now so if you've set up tuple multi-site for you're familiar with this with this picture here basically with Drupal multi-site you create a Drupal directory

that's where your core files are you'll have a sites all that's where your shared modules and themes will go and then every site has a sites directory under under the site's directory so in this picture I've got site wall inside too and

they all have if they have custom modules or themes and their files I don't show that in this picture all go in those directories that's the standard Drupal multi-site directory structure it works it works best if you have subdomains like in this example

site one college.edu situ college.edu it does not work as well if you have sub directories like college did I need to use slash site once last site to you can make it work it involves creating some symlinks out at the at the root of your drupal files so it's

it's limited in how well it scales from from my experience anyhow I'm sure some people have made it scale quite large but we found a different way of doing it which is we have one instance of the Drupal core files and the sites all that we then symlink

to the site's directory which which can be anywhere so we're not we don't have to create the site's directory under Drupal core sites we create them anywhere in our web tree and we sim link to the Drupal core files so each tuple site thinks

it's it's own Drupal site and just use the site's default for its files and its settings and the thing about this is it scales quite well when I first saw it I kind of scoffed at it and said well listen this is wrong this isn't the way Drupal

[ ... ]

Nota: se han omitido las otras 4.990 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.