Problem/Motivation

Nowadays there are a lot of dependencies that are not really needed on sites based on rocketship. 2 examples are search_api and migrate. They might not be needed on some sites, and are still difficult to uninstall since they are treated as dependencies, even if they are not used at all on the site, having a performance impact and maintenance cost with no benefit.

Proposed resolution

This is a proposal, there are other solutions.
As an easy solution, many dependencies might be moved from the "dependencies" section to the "install" section of the info.yml file. If they are on rocketship_core, they should be moved to the dropsolid_rocketship_profile as well for better use of the single responsibility principle.
In this way, the functionality and behavior of rocketship will remain as it is but will be possible to uninstall modules after the installation.

Remaining tasks

Determine other modules or functionality which is less used and could be optional.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

sdstyles created an issue. See original summary.

mallezie’s picture

Status: Active » Needs work
sdstyles’s picture

Status: Needs work » Needs review

Thanks,
Fixed the typo, and removed redirect as dependency for rocketship_blocks, however we can't get ride of it, yet, as the rocketship_seo has a dependency to it because of redirect.settings.yml and rockethip_core requires it in PathAliasUpdateSubscriber.

Dropsolid Rocketship profile still use it setup some redirects during installation.

mallezie’s picture

Status: Needs review » Reviewed & tested by the community

Thanks Sorin!

Good spot on redirect in rocketship_seo. But at least the dependency is on the correct place now.

nginex made their first commit to this issue’s fork.

  • nginex committed 46cb9c6d on 6.0.x authored by sdstyles
    Issue #3331973: Move modules from "dependencies" to "install" on info....
nginex’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for the work

nginex’s picture

Status: Fixed » Closed (fixed)

It's now available since 6.0.3