Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 37 ยท Installation and Admin

Run the Joomla Web Installer

Walk through the Joomla web installer: site name, admin account, database settings, table prefix and the final checks, with a runnable form validator.

With a folder of Joomla files and an empty database ready, installation takes a few minutes. You open the site address in a browser and Joomla's web installer asks for the details it needs. When you finish, it writes configuration.php, creates the database tables and gives you a working site and an administrator login.

This lesson describes each installer screen and what to enter. The installer itself is not available on this site, so the screens are described in words. The runnable stand-ins validate the same kinds of input (passwords, table prefix, email) so you can see what makes a valid entry.

Start the installer

Open the address of your folder in a browser, for example http://localhost/joomla or http://joomla.test. If the files are in place and no configuration.php exists, Joomla shows the installer automatically. Choose the installation language first; it can differ from the language you will use on the site later.

The installer has a few simple steps.

The installer in four steps

  1. Site setup
Name, admin user, password, email
  1. Database
Type, host, user, password, name, prefix
  1. Overview
Review and run the checks
  1. Done
Open site or administrator

No installation folder to delete in modern versions

1 / 2

Step 1: site and admin account

You enter:

  • Site name: shown in browser titles and by default in the header. You can change it later in Global Configuration.
  • Super User name and username: the full administrator account. Avoid the username admin, which bots try first.
  • Password: use a long, unique one. Modern Joomla versions enforce a minimum length (12 characters by default) and complexity can be tuned in the Users component options.
  • Email: used for password resets and system messages. It must be a real address you can read.
  • Site offline (optional): set it to Yes to keep visitors out until your site is ready.

Step 2: database

  • Database type: MySQLi, MySQL (PDO) or PostgreSQL. The first two work with MySQL and MariaDB.
  • Host name: usually localhost. In Docker it is the service name of the database container.
  • Username and password: those of the database user you created.
  • Database name: the empty database from the previous lesson.
  • Table prefix: text put in front of every table name (default is random, like x4k2p_), so that several sites can share one database and so that tables are harder to guess.
  • Connection encryption options are available for remote databases.

When you press Install, Joomla creates the tables and a starting set of data. The final page offers Open Site and Open Administrator.

What happened behind the scenes

  • configuration.php was written in the site root with your database details and a random secret.
  • Tables such as x4k2p_content (articles), x4k2p_menu, x4k2p_modules, x4k2p_users and x4k2p_extensions were created.
  • Your Super User was added to the Super Users group.
  • Default extensions, including the Cassiopeia template and core modules, were installed.

Never reuse your live site's database password on a local test machine, and never put an installation on a public address with a default or empty database password. Anyone who finds an open installer can take the site over.

Validate the form like the installer

The installer checks your entries before it continues. The stand-in validator below applies similar kinds of rules, so you can see what is accepted. The exact rules of the real installer may differ in detail between versions.

JS Stand-in: validate installer input

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Both attempts exercise different branches. The first fails on every rule; the second passes. Note the use of regular expressions for the prefix and email and a plain length check for the password: a good password policy is about length first.

Generate a random prefix

Joomla suggests a random prefix, which is a tiny but useful security habit. The stand-in below builds one the same way in spirit.

JS Stand-in: a random table prefix

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The result is different on each run. A random prefix does not replace real security, but it removes one easy guess.

After the installation

  1. Open the frontend and check that the default page loads.
  2. Log in at /administrator with the Super User you created.
  3. Read the first post-installation messages in the backend; they explain optional settings such as enabling two-factor authentication.
  4. Open System > Global Configuration and review the settings (next lessons).
  5. Keep a note of the database details and admin account in a password manager, not in a text file in the webroot.

Common installation problems

  • "Cannot write configuration.php". The web server needs write access to the site folder. Joomla shows the generated file text so you can create it by hand.
  • "Could not connect to database". Check the host, user, password and that the database exists and uses the right type.
  • A blank page or error 500 after install. Look at the PHP and web server error logs; a missing extension or an .htaccess rule is the usual cause.
  • Installer appears again. That means configuration.php is missing or unreadable.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What file does the installer create with your database details?

    configuration.php stores the database connection, site name, secret and other settings.
  2. 2. What is the table prefix for?

    The prefix distinguishes tables and makes names harder to guess.
  3. 3. Which is the best choice for the Super User username?

    Bots try common names such as admin first. A unique username removes an easy target.
  4. 4. Where do you log in to manage the site after installation?

    The backend lives under /administrator by default.

Summary

  • The web installer collects site name, Super User, database settings and a table prefix, then creates tables and configuration.php.
  • Use a long unique password, a non-obvious username and a real email address.
  • A random table prefix and a dedicated database user are small, useful security habits.
  • After installing, log in at /administrator, read the post-installation messages and review the configuration.

Next: A Tour of the Administrator Backend