Databases Reference
In-Depth Information
We ensure that the permissions and ownership of the directory and files are
appropriate for our web server; the web server user or group must be able to
read them.
Installation on Local Windows Servers
(Apache, IIS)
The procedure here is similar to that described in the
Installation on a Remote Server
Using a Windows Client
section, except that the target directory will be under our
DocumentRoot
(for Apache) or our
wwwroot
(for IIS). Of course, we do not need to
transfer anything after the modifications of
config.inc.php
, as the directory is
already on the web space.
Apache is usually run as a service, so we have to ensure that the user under which
the service is running has normal read privileges to access our newly created
directory. The same principle applies to IIS, which uses the
IUSR_machinename
user. This user
must
have read access to the directory. You can adjust permissions in
the
Security/permissions
tab of the directory's properties.
First Connection Configuration
Here we learn how to prepare and use the configuration file which contains
the parameters to connect to MySQL and which can be customized as per our
requirements. In this chapter, we will concentrate on the parameters that deal with
connection and authentication. Other parameters will be discussed in the chapters
where the corresponding features are explained.
Before configuring, we can rename the directory
phpMyAdmin-2.8.2
to something easier to remember,
like
phpMyAdmin
,
phpmyadmin
,
admin
, or whatever.
This way, we or our users will be able to visit an easily
remembered URL to start phpMyAdmin. We can also use a
symbolic link if our server supports this feature.
Configuration Principles
In versions before 2.8.0, a generic
config.inc.php
file was included in the
downloaded kit. Since 2.8.0, this file is no longer present in the directory structure.
Note that phpMyAdmin looks for this file in the first level directory - the same one
where
index.php
is located.
Search WWH ::
Custom Search