Cannot run the app locally

[petrbroz]

I've run into a couple of issues when trying to setup and run the app locally:

• When running npm run init, the script complains about a missing env. var. DEPLOY_TARGET which doesn't seem to be mentioned anywhere in the README
  • I tried following the "Deployment Instructions" link in the https://github.com/Autodesk-Forge/forge-digital-catalog#deployment section to see if perhaps I find some additional information there, but the link leads to a non-existent page
  • The "Local WebHooks Instructions" link is also broken
• When trying to run the local server app with npm run dev, the app crashes due to some error in the draco3d dependency
  • I've seen this issue in the past, too, but don't know how to resolve it :/
  • For now I've resolved the issue by removing the gltf-pipeline dependency from the code
• Then, after running npm run dev again, the Node.js process complained about "promise rejection not being handled", and exited
  • I fixed that by adding a .catch call to the adminController.wakeUp()... chain
  • After that I found out that this wakeUp() call is rejected with a 403 error (Only the bucket creator is allowed to access this api.)
  • It seems that the npm run init script configures a bucket for my app called digital-catalog-localhost-development but this bucket is not owned by my Forge credentials... did I do something wrong during the configuration?

[petrbroz]

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:

• The 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 successfully
• The bucket name you're generating during npm 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 own

[petrbroz]

Btw. 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): master...petrbroz:sample-review