Project

General

Profile

« Previous | Next » 

Revision 7243

View differences:

configuration.rst
34 34
(if the installation is new, or if Metacat was unable to determine the location 
35 35
of an existing back-up directory). The authentication configuration is required 
36 36
for logging in to the Metacat and for defining administrative accounts. 
37
Instructions for changing the authentication configuration without 
38
authentication are included at the end of this section.
37
Instructions for `Changing Authentication Configuration without Authentication`_ 
38
are included at the end of this section.
39 39

  
40 40
Back-up Configuration
41 41
~~~~~~~~~~~~~~~~~~~~~
......
228 228
default configuration.
229 229

  
230 230
If your Metacat has a customized skin, it will appear as a choice in the 
231
Skins Configuration settings (Figure 3.7). You can creat your own skins as 
231
Skins Configuration settings (see below screenshot). You can create your own skins as 
232 232
well. For more information about creating skins, please see the section called
233
Creating a Custom Skin.
233
`Creating a Custom Skin`_.
234 234

  
235 235
.. figure:: images/screenshots/image023.png
236 236
   :align: center
......
254 254
Database Configuration
255 255
~~~~~~~~~~~~~~~~~~~~~~
256 256
Because the Database Configuration is dependent on values specified in the 
257
Global Configuration section, the link to these settings does not become active 
257
Global Properties section, the link to these settings does not become active 
258 258
until after the global settings have been saved. Once the global settings have 
259 259
been saved, Metacat automatically detects the database schema version and 
260 260
upgrades it if necessary (and with your permission). 

Also available in: Unified diff