Unable to launch commuter

I am trying to set up commuter to work with an s3 storage backend on an Amazon EC2 instance.

Referencing the documentation at https://github.com/nteract/commuter I have set the relevant environment variables with the following commands:

export COMMUTER_STORAGE_BACKEND=s3
export COMMUTER_BUCKET=bucket-name

But when trying to launch commuter via commuter command I get the following error:

CONFIGURED DISCOVERY none
Running in the current working directory,  /home/jupyter-tljh_admin
internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module './config/babel.flow.config'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/usr/local/share/.config/yarn/global/node_modules/@nteract/webpack-configurator/index.js:12:25)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)

Would love to get this set up, is this a reasonable place to ask for this sort of help? Thanks,

[rgbkrk]

It’s not fixed and not ready for consumption currently. We’re doing some internal fixups and will be posting a refreshed commuter soon.

Curiosity – will you be backing notebooks with local storage or S3?

[rgbkrk]

I just migrated all the issues for commuter over to this repo and will start handling an overhaul of commuter with a few other folks. My most recent relevant update is from https://github.com/nteract/commuter/issues/249#issuecomment-456947550:

Super sorry! This is the right repo. We’ve been going through some structural changes with the nteract repos so I didn’t get this one back to a normal state. On my end I’ve been focused on an internal fork of commuter (at Netflix) and want to get the changes to be minimal on both while getting prod mode back to working for the deployed version externally.

I’ve sadly not been running with the commuter command, instead using either yarn dev or yarn start (after assets have been built). Does that work for you on master for the moment?