Skip to content

[Feature] settings import/export #294

Closed

Description

@dpantel

Feature request:

I would love an easy way to export and import the settings. It would help greatly with automated deployment (Ansible, etc.) of Heimdall.

I know I can copy the sqlite db, but that seems messy and might interfere with db changes in the future.

Some ideas:

  1. The most rudimentary way to implement this would be a simple sql dump and ingest. This way, all you need is a text file.

    • upsides
      • easy to implement
    • downsides
      • hard to read/edit manually
      • have to trust that text file is well-formed
  2. A more complicated, but better way would be to transform the necessary data to/from a config file.

    • downsides
      • harder to implement
    • upsides
    • formats to consider
      • TOML
      • YAML
      • JSON
      • INI

Activity

  1. DavidRawling commented on Nov 20, 2018

    @DavidRawling

    An alternative or extension to this might be for the admin to be able to add the app to a "shared" section of the heimdall world, which then makes it available to all users for pinning (but not customisation).

  2. dakipro commented on Dec 12, 2018

    @dakipro

    I would also like this as I would like to provision server and include heimdall dashboard preconfigured based on services server is heaving. Perhaps even a web API would work.

  3. justjake commented on Nov 10, 2019

    @justjake

    I just finished setting up a new server. The hiemdall part is the only thing that I haven't figured out how to automate :(.

  4. justjake commented on Nov 14, 2019

    @justjake

    See also #383 ”Web GUI Backup”.

  5. makcuber commented on Jan 29, 2020

    @makcuber

    Just got Heimdall running in docker to test it out. The lack of some sort of bulk import feature is a big negative for me. I have a ton of URL's preorganized as bookmarks, and I'd love to be able to just export those and import them into Heimdall so they are accessible as a slashpage

  6. locked and limited conversation to collaborators on Mar 12, 2022
  7. converted this issue into a discussion #692 on Mar 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions