Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/calavera/trinidad-dbpool
Database connection pool for Trinidad
https://github.com/calavera/trinidad-dbpool
Last synced: about 2 months ago
JSON representation
Database connection pool for Trinidad
- Host: GitHub
- URL: https://github.com/calavera/trinidad-dbpool
- Owner: calavera
- License: mit
- Created: 2010-03-23T23:40:46.000Z (almost 15 years ago)
- Default Branch: master
- Last Pushed: 2011-02-03T15:28:51.000Z (almost 14 years ago)
- Last Synced: 2024-10-05T21:47:25.443Z (3 months ago)
- Language: Ruby
- Homepage: http://github.com/calavera/trinidad-dbpool
- Size: 1.72 MB
- Stars: 4
- Watchers: 2
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.rdoc
- Changelog: History.txt
- License: LICENSE
Awesome Lists containing this project
README
= trinidad-dbpool
Trinidad extensions to support database connection pools configured into the Apache Tomcat
container.== Pools supported
* MySql (trinidad_mysql_dbpool_extension)
* PostgreSQL (trinidad_postgresql_dbpool_extension)== Usage
* Install the extension gem, ie: jruby -S gem install trinidad_mysql_dbpool_extension
* Configure the pool into the trinidad's configuration file, ie:web_apps:
default:
extensions:
mysql_dbpool: # EXTENSION NAME AS KEY
jndi: 'jdbc/TestDB' # jndi name
username: 'root' # database username
password: 'root' # database password
url: 'jdbc:mysql://localhost:3306/javatest' # database url
maxActive: 100 # max nodes actives
maxIdle: 30 # max nodes idles
maxWait: 10000 # max nodes waiting_jndi_, _username_, _password_ and _url_ are mandatory, while other
configuration options can be found here:http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html
http://commons.apache.org/dbcp/configuration.html
* Configure your rails application to use jndi into the config/database.yml
production:
adapter: jdbc
jndi: java:/comp/env/jdbc/TestDB
driver: com.mysql.jdbc.Driver # jdbc driver is mandatory== Note on Patches/Pull Requests
* Fork the project.
* Make your feature addition or bug fix.
* Add tests for it. This is important so I don't break it in a
future version unintentionally.
* Commit, do not mess with rakefile, version, or history.
(if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
* Send me a pull request. Bonus points for topic branches.== Copyright
Copyright (c) 2010 David Calavera. See LICENSE for details.