via DNS, or edits to the client systems’ /etc/hosts file (on Windows the equivalent is C:\Windows\System32\drivers\etc\hosts). This hostname must be mapped to your box somehow, e.g. Or, instead of disabling the “it works” page, you may edit our configuration file to add a hostname that the WordPress installation will respond to requests for. Create /etc/apache2/sites-available/nf with following lines: Įnable the site with: sudo a2ensite wordpressĮnable URL rewriting with: sudo a2enmod rewriteĭisable the default “It Works” site with: sudo a2dissite 000-default Configure Apache for WordPressĬreate Apache site for WordPress. This is beyond the scope of this guide, however. In such setup the wp-config.php should (read: if you do it differently you need a good reason) be readonly to the site owner and group and other permissions set to no-access ( chmod 400).
Note that this sets the ownership to the user This will require configuring PHP-FPM to launch a separate instance per site each running as the site’s user account. This will also have fewer “gotcha” problems that the WordPress support volunteers will not be able to anticipate and therefore be unable to help with.Ĭreate the installation directory and download the file from : sudo mkdir -p /srv/wwwĬurl | sudo -u www-data tar zx -C /srv/www
We will use the release from rather than the APT package in the Ubuntu Archive, because this is the preferred method from upstream WordPress.
0 kommentar(er)
