Skip to content

Commit

Permalink
Intial Install
Browse files Browse the repository at this point in the history
  • Loading branch information
pfhenley86 committed Feb 12, 2014
0 parents commit 40b13d5
Show file tree
Hide file tree
Showing 1,101 changed files with 320,892 additions and 0 deletions.
1,833 changes: 1,833 additions & 0 deletions drupal-dev/CHANGELOG.txt

Large diffs are not rendered by default.

44 changes: 44 additions & 0 deletions drupal-dev/COPYRIGHT.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
All Drupal code is Copyright 2001 - 2013 by the original authors.

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.

This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.

You should have received a copy of the GNU General Public License
along with this program as the file LICENSE.txt; if not, please see
http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.

Drupal is a registered trademark of Dries Buytaert.

Drupal includes works under other copyright notices and distributed
according to the terms of the GNU General Public License or a compatible
license, including:

Javascript

Farbtastic - Copyright (c) 2010 Matt Farina

jQuery - Copyright (c) 2010 John Resig

jQuery BBQ - Copyright (c) 2010 "Cowboy" Ben Alman

jQuery Cookie - Copyright (c) 2006 Klaus Hartl

jQuery Form - Copyright (c) 2010 Mike Alsup

jQuery Once - Copyright (c) 2009 Konstantin K�fer

jQuery UI - Copyright (c) 2010 by the original authors
(http://jqueryui.com/about)

Sizzle.js - Copyright (c) 2010 The Dojo Foundation (http://sizzlejs.com/)

PHP

ArchiveTar - Copyright (c) 1997 - 2008 Vincent Blavet
42 changes: 42 additions & 0 deletions drupal-dev/INSTALL.mysql.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@

CREATE THE MySQL DATABASE
--------------------------

This step is only necessary if you don't already have a database set up (e.g.,
by your host). In the following examples, 'username' is an example MySQL user
which has the CREATE and GRANT privileges. Use the appropriate user name for
your system.

First, you must create a new database for your Drupal site (here, 'databasename'
is the name of the new database):

mysqladmin -u username -p create databasename

MySQL will prompt for the 'username' database password and then create the
initial database files. Next you must log in and set the access database rights:

mysql -u username -p

Again, you will be asked for the 'username' database password. At the MySQL
prompt, enter the following command:

GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER
ON databasename.*
TO 'username'@'localhost' IDENTIFIED BY 'password';

where

'databasename' is the name of your database
'username@localhost' is the username of your MySQL account
'password' is the password required for that username

Note: Unless your database user has all of the privileges listed above, you will
not be able to run Drupal.

If successful, MySQL will reply with:

Query OK, 0 rows affected

If the InnoDB storage engine is available, it will be used for all database
tables. InnoDB provides features over MyISAM such as transaction support,
row-level locks, and consistent non-locking reads.
44 changes: 44 additions & 0 deletions drupal-dev/INSTALL.pgsql.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@

CREATE THE PostgreSQL DATABASE
------------------------------

Note that the database must be created with UTF-8 (Unicode) encoding.

1. CREATE DATABASE USER

This step is only necessary if you don't already have a user set up (e.g., by
your host), or want to create a new user for use with Drupal only. The
following command creates a new user named 'username' and asks for a password
for that user:

createuser --pwprompt --encrypted --no-createrole --no-createdb username

If there are no errors, then the command was successful.

2. CREATE DRUPAL DATABASE

This step is only necessary if you don't already have a database set up
(e.g., by your host) or want to create a new database for use with Drupal
only. The following command creates a new database named 'databasename',
which is owned by the previously created 'username':

createdb --encoding=UTF8 --owner=username databasename

If there are no errors, then the command was successful.

3. CREATE SCHEMA OR SCHEMAS (Optional advanced step)

Drupal will run across different schemas within your database if you so wish.
By default, Drupal runs inside the 'public' schema but you can use $db_prefix
inside settings.php to define a schema for Drupal to run inside of, or
specify tables that are shared inside of a separate schema. Drupal will not
create schemas for you. In fact, the user that Drupal runs as should not be
allowed to do this. You'll need to execute the SQL below as a superuser,
replace 'username' with the username that Drupal uses to connect to
PostgreSQL, and replace 'schema_name' with a schema name you wish to use,
such as 'shared':

CREATE SCHEMA schema_name AUTHORIZATION username;

Do this for as many schemas as you need. See default.settings.php for
instructions on how to set which tables use which schemas.
31 changes: 31 additions & 0 deletions drupal-dev/INSTALL.sqlite.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@

SQLITE REQUIREMENTS
-------------------

To use SQLite with your Drupal installation, the following requirements must be
met: Server has PHP 5.2 or later with PDO, and the PDO SQLite driver must be
enabled.

SQLITE DATABASE CREATION
------------------------

The Drupal installer will create the SQLite database for you. The only
requirement is that the installer must have write permissions to the directory
where the database file resides. This directory (not just the database file) also
has to remain writeable by the web server going forward for SQLite to continue to
be able to operate.

On the "Database configuration" form in the "Database file" field, you must
supply the exact path to where you wish your database file to reside. It is
strongly suggested that you choose a path that is outside of the webroot, yet
ensure that the directory is writeable by the web server.

If you must place your database file in your webroot, you could try using the
following in your "Database file" field:

sites/default/files/.ht.sqlite

Note: The .ht in the name will tell Apache to prevent the database from being
downloaded. Please check that the file is, indeed, protected by your webserver.
If not, please consult the documentation of your webserver on how to protect a
file from downloading.
Loading

0 comments on commit 40b13d5

Please sign in to comment.