wp-config.php Generator

Build a correct wp-config.php without copy-pasting from a 2014 blog post

Berjalan di browser kamu. Tidak ada yang diunggah.

Database

Database name Database user Database host Table prefixChanging this on a NEW install is fine. Changing it on an existing site requires renaming tables and rewriting two option rows — it is not a config change.

Debugging

Enable WP_DEBUGLogs PHP notices, warnings and errors. Pairs with the two options below — never enable it alone on a live site. Write errors to wp-content/debug.logRecommended. Errors go to a file instead of the page. Hide errors from visitorsSets WP_DEBUG_DISPLAY false. Without this, WP_DEBUG prints PHP errors — including your server's absolute paths — to anyone loading the page. Log database queries (SAVEQUERIES)Useful when hunting a slow page. Costs memory on every request — turn it off again afterwards.

Hardening

Disable the theme & plugin file editorDISALLOW_FILE_EDIT. If an admin account is ever compromised, the built-in editor is how a PHP backdoor gets written. There is no good reason to leave it on. Force SSL for the admin areaFORCE_SSL_ADMIN. Only enable once HTTPS actually works, or you will lock yourself out. Enable automatic core updates

Limits

WP_MEMORY_LIMIT (MB) Post revisions to keep0 disables them. Unlimited revisions are the quiet reason many wp_posts tables get enormous.

wp-config.php

Salts are generated in your browser with crypto.getRandomValues(). They are never sent anywhere — but for the record, WordPress's own api.wordpress.org salt endpoint is equally fine; it returns fresh random values over TLS.

Tentang wp-config.php Generator

Generate a wp-config.php with the constants you actually need — debug logging, memory limits, file-edit lockdown, upload limits, table prefix, and fresh salts. Everything is generated in your browser; nothing is sent anywhere.

Terkait

Tools lain yang mungkin kamu butuhkan

WP_DEBUG Configurator

Turn on the debug log without breaking your live site

Max Upload Size Fixer

Raise the upload limit — and get all three values consistent

WordPress .htaccess Generator

The rules WordPress needs, plus the hardening rules it does not ship with

FAQ

Pertanyaan

Apakah aman membuat salt wp-config.php di browser?

Ya. Salt-nya dihasilkan dengan crypto.getRandomValues(), generator angka acak yang aman secara kriptografis di browser, dan tidak pernah keluar dari mesinmu. Sekadar catatan, endpoint salt milik WordPress sendiri, api.wordpress.org, sama-sama aman — endpoint itu mengembalikan nilai acak baru lewat TLS. Ini soal kenyamanan, bukan perbaikan keamanan.

Kenapa ini tidak meminta password database saya?

Karena kamu tidak seharusnya mengetik password database produksi ke sebuah halaman web, sepercaya apa pun halaman itu mengaku dirinya. File yang dihasilkan punya placeholder — isi secara lokal, di editor kamu.

Bisakah saya mengubah table prefix di situs yang sudah ada?

Tidak cukup hanya dengan mengedit wp-config.php. Mengubah $table_prefix di situs yang sudah live mengharuskan mengganti nama setiap tabel DAN menulis ulang dua baris di tabel options dan usermeta. Ubah saat instalasi baru, atau biarkan saja.