Open petrbroz opened 4 years ago
Thank you for adding the DEPLOY_TARGET
default, this part is now working well.
The remaining comments will still need to be addressed at some point, specifically:
gltf-pipeline
dependency is still preventing the server app from starting... I had to remove it from your code in order to be able to run the app successfullynpm run init
will likely not be owned by the other developer's Forge credentials. I've resolved that issue by manually editing the bucket name in config/development.json to one of the buckets I actually ownBtw. here's my fork with the modifications that were needed to get the app running (not including the bucket name change in the config JSON): https://github.com/Autodesk-Forge/forge-digital-catalog/compare/master...petrbroz:sample-review
I've run into a couple of issues when trying to setup and run the app locally:
npm run init
, the script complains about a missing env. var.DEPLOY_TARGET
which doesn't seem to be mentioned anywhere in the READMEnpm run dev
, the app crashes due to some error in thedraco3d
dependencygltf-pipeline
dependency from the codenpm run dev
again, the Node.js process complained about "promise rejection not being handled", and exited.catch
call to theadminController.wakeUp()...
chainwakeUp()
call is rejected with a 403 error (Only the bucket creator is allowed to access this api.
)npm run init
script configures a bucket for my app calleddigital-catalog-localhost-development
but this bucket is not owned by my Forge credentials... did I do something wrong during the configuration?