Maybe you need to do your own docker image.if it is missing in the official container of wordpress you have no magic way to install it. What is strange is that the app is able to communicate with the mariadb container…so why you need another php mysql plugin
Once the app is restarted I went to the media manager and you can see the maximum size of the image you can send
Oh! Interesting. Thank you.
Forgive me for the newb question, I’m poking around on the github, trying to understand the module and how I could modify it. It looks to me as though this RUN line could be added to the Containerfile under the ui folder. Can it really be that simple?
Is there a doc somewhere that would help me build a check out of the github into an ns8 module?
not simple maybe as you wish but you need to understand the concept of dockerfile then you will add to the image whatyou need
Once the app is restarted I went to the media manager and you can see the maximum size of the image you can send
This is still not working as I would expect. Here’s my uploads.ini file:
memory_limit=512M
upload_max_filesize=512M
post_max_size =512M
max_execution_time=600
max_input_time=600
max_file_uploads=50
And here is what I see in media manager:
I have modified the settings (Request LE Certificate and Force HTTPS) on the cluster manager to try to force the module to restart, but the settings don’t seem to update.
I thought perhaps I could manually issue a restart using podman at the cli, but I can’t find the wordpress module. 
# podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5cf6aed3b39a ghcr.io/nethserver/restic:2.5.4 rclone serve webd... 31 hours ago Up 31 hours ago rclone-webdav
e466e6cdbdf9 ghcr.io/nethserver/redis:2.5.4 redis-server /dat... 31 hours ago Up 31 hours ago redis
4602cd1c76d3 docker.io/grafana/promtail:2.9.2 -config.file=/etc... 24 hours ago Up 24 hours ago promtail
ae1accf91c2d docker.io/crowdsecurity/crowdsec:v1.5.4-debian 24 hours ago Up 24 hours ago crowdsec1
#
I think I’m missing something obvious.
If it is running on top of nginx, then it is also needed to modify client_max_body_size nginx config parameter.
Hi Marc,
Thanks for the reply. Unless I am mistaken (very possible), I believe this is based on the wordpress:apache docker image. So nginx config wouldn’t apply.
Thank you again. I think I have been able to work out the basics on the dockerfile. I was able to successfully build a wordpress-pdo image using podman. However, I am still unclear on the NS8 module structure, so I’m uncertain how to marry my wordpress image to the module, or two a new module, such that it is working in harmony with what you’ve already constructed.
Here’s my containerfile:
FROM docker.io/wordpress:6.4.3-php8.3-apache
RUN docker-php-ext-install pdo_mysql
And the build command is:
# podman build -t wordpress-pdo -f Container.file .
It seems like I could do what I want using the podman --replace directive as is being done here. However, as I mentioned above, I am not able to see the running wordpress container using podman, so I have no idea how to reference it.
I gave in and rebooted the server. The changes to uploads.ini are now reflected in the wordpress interface. So, the question remains, what is the correct way to restart this module?
save the settings in the module settings page, and it will restart, however, i hope nothing breaks, since you have replaced the internal wp container with your build, or is that what you did?
I’ve tried that repeatedly. It does not restart the container for me. The only thing which has worked was a reboot.
Happy to try it, but I don’t know how to make the change. How would I replace Stephdl’s wp container with my build?
Not so simple. Maybe you should run your own container/pod. Each upgrade of wordpress container you will need to upgrade your container and tag it with the same tag that the wordpress container use
This is an example
@stephdl allow me to add this.
Not many people are container servy.
Equally, while at the core, what you are using might not immediately support some key requirements in users running systems on Nethserver, it is my believe that, asking a user to build and support their version of app implementing customs is not wise, especially if the said is not really a specific use case.
In near future, other members might come to a similar requirement, and other requirements as well.
Wouldn’t it be wise, and to the benefit of everyone if as the App developer to implement some of these into the said module, so that everyone benefits, and the upgrade and update path is easier for everyone.
Don’t get me wrong, and we do appreciate all your works and efforts, chances are, if he requires it, others might, and equally some others. so instead of having disenfranchised versions, everyone gets to reap from the same benefits.
Ns8 is still young…
what are your thoughts on this?
The settings page of the module. Save the form again
MAybe a command line command might help him out, not sure…
Might have a try
try
add-module ghcr.io/nethserver/wordpress:pdomysql
Testing Stephdl’s new build. THANK YOU!!!
This bit still doesn’t work for me. Here’s the logs when I save the form:
2024-03-12T12:58:12Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/c16b2bbf-3732-47f1-9bd4-ed78bc280778: get-name/50get_name is starting
2024-03-12T12:58:12Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/7386cf1b-8692-4ff1-b632-5a8c21aede72: get-status/20read is starting
2024-03-12T12:58:13Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/c16b2bbf-3732-47f1-9bd4-ed78bc280778: action "get-name" status is "completed" (0) at step 50get_name
2024-03-12T12:58:13Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/7386cf1b-8692-4ff1-b632-5a8c21aede72: action "get-status" status is "completed" (0) at step validate-output.json
2024-03-12T12:58:18Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/1725d048-d836-40b3-8b00-06eae8df7654: get-configuration/20read is starting
2024-03-12T12:58:18Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/1725d048-d836-40b3-8b00-06eae8df7654: action "get-configuration" status is "completed" (0) at step validate-output.json
2024-03-12T12:58:20Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/d99ae24a-3be1-4cfe-80d9-11726f69ab83: configure-module/01Hostname_validation is starting
2024-03-12T12:58:20Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/d99ae24a-3be1-4cfe-80d9-11726f69ab83: configure-module/10secrets is starting
2024-03-12T12:58:20Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/d99ae24a-3be1-4cfe-80d9-11726f69ab83: configure-module/20configure_traefik is starting
2024-03-12T12:58:21Z [1:wordpress2:agent@wordpress2] dump_env() is deprecated and implemented as a no-op
2024-03-12T12:58:21Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/d99ae24a-3be1-4cfe-80d9-11726f69ab83: configure-module/80start_services is starting
2024-03-12T12:58:21Z [1:wordpress2:systemd] Reloading.
2024-03-12T12:58:21Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/d99ae24a-3be1-4cfe-80d9-11726f69ab83: action "configure-module" status is "completed" (0) at step 80start_services
2024-03-12T12:58:21Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/82d9189b-6e3f-40b2-b7c5-5d3ae283a476: get-configuration/20read is starting
2024-03-12T12:58:21Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/82d9189b-6e3f-40b2-b7c5-5d3ae283a476: action "get-configuration" status is "completed" (0) at step validate-output.json
2024-03-12T12:58:24Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/8eda9b19-3360-4feb-bb4a-4b101eed08fc: get-status/20read is starting
2024-03-12T12:58:24Z [1:wordpress2:agent@wordpress2] task/module/wordpress2/8eda9b19-3360-4feb-bb4a-4b101eed08fc: action "get-status" status is "completed" (0) at step validate-output.json
Once again, a reboot immediately reflects the changes in uploads.ini. Is this really unique to me? Hitting the save button resets the module for everyone else?
what was wrong you have no error ???
yep it is a bug, I fix it