Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
cloud-native
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Development
  • cloud-native
  • Issues
  • #8

Closed
Open
Opened Nov 21, 2017 by totten@tottenOwner

Move example data to an optional/add-on step

During installation, the installer shows a checkbox which asks whether you want to load sample data. Then:

  • If you don't want sample data, it loads sql/civicrm_data.mysql.
  • If you do want sample data, it loads sql/civicrm_generated.mysql.

This has some consequences:

  • You must choose whether to load sample data during installation. This is presented in the installer UI.
  • The civicrm_generated.mysql takes extra work to maintain (eg bin/regen.sh; the output of which is not merge-friendly).

The goal here would be to have one installation process -- which could be headless. Afterwards, you should have the option to enable create the sample data. This option may be specified as at same time as other install parameters (eg via arg) or perhaps via a separate command afterwards.

Edited May 17, 2018 by JoeMurray
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/cloud-native#8