Just a quick note, we have fixed the issue with regards to the resize of the machines. We have submitted a new version of the solution and it will be available in the marketplace in the following days.
That's great to hear!
Please, disable the apache system service so you don't run into this issue again. Run the following command:
sudo systemctl disable apache2
We are facing few issues, such as while trying to install the plugins it creating the folder with ‘daemon’ as owner and group due to that we are unable to install / update / delete the plugins. If I gave 777 to the folder then only it install the plugin but still facing the issue with updating the plugins. So we also need the below information along with this.
Could you please describe how are you trying to install the plugins? You can find some documentation on this here:
Answering your questions:
Unfortunately, that is not possible to achieve with this solution. Note that if you set multiple WordPress instances, you will need to create a shared volume and mount it in all the nodes to have the application in sync across all the VMs.
For this purpose you can find useful the following guide:
In the instances, you can become superuser by executing
sudo su. This command changes from your unprivileged system user to "root" user. In the database, you also have an administrator profile. When you first launched the deployment, you needed to set a password for the database. You can use the following command to obtain a mysql console with privileged permissions:
From the WordPress instance:
mysql -h provisioner-peer -uroot -p
From the database instance:
mysql -uroot -p
That will depend on the maintenance tasks you want to accomplish. To mention some:
5) What is the architecture of the application like PHP, MySQL, Apache and WordPress (folder structure, .ini, config, libraries etc…) as we saw the main wordpress folder is in /opt/bitnami/wordpress except the wp-content and config files but the shortcuts are exists in this folder.
All the components are located under
/opt/bitnami/. You can find there Apache, PHP and WordPress for example. You can find the configuration files of the services in
/opt/bitnami/NAME_OF_THE_SERVICE/conf/ and the logs in
/opt/bitnami/NAME_OF_THE_SERVICE/logs/. For WordPress (not a service but an application), the main config file is
As you point, some files are symbolic links or shortcuts to
/bitnami/. That is because
/bitnami is mounted in a different volume so you reattach it to a different instance in the future but keeping your data.
The service configuration is configured to optimize the performance. If you want to manually tweak the values, you can do so by modifying the following config files:
If you change them, you will need to restart the services:
sudo service bitnami restart
Note that we do not recommend to modify those values, you can run into issues when changing them.