Note that in many cases when creating databases and users via a web-based interface, the username you use to log into your control panel is added as a prefix to the database name and possibly to the database username as well. You will enter these items into fields in your browser when running the installation script (For example, are you installing in, or in, or etc.?) as you create the database. Take note of the username, password, database name and hostname. In most web control panels' "database wizard", if you simply check "All" privileges for the user you create (and then uncheck "Grant" if it is listed as a privilege) your user will be set up correctly. When you create the user for your database, you may see a page where you can specify the privileges that the user will have for various operations on the database. To create a database using a browser-based control panel consult the documentation or ask your web host service provider. These tools include easy-to-use features for creating a new database, and for creating a "user" with rights to the database. Most web hosting accounts provide a Web-based control panel to help you administer your site. Allowed characters are a.z, 0.9, and "_" (underscore).Ĭreate a database and user via a browser-based control panel. If you use capital letters in the database name, they will be converted to lower case.Selection of characters in MySQL/MariaDB database name Using SQL commands (using the command line).Web browser-based control panel (such as "CPanel" or "Plesk").This page provides direction for creating your Drupal database using one of the following methods: The database user you specify during installation is the one that will connect to the database on every page load. If you are installing Drupal on a public web server, then you should create the database first, and give access to a less privileged user. When you run the installation script (next step) just supply the user name and password of a database user with permission to create a new database. Remember this database name, as it will be used to configure Jira's connection to this database in subsequent steps.If you are installing Drupal on a test site, then you can skip this step. Remember this database user name, as it will be used to configure Jira's connection to this database in subsequent steps.Ĭreate a database for Jira to store issues in (e.g. Create a database user (login role) which Jira will connect as (e.g.You can find information on creating users and databases for your version of PostgreSQL on their website. Create users and databases for your version of PostgreSQL PostgreSQL 9.6 documentation - Connections and AuthenticationĪfter you modify the data/nf and data/pg_hba.conf files, restart PostgreSQL for the changes to take effect.PostgreSQL 10 documentation - Connections and Authentication.PostgreSQL 11 documentation - Connections and Authentication.The following PostgreSQL documentation contains information on the appropriate listen_addresses value in the nf file as well as the pg_hba.conf file: if your PostgreSQL server is not installed locally on your Jira server host system), you will need to configure your data/nf and data/pg_hba.conf files to accept remote TCP connections from your Jira server's IP address. If you are connecting Jira to a remote PostgreSQL server (i.e. Create and configure the PostgreSQL database Accept remote TCP connections (remote PostgreSQL server only)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |