Description of the need Currently redirect configuration does not write to a json file. It would be preferable if they did. For the containerized deployment method that we are working on with Backdrop, the preference is that we would not actually log into site instances and manually create redirects, we want these redirects to exist upon deployment.
Proposed solution All redirects would be written to a json config file. The redirect module is already included in Backdrop core, this would be a feature enhancement.
Alternatives that have been considered The only alternatives that have been considered are server level rewrites that would have to be added to all instances.
Recent comments
https://www.drupal.org/project/views/issues/1266388 shows that this is an architectural issue, and requires another 2 hooks being adjusted. It would be really nice to add comments/notes to...
node access
Hmmm, from D7 ancient tomes: from https://drupal.stackexchange.com/questions/7056/limit-which-roles-can-view-a-node-basing-on-its-content-type yet https://docs.backdropcms.org/api/...
node access
I also note on this screen: "Furthermore note that content which is not published is treated in a different way by Backdrop: it can be viewed only by its author or users with the...
node access