Topics created by Matthew Kee

You can make the following change to your server.js file which boots jsreport.
This will update the jsreport user password during the startup to an env variable value,

const jsreport = require('jsreport')() if (process.env.JSREPORT_CLI) { // export jsreport instance to make it possible to use jsreport-cli module.exports = jsreport } else { jsreport.init().then(() => { // *** here is the change return jsreport.documentStore.collection('users').update({ username: 'jsreport' }, { $set: { password: require('password-hash').generate(process.env.YOUR_VARIABLE) } }) // *** change end // running }).catch((e) => { // error during startup console.error(e.stack) process.exit(1) }) }

Worked like a charm. Thanks for all the help!

I can't replicate this so far. I have an entity like this and I can edit it in studio without issues.

{ "name": "t", "engine": "handlebars", "recipe": "chrome-pdf", "shortid": "YDk7AYwFfX", "creationDate": { "$$date": 1673020613229 }, "modificationDate": { "$$date": 1673285032858 }, "_id": "khiOoblGOqkQn9bg", "$entitySet": "templates", "chrome": { "printBackground": true } }

Could you try it in a private browser window? Maybe there is something wrong cached in the browser.

Figured this out. In case anyone else cares, you can click "profile" on the report and see the console.log output.