docs: add Backdrop-specific config considerations.#7037
Conversation
|
|
||
| Backdrop also allows you to store your active configuration in the database ([as of Backdrop 1.28.0](https://docs.backdropcms.org/change-records/swappable-config-storage)), which can be simpler while developing locally, especially if you are making use of DDEV's snapshot feature. In this case, the database and the active configuration are effectively bundled and refreshing the database also refreshes the active configuration. | ||
|
|
||
| #### Command line tool |
There was a problem hiding this comment.
I wonder would it make sense to move the command line part over to the backdrop quickstart? i mean for drupal drush is contained in every quickstart available (except for drupal cms but that is shipping with drush out of the box) so i suppose wouldnt ddev add-on get backdrop-ops/ddev-backdrop-bee be better suited in the two backdrop quickstarts? or is bee used less extensively with backdrop compared to drush with drupal?
There was a problem hiding this comment.
That makes sense to me.
There was a problem hiding this comment.
It does seem like bee has become adequately standard now that it should just be installed from the add-on right away when setting up a project. That can be another PR of course.
There was a problem hiding this comment.
I've removed the CLI piece from this PR and will make another for the quickstarts.
|
There are minor markdown complaints in https://github.com/ddev/ddev/actions/runs/13596373138/job/38014122763?pr=7037, easy to fix with another commit. |
3 participants
The Issue
Backdrop's config storage options can be confusing with local development, so it would be good to have a short description of the options as discussed in #7014 (comment)
As well, it is worth mentioning Backdrop's command line tool,
bee.Review rendered at https://ddev--7037.org.readthedocs.build/en/7037/users/usage/cms-settings/#backdrop-specifics