You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to discuss about a new way to handle the repo files.
First of all is important to mention that Wordpress is included in this repo to have a easy installation process but also to give the users the right version of Wordpress to use (the supported one)
However, there are 2 things that might be solved:
Power users would still like to use the plugins separately and install them into a pre-existing Wordpress installation
We do not have a straightforward way to update the Wordpress files
Solutions
Plugins: We can create a github action that pushes the files of our plugins into one or more separated repositories that are read-only
Wordpress version: we should set a github action that updates the Wordpress files when we run the action. Maybe by getting them from the official Wordpress repository
The text was updated successfully, but these errors were encountered:
In our company, we have successfully managed WordPress installations using Bedrock from roots.io, which handles dependencies via Composer. I propose a similar approach for this project, where we could create three separate repositories:
One for the CMS
One for WordPress
One for the plugin
The plugin and the versions of WordPress would be installed through Composer in Bedrock. This way, it allows for better dependency management and easier updates for both WordPress and the plugin."
I would like to discuss about a new way to handle the repo files.
First of all is important to mention that Wordpress is included in this repo to have a easy installation process but also to give the users the right version of Wordpress to use (the supported one)
However, there are 2 things that might be solved:
Solutions
The text was updated successfully, but these errors were encountered: