Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New repo structure #142

Open
Yehonal opened this issue Sep 17, 2024 · 2 comments
Open

New repo structure #142

Yehonal opened this issue Sep 17, 2024 · 2 comments

Comments

@Yehonal
Copy link
Member

Yehonal commented Sep 17, 2024

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:

  1. Power users would still like to use the plugins separately and install them into a pre-existing Wordpress installation
  2. We do not have a straightforward way to update the Wordpress files

Solutions

  1. Plugins: We can create a github action that pushes the files of our plugins into one or more separated repositories that are read-only
  2. 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
@Ercules76
Copy link
Member

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."

@Yehonal
Copy link
Member Author

Yehonal commented Nov 5, 2024

I'm totally new to Bedrock, are you willing to work on it or provide guidance on how to set this up?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants