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

Feature Request: Presets for New Projects #279

Open
3 tasks done
knowler opened this issue Mar 29, 2022 · 3 comments
Open
3 tasks done

Feature Request: Presets for New Projects #279

knowler opened this issue Mar 29, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@knowler
Copy link
Member

knowler commented Mar 29, 2022

Terms

Summary

This would be a flag for new that could point to a file that might specify a list of plugins/packages to install for the project.

Motivation

Why are we doing this?

Developer convenience.

What use cases does it support?

Say you are an agency with a stack of plugins/packages that you always use for new projects or perhaps you have multiple types of projects each with their own list of plugins.

What is the expected outcome?

New Trellis project is created with Bedrock + all the plugins from the config file.

Potential conflicts / foreseeable issues

We will need to think through how the configuration would work. Should it just be a file that lives anywhere, should it be in a global conventionally placed config file, could it be a remote file somewhere (like a repo public or private)? We’d need to figure this out and stick with it.

Additional Context

No response

@knowler knowler added the enhancement New feature or request label Mar 29, 2022
@swalkinshaw
Copy link
Member

What kind of plugins/packages?

  • Composer
  • Ansible galaxy roles?

In either case, could this be solved by #9 ? In your use case, the agency would have a custom Bedrock or Trellis fork (with the packages they want).

@knowler
Copy link
Member Author

knowler commented Mar 29, 2022

What kind of plugins/packages?

Composer

In either case, could this be solved by #9 ? In your use case, the agency would have a custom Bedrock or Trellis fork (with the packages they want).

Oops, ya, I missed that. Though, I’ve heard difficulty expressed on a few occasions about the need to maintain a fork. I thought something like this could alleviate that.

@johnkraczek
Copy link
Contributor

johnkraczek commented Jul 12, 2023

I would also be interested in this.
At my agency, we have a private composer repository source that has all of the private plugins our agency uses.
Right now, we always go add that to the config each time we run a new project. It would be great if we could specify a config file that would be used.

config.json

... other yaml keys ...

  "repositories": [
    {
      "type": "composer",
      "url": "https://wpackagist.org",
      "only": ["wpackagist-plugin/*", "wpackagist-theme/*"]
    },
    {
      "type": "composer",
      "url": "https://composer.example.com"
    }
  ],
  "require": {

   ... other require slugs ...

    "elementor/elementor-pro": "*"
  },

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

No branches or pull requests

3 participants