ZerethShell
File Manager
SQL Manager
/
var
/
softaculous
/
wp64
_wp-config.php
<?php /** * The base configuration for WordPress * * The wp-config.php creation script uses this file during the installation. * You don't have to use the web site, you can copy this file to "wp-config.php" * and fill in the values. * * This file contains the following configurations: * * * Database settings * * Secret keys * * Database table prefix * * ABSPATH * * @link https://wordpress.org/documentation/article/editing-wp-config-php/ * * @package WordPress */ // ** Database settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define( 'DB_NAME', '[[softdb]]' ); /** Database username */ define( 'DB_USER', '[[softdbuser]]' ); /** Database password */ define( 'DB_PASSWORD', '[[softdbpass]]' ); /** Database hostname */ define( 'DB_HOST', '[[softdbhost]]' ); /** Database charset to use in creating database tables. */ define( 'DB_CHARSET', '[[utf8]]' ); /** The database collate type. Don't change this if in doubt. */ define( 'DB_COLLATE', '' ); /**#@+ * Authentication unique keys and salts. * * Change these to different unique phrases! You can generate these using * the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}. * * You can change these at any point in time to invalidate all existing cookies. * This will force all users to have to log in again. * * @since 2.6.0 */ define( 'AUTH_KEY', '[[AUTH_KEY]]' ); define( 'SECURE_AUTH_KEY', '[[SECURE_AUTH_KEY]]' ); define( 'LOGGED_IN_KEY', '[[LOGGED_IN_KEY]]' ); define( 'NONCE_KEY', '[[NONCE_KEY]]' ); define( 'AUTH_SALT', '[[AUTH_SALT]]' ); define( 'SECURE_AUTH_SALT', '[[SECURE_AUTH_SALT]]' ); define( 'LOGGED_IN_SALT', '[[LOGGED_IN_SALT]]' ); define( 'NONCE_SALT', '[[NONCE_SALT]]' ); /**#@-*/ /** * WordPress database table prefix. * * You can have multiple installations in one database if you give each * a unique prefix. Only numbers, letters, and underscores please! */ $table_prefix = '[[dbprefix]]'; /** * For developers: WordPress debugging mode. * * Change this to true to enable the display of notices during development. * It is strongly recommended that plugin and theme developers use WP_DEBUG * in their development environments. * * For information on other constants that can be used for debugging, * visit the documentation. * * @link https://wordpress.org/documentation/article/debugging-in-wordpress/ */ define( 'WP_DEBUG', false ); /* Add any custom values between this line and the "stop editing" line. */ /* Multisite */ define( 'WP_ALLOW_MULTISITE', true ); define( 'MULTISITE', true ); define( 'SUBDOMAIN_INSTALL', false ); define( 'DOMAIN_CURRENT_SITE', '[[domhost]]' ); define( 'PATH_CURRENT_SITE', '[[relativeurl]]/' ); define( 'SITE_ID_CURRENT_SITE', 1 ); define( 'BLOG_ID_CURRENT_SITE', 1 ); [[WP_AUTO_UPDATE_CORE]] /* That's all, stop editing! Happy publishing. */ /** Absolute path to the WordPress directory. */ if ( ! defined( 'ABSPATH' ) ) { define( 'ABSPATH', __DIR__ . '/' ); } /** Sets up WordPress vars and included files. */ require_once ABSPATH . 'wp-settings.php';
Kaydet
Vazgeç