[Building Sakai] Sakai quickstart with vagrant and puppet

Poindexter, David Ray davpoind at iupui.edu
Sun Feb 24 11:56:35 PST 2013


Just curious, why couldn't one pick SQLite for an option for quick starting some dev? It's well supported, and it's available on every platform.
--
David Poindexter
Systems Analyst
Enterprise Student Systems
UITS
Indiana University
535 West Michigan Street
Indianapolis, IN 46202-5157
O: 317.274.8686
W: http://uits.iu.edu<http://uits.iu.edu/>

From: Noah Botimer <botimer at umich.edu<mailto:botimer at umich.edu>>
Date: Saturday, February 23, 2013 7:11 PM
To: Zach Thomas <zach.thomas at gmail.com<mailto:zach.thomas at gmail.com>>
Cc: Sakai Dev <sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>>
Subject: Re: [Building Sakai] Sakai quickstart with vagrant and puppet

I think it is a very good idea for us to upgrade our DB pool. As far as I can tell, there is no reason we should be binding to DBCP (extending some of their classes) like we are anymore.

The DataSource interface is good at hiding this kind of thing (what/where/how you get a connection). The Tomcat pool, newer DBCP, and a few others are all reasonable choices. We should pick a nice, modern default, clean up our config pattern, and let people swap out easily if interested.

Zach, this is not to say you shouldn't do some clean/purge business to make a system install work more easily in the meantime. I just think we are way overdue on updating our most basic infrastructure (and the integrated version of DBCP has some pretty bad gotchas and a few performance issues).

Thanks,
-Noah

On Feb 23, 2013, at 6:35 PM, Zach Thomas wrote:

For some reason, the packaged version of Tomcat7 adds commons-dbcp and commons-pool to the Tomcat lib directory, which conflicts with the ones we deploy to shared/lib.

I got a clean startup as soon as I removed the packaged version of those libs.

Zach

On Feb 23, 2013, at 10:32 AM, Christian Seberino <cseberino at gmail.com<mailto:cseberino at gmail.com>> wrote:


what exactly is the problem encountered with the latest Tomcat package?

On Feb 23, 2013 3:19 AM, "Steve Swinsburg" <steve.swinsburg at gmail.com<mailto:steve.swinsburg at gmail.com>> wrote:
Yep it still applies unless you do more config tweaking.

Zach, post up what you have, maybe we can actually address it.

Cheers
Steve

Gesendent von meinem iPhone

On 23/02/2013, at 15:35, Christian Seberino <cseberino at gmail.com<mailto:cseberino at gmail.com>> wrote:

> On 02/22/2013 03:53 PM, Zach A. Thomas wrote:
>> P.S. As a side effect of this work, I found out why Sakai breaks[1] with the standard tomcat7 package available
>
> Is this *still* true with latest Sakai version?  If yes I won't try to
> use the Ubuntu tomcat7 package.
> Glad you mentioned something.
>
> cs
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130224/77ac11f5/attachment.html 


More information about the sakai-dev mailing list