Best Practices: Sharing a project |
Good ideas, both of you! I’m afraid the issue is larger than that, as it includes third-party modules that need configuring. For example, I’m using Lonnie’s Myth:Auth and will include instructions on how to configure the Activator emails BUT I also want to preconfigure some other values in app/Config/Auth.php. https://github.com/lonnieezell/myth-auth...h.php#L211
I really like this idea of an empty namespace that ships with projects and can receive “overrides” without removing files from the update stream. I think it would take extending the core Config class to prioritize that namespace. |
Messages In This Thread |
Best Practices: Sharing a project - by MGatner - 01-31-2020, 07:59 AM
RE: Best Practices: Sharing a project - by InsiteFX - 01-31-2020, 09:02 AM
RE: Best Practices: Sharing a project - by MGatner - 01-31-2020, 09:08 AM
RE: Best Practices: Sharing a project - by InsiteFX - 01-31-2020, 09:16 AM
RE: Best Practices: Sharing a project - by jreklund - 01-31-2020, 11:59 AM
RE: Best Practices: Sharing a project - by John_Betong - 01-31-2020, 08:12 PM
RE: Best Practices: Sharing a project - by MGatner - 02-01-2020, 05:27 AM
RE: Best Practices: Sharing a project - by jreklund - 02-01-2020, 07:34 AM
RE: Best Practices: Sharing a project - by littlej - 02-02-2020, 12:16 AM
RE: Best Practices: Sharing a project - by littlej - 02-03-2020, 11:33 PM
RE: Best Practices: Sharing a project - by MGatner - 02-04-2020, 04:09 AM
RE: Best Practices: Sharing a project - by littlej - 02-04-2020, 09:25 AM
|