Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.examples beat.examples
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.examplesbeat.examples
  • Issues
  • #6

Database development is a pain

Currently, developing a database for inclusion in the platform is a difficult task.

The user has to practically install a functional beat.web platform on his own machine to do it thoroughly:

  1. Create the JSON and RST descriptions of the database
  2. Upload that into the beat.databases package and install the contribution
  3. Create a toolchain that can use the database
  4. Create a new configuration that uses the database
  5. Download all pieces locally so that one can debug the toolchain and make sure all is working fine.

We should try to simplify this a bit.

Assignee
Assign to
Time tracking