How is jsreport-fs-store-aws-s3-persistence helpful in jsreports?

[Vishnu Menon]

I am migrating from jsreport 1 to latest jsreport. When checking the configuration i found that jsreport 1 was using jsreport-fs-store-aws-s3-persistence and saving the file structure to AWS cloud.

This configuration was done long ago and when i read through the documentation i was not if this is required.We are planning to have separate instances in development and production and export and import the templates on deployment.

Can i have some help to understand if this is required?

[jan_blaha]

That is a big jump from 1 to the latest. You will need to migrate first to v2 and then to v3.

Here are the migration notes for v2
https://jsreport.net/blog/jsreport-v2-released
https://jsreport.net/learn/v2-breaking-changes
Note to install v2, just update your package.json and set a v2 version and run npm i

Here are the migration notes for v3
https://jsreport.net/blog/jsreport-300-released
https://jsreport.net/learn/v3-migration-guide

You may have it easier if you, while still in v1, export from s3 to the local fs store and perform the update with fs.

And if you don't have hundreds of entities, you may have it easier to start with v3 from scratch and just copy-paste the entities' contents.

If you want to use s3 as the template store, here is the latest doc
https://jsreport.net/learn/fs-store#aws-s3

Good luck!