Project

General

Profile

Actions

Feature #80212

closed

Idea: move some database stored config to files

Added by Urs Braem over 7 years ago. Updated 28 days ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
System/Bootstrap/Configuration
Start date:
2017-03-09
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Here's a longer term idea (proposal): move all backend user configuration away from the database into files, so they can be included in VCS.

I'm thinking about the following tables

  • be_users, be_groups, backend_layout (mostly)
  • sys_file_storage, sys_filemounts (maybe)

A use case: we have to create a new region on a pagetype, with a new content type

Imaginary workflow:

  • Create a new content element, for example as an extension, or with ext:mask
  • Add a new be_layout column for that item
  • Allow the new content element in be user settings, check excludefields
  • Get the updated config file from on the server
  • Commit everything in one commit

Actually, I'd personally prefer to edit BE user rights in JSON structures instead of endless checkbox lists.
But maybe others don't think so.


Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Feature #92431: Make be_users and be_groups permissions configurable via YAMLClosed2020-09-28

Actions
Related to TYPO3 Core - Epic #95904: Make backend user and user groups deployableUnder Review2021-11-08

Actions
Actions #1

Updated by Susanne Moog almost 6 years ago

  • Target version changed from 9 LTS to Candidate for Major Version
Actions #2

Updated by Susanne Moog over 4 years ago

  • Category set to System/Bootstrap/Configuration
Actions #3

Updated by Georg Ringer almost 4 years ago

  • Related to Feature #92431: Make be_users and be_groups permissions configurable via YAML added
Actions #4

Updated by Georg Ringer 28 days ago

  • Status changed from New to Closed

closing issue in favor of #95904

Actions #5

Updated by Georg Ringer 28 days ago

  • Related to Epic #95904: Make backend user and user groups deployable added
Actions

Also available in: Atom PDF