New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

export - import #221

Closed
pofider opened this Issue Jun 16, 2016 · 6 comments

Comments

Projects
None yet
2 participants
@pofider
Contributor

pofider commented Jun 16, 2016

extension jsreport-export-import capable of exporting/importing all the templates,scripts.. into/from file or stream. It would be useful for transferring templates between dev/test/prod environments, possibly automated with API.

The options for export would be:

  • entity types to export (default all)
  • export target
    • file stream (default)
    • target environment (user can optionally specify url and credentials to the target environment) (this has probably low priority)

The import options would be:

  • source file
  • drop - clean restore (drop whole entity type collection before inserting)
  • entity types to import (default all)

All of this would use our node document store API, so it would work universally across all kind of stores like fs, mongo, sql... This implies it would also provide another important feature which is migration across different data stores.

@pofider pofider added the enhancement label Jun 16, 2016

@pofider pofider changed the title from export - backup - import to export - import Dec 13, 2016

@zam6ak

This comment has been minimized.

Show comment
Hide comment
@zam6ak

zam6ak Dec 13, 2016

@pofider I think this look good, but I would not mix backup/restore functionality with import/export.
IMHO, backup/restore should be perhaps npm run {script} kind of activity and not something a user would do via UI (opportunity for users to mess up stuff)...

As for import/export it would be nice to support exporting and importing "a package".
A package could contain a template, few assets, a script or two. Something that to end user has meaning as a whole. It could be as simple as creating a ZIP of several selected export items.

I also agree with low priority for export/import to target environment.

zam6ak commented Dec 13, 2016

@pofider I think this look good, but I would not mix backup/restore functionality with import/export.
IMHO, backup/restore should be perhaps npm run {script} kind of activity and not something a user would do via UI (opportunity for users to mess up stuff)...

As for import/export it would be nice to support exporting and importing "a package".
A package could contain a template, few assets, a script or two. Something that to end user has meaning as a whole. It could be as simple as creating a ZIP of several selected export items.

I also agree with low priority for export/import to target environment.

@pofider

This comment has been minimized.

Show comment
Hide comment
@pofider

pofider Dec 14, 2016

Contributor

@zam6ak Ah ok, you are rather interested in export/import particular objects than whole collections. This make sense, but we gonna have to provide an entity tree in which you can select these items through check boxes.

Contributor

pofider commented Dec 14, 2016

@zam6ak Ah ok, you are rather interested in export/import particular objects than whole collections. This make sense, but we gonna have to provide an entity tree in which you can select these items through check boxes.

@pofider

This comment has been minimized.

Show comment
Hide comment
@pofider

pofider Dec 14, 2016

Contributor

I've implemented your request and add the possibility to select particular entities for import. I'm close to release now. See the demo

export

Good news is that this also work across the stores. It makes it very easy to migrate data from file system to mongo or sql now.

Contributor

pofider commented Dec 14, 2016

I've implemented your request and add the possibility to select particular entities for import. I'm close to release now. See the demo

export

Good news is that this also work across the stores. It makes it very easy to migrate data from file system to mongo or sql now.

@zam6ak

This comment has been minimized.

Show comment
Hide comment
@zam6ak

zam6ak Dec 15, 2016

Great ! I will test as soon as new release is out

zam6ak commented Dec 15, 2016

Great ! I will test as soon as new release is out

@pofider

This comment has been minimized.

Show comment
Hide comment
@pofider

pofider Dec 15, 2016

Contributor

The preview can be installed like this:

npm install jsreport-import-export --production
npm install jsreport-studio@1.2.3 --production

This will be part of the next jsreport release, which should come after the Christmas .

Contributor

pofider commented Dec 15, 2016

The preview can be installed like this:

npm install jsreport-import-export --production
npm install jsreport-studio@1.2.3 --production

This will be part of the next jsreport release, which should come after the Christmas .

@pofider

This comment has been minimized.

Show comment
Hide comment
@pofider

pofider Jan 2, 2017

Contributor

This is now released in jsreport@1.3.0. We can solve the coming problems in separate issues.

Contributor

pofider commented Jan 2, 2017

This is now released in jsreport@1.3.0. We can solve the coming problems in separate issues.

@pofider pofider closed this Jan 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment