There are several benefits to running WordPress on Synology NAS. Perhaps the most obvious is that it provides a fast and reliable way to host your website. Additionally, since WordPress is already pre-installed on many Synology NAS devices, it is quick and easy to set it up.
Install WordPress on a Synology
In this article, I have walked you through the steps of installing WordPress on Synology. I also showed you how to install phpmyadmin as an additional package. Finally, I weighed the pros and cons of doing so. Following my instructions, you should now be able to install WordPress on Synology and also modify it in order to get the latest WordPress version automatically.
There are two ways to install WordPress on your Synology NAS: simple and complex. Also known as the Synology way and the WordPress.org way. This first part in a series of four explains their differences. Make your choice and continue with part 2 (simple & limited) or part 3 (complex & flexible).
One option is the Synology WordPress package from Package Center. This installation takes care of all dependencies and most of the necessary configurations. This is obviously the easy way but has several limitations.
You can download the latest version from WordPress.org and install it on your NAS. You install the packages WordPress depends on from Package Center. Finally, you configure some items yourself to connect the components.
The WordPress from Synology setup stores its files in the /web/wordpress folder. As a result, the web address of your site is _address_nas/wordpress or _name.local/wordpress. Therefore, if you install WordPress from Synology, I assume your main reason is the simple setup. I also assume you use it internally, not accessing it from the internet.
The WordPress.org installation mitigates the issue of the subfolder as suffix via a virtual host configuration in Web Station. Within Web Station, you configure a domain name for this /web/subfolder. As a result, your website address will be something if synodemo.com is your domain. I discuss virtual host in part 3.
If you plan to run WordPress on your NAS and make it accessible from the Internet, you could consider running it from a separate NAS or a virtual NAS. In the latter case, you can choose between installing WordPress on a virtual DSM or from within Docker.
Go to Successfully install WordPress on Synology NAS (part 2) for the WordPress from Synology solution. Or choose Successfully install WordPress on Synology NAS (part 3), where you learn how to install the download from WordPress.org on your Synology NAS.
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as Themes. In this step by step guide I will show you how to install WordPress on your Synology NAS using Docker & Portainer.
Install Portainer using my step by step guide. If you already have Portainer installed on your Synology NAS, skip this STEP. Attention: Make sure you have installed the latest Portainer version.
Go to File Station and open the docker folder. Inside the docker folder, create two new folders and name one wordpress and the other one wordpressdb. Follow the instructions in the image below. Note: Be careful to enter only lowercase, not uppercase letters.
Scroll down on the page until you see a button named Deploy the stack. Click on it. Follow the instructions in the image below. The installation process can take up to a few minutes. It will depend on your Internet speed connection.
Please wait approximately 5 minutes for the installation to be completed or you will get a blank page with the following error message: Error establishing a database connection. The installation process can take up to a few seconds/minutes. It will depend on your Internet speed connection. Now open your browser and type in -ip-address:8181 Select your language then click Continue. Follow the instructions in the image below.
Technically, you will be able to get to WordPress now, but if you try and access any specific posts, you will receive an error. The reason is that our Site Address has /wordpress in the URL. We can quickly change this from the WordPress admin settings.
This problem appears only with WordPress since if I create a different virtual host where the root folder points to web/webpage1 (containing a simple index.html), I am able to see the webpage. I gave all the permissions to my user (I am admin) in the web folder and all its content, so webpage1 and wordpress folders should have same permissions.
Hi, i got installed wordpress everything the whole setup is done in DSM 7. the only problem i am facing now is to change the url from example.com/wordpress to fully another domain test.com i created here virtual host with the domain is working but it have access only to the home folder and not to the subsites i guess its because in wordpress is still under general settings the domain example.com/wordpress but its greyed out and i am unable to change that to the test.com urlDo you have please may any idea how to change the url?
You should be able to create a manual backup using the method here: -guide/how-to-make-a-wordpress-database-backup-manually/If you reach out to your hosting provider they should be able to assist with getting you access back to your site
Linux distributions mostly rely on a package management system to ease the installation of additional software packages and components. IPKG is the package management system most frequently used on the DSM. In order to use it, you must download and install the correct version for the CPU available in the NAS (the DS212j is powered by a Marvel Kirkwood mv6281 ARM CPU). The following wiki pages on the Synology website explain how to determine the correct version:
Subversion support is not available out of the box or installable trough the package center, but the IPKG repository contains it. Installing and setting it up is quite simple if you follow this article on the Synology wiki ( -by-step_guide_to_installing_Subversion). Although, I would prefer an integrated solution trough the package center.
I the past I was a big fan of SVN, but more recently I became fund of GIT. Just like with Subversion, it is not supported by DSM trough the package center, but the IPKG repository contains it. Ryan Helco ( -guide-git-gitolite-synology-diskstation/) took the effort to write down the necessary steps to set it up.
Unfortunately, installing and configuring the necessary packages and tools is not always that user friendly. Though, either Synology or the 3rd party ecosystem could change this quite easy in the near future by adding a number of these packages to the package center. The bundled MySQL database and phpMyAdmin are a good example. Both are officially available and setting them up is a piece of cake.
As mentioned before, you have to create SynoBuildConf/build, SynoBuildConf/install, SynoBuildConf/depends and WordPress source project before creating spk. However, since WordPress depends on PHP, we don't have to compile any source code.
Secondly, before installing your WordPress spk, you need to download the dependant packages such as WebStation, MariaDB, PHP7.2 and Apache2.2 in DSM from Package Center. Noted that we use PHP7.2 and Apache2.2 in this example, you can choose whatever you want in considering your circumstances.
The following is the privilege file under conf directory. The privilege file is configuration for specifying the installation and run time privilege.The detail of privilege will be elaborated under privilge section.
The following is the resource file under conf directory. The resource file are configurations for calling workers. In this example, since we would like to integrate WordPress with WebStation, we will call WebStation's worker to run specific setup during installation. For more details, please see webservice.
If the building process was successful, you will see that the .spk file has been placed under result_spk folder.To test the spk file, you can use manual install in Package Center to install your package.
If you are not comfortable with the performance, check the [where you installed ZurmoCRM]/app/protected/config/debug.php file and look for $phpLevelCaching. It should be true by default.
Edit the [where you installed ZurmoCRM]/app/protected/modules/zurmo/components/BeginRequestBehavior.php file and change public function handleApplicationCache($event) as highlighted by bold.
The $memcacheServiceHelper->runCheckAndGetIfSuccessful() calls runCheckAndGetIfSuccessful() in [where you installed ZurmoCRM]/app/protected/modules/install/serviceHelpers/MemcacheServiceHelper.php to check if Memcache has been load.
The problem users might run into with running WordPress on Synology, is folder permissions. By default, the Synology packaged version of WordPress will work just fine. But if you run multiple versions, you will get alerts to setup FTP settings in order to download, install, and update your WordPress plugins, themes, and core updates.
Synology Web Station uses a special HTTP user for it's default web folders, including it's WordPress package. If you create your own folders, like for multiple WordPress sites, the system will use your permissions instead. This is what causes the issues with installing/updating plugins, themes and WordPress. Now that you are logged into your Synology via Terminal/SSH, you can navigate to the systems WEB folder and update all of your WordPress folders and files. 2ff7e9595c
コメント