Ticket #185 (closed enhancement: fixed)

Opened 3 years ago

Last modified 3 years ago

Set up an initial version of the 'getting started' wizard

Reported by: work@… Owned by: work@…
Priority: major Milestone: 0.8.2
Component: Core Functionality Version:
Keywords: Cc:
Product: Operating system:
URL: Hardware:

Description (last modified by work@…) (diff)

Set up a 'getting started' wizard. On a clean installation of gscf the end-user should be presented with a wizard to help set-up the gscf instance. Initially this wizard should contain the collowing changes:
- set up database configuration. This should probably be stored in an external file somewhere. Possible by using the "external-config" plugin
- help define and set up external modules (module definitions and URL's)
- help generate dummy data so you quickly have an instance available to do some initial testing and evaluation with (hence: by moving the BootStrapStudies??, etc into this wizard instead of from the bootstrap)
Note that the latter should not happen when a database instance already has studies in it... Perhaps it should be possible to clean the database.
In the future this wizard should be able to do more, namely:
- import data from an external instance. Initially by some to be determined file format (XML?), and maybe later also by polling from a live instance?
- upgrade SQL schema's in the future?
These two features are currently out of scope, but keep in mind this is the direction we are heading

Change History

  Changed 3 years ago by work@…

  • status changed from new to assigned
  • summary changed from Factor out configuration into a separate configuration file to Set up an initial version of the 'getting started' wizard
  • description modified (diff)
  • reporter changed from business@… to work@…

Set up a 'getting started' wizard. On a clean installation of gscf the end-user should be presented with a wizard to help set-up the gscf instance. Initially this wizard should contain the collowing changes:

- set up database configuration. This should probably be stored in an external file somewhere. Possible by using the "external-config" plugin
- help define and set up external modules (module definitions and URL's)
- help generate dummy data so you quickly have an instance available to do some initial testing and evaluation with (hence: by moving the BootStrapStudies?, etc into this wizard instead of from the bootstrap)

Note that the latter should not happen when a database instance already has studies in it... Perhaps it should be possible to clean the database.

In the future this wizard should be able to do more, namely:
- import data from an external instance. Initially by some to be determined file format (XML?), and maybe later also by polling from a live instance?
- upgrade SQL schema's in the future?

These two features are currently out of scope, but keep in mind this is the direction we are heading

follow-up: ↓ 4   Changed 3 years ago by business@…

I think that it's OK for development mode to assume that there is also a local instance of 'sam' at 8182 and a local instance of 'nmcdsp' at 8183, to allow for concurrent development of those projects (but we should document that more clearly in the source code), but in production mode, obviously the URLs should be configured.

  Changed 3 years ago by work@…

  • description modified (diff)

in reply to: ↑ 2   Changed 3 years ago by work@…

Replying to business@…:

I think that it's OK for development mode to assume that there is also a local instance of 'sam' at 8182 and a local instance of 'nmcdsp' at 8183, to allow for concurrent development of those projects (but we should document that more clearly in the source code), but in production mode, obviously the URLs should be configured.

I agree, but that should also be configured in Config.groovy and not in BootStrapStudies?.groovy

  Changed 3 years ago by work@…

Moved module specific configuration from BootStrapStudies?.groovy to Config.groovy and moved instantiation of objects from Config.groovy to the BootStrap?.groovy in changelist r1187. Config.groovy should only contain configuration and all configuration should be in there, not in logic elsewhere...

Todo: now it is assumed that we always will have SAM or NMCDSP, however GSCF should always be able to run standalone. This means that module specific configuration does not belong in Config.groovy or BootStrap?.groovy altogether. One could even argue if the CommunicationManager? should be in there as it's SAM specific.

  Changed 3 years ago by work@…

depends on #183

  Changed 3 years ago by work@…

  • type changed from defect to enhancement

  Changed 3 years ago by work@…

  • milestone changed from 0.7 to 0.8

  Changed 3 years ago by work@…

  • component changed from General to Core Functionality

  Changed 3 years ago by work@…

created a new ajax flow r1648

  Changed 3 years ago by work@…

also include #337 here

  Changed 3 years ago by work@…

Initial working version committed in r1846

  Changed 3 years ago by work@…

  • milestone changed from Could have to 0.8.2

  Changed 3 years ago by business@…

* Change config dir to .gscf
* Ask for password change for admin account
* In home page, if someonly is logged in as admin, and running on in-mem database, give a warning box that the database is running in-mem, and provide a link to the setting up wizard.

  Changed 3 years ago by business@…

Idea: instead of using Grails environments to discern dbnp-demo, ci etc, use the name of the application context in e.g. Tomcat and read a config file based on that. Which would result in the name of the WAR file being used to determine the config file and thus the instance settings. That way, we don't have to recompile for different environments anymore and can just rename the WARs and put custom configs on the server.

  Changed 3 years ago by work@…

  • status changed from assigned to closed
  • resolution set to fixed

- working setup wizard
- changed default configuration
- added title with direct link to configure the appliction (with auto login to administrator) if setup is required
- r1859

Note: See TracTickets for help on using tickets.