Skip to content

Workspace: Strategy for safer update #2466

@geofranzi

Description

@geofranzi

Currently, the most time-consuming and error-prone step is updating the workspace. The previous setting can easily get lost during manual copy, or new settings can be overlooked.

  • check what needs to be in the workspace (can something move to data or to the database)?
  • settings files (at least the smpt settings) need to stay ar file, write a script to compare and copy between old and new

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions