GithubHelp home page GithubHelp logo

Comments (4)

danepowell avatar danepowell commented on July 25, 2024

Re-posting from #141...

Your argument makes complete sense and I was initially inclined to agree. However, at least within PS, it's rare that we launch new multisite projects on ACE any more. Multisite almost always goes on ACSF, which doesn't use either all or default anyway. So to me it actually makes sense to keep using default, since that aligns with the most common use case. It's really a pain on a single-site installation when some config exists in sites/all and other config in sites/default.

I think you could make a good argument either way. Regardless of the merits of all vs default though: we've already flipped back and forth between them at least twice, and the transition sucks for anyone already using Bolt. I don't particularly want to do it again unless there's a pretty compelling reason.

from blt.

danepowell avatar danepowell commented on July 25, 2024

Not sure if it's worth the added complexity, but we could have a "multisite" switch in project.yml. If a project is multisite, settings go into sites/all. Otherwise they go into sites/default.

from blt.

greylabel avatar greylabel commented on July 25, 2024

The compelling reason, IMHO, is it is better architecture to treat default the same as you would any other site in a multisite and not a special, global snowflake. For single-site installations, I don't really know how much heartburn this will cause if BLT handles the provisioning and is well documented -- developers should already be comfortable with the ideas of using sites/all with single-sites for modules and themes, not much difference here in concept.

That said, I really like the idea of "multisite" switch in project.yml or better multisite considerations throughout the project, including build.yml, box/config.yml, CI integration, and all other config files.

from blt.

grasmash avatar grasmash commented on July 25, 2024

This is now a moot point as of 8.4.0, given that default settings are now in vendor/acquia/blt/settings. Only local settings are insites/default and these are site specific.

from blt.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.