Closed TrevorBurgoyne closed 1 year ago
There seems to be some access constraint with terraform init
regarding the S3 bucket where the actual terraform configuration resides, preventing me from testing this without access (on my current machine anyways). I'll take a look at this later tonight. This might be solved by adding some base64 string to the bucket names (to avoid collisions) and some logic to check whether QASM buckets exist in the account of the deployer. It also could be a skill issue on my part.
It is probably worth looking into some interoperability (for both testing and deployment) between locally available and assumed AWS credentials. Either a config specification for AWS_PROFILE
or a "setup GUI" to do so would be handy to make sure things are deployed in the right spot, and make pure-standalone applications easier to test. (By pure-standalone, I mean applications that access only public resources or the necessary credentials are bundled in deployment, e.g. the demo build).
S3 Deep Links
What?
intercept_s3_protocol
as a top-level option in the config, which allows the user to specify which components should be allowed to handle redirects froms3://
links.s3://
link in a browser will automatically prompt the user to open the link in QASM. Depending on the active screen in the app, the link will then be passed to the component and loadedgrid
andmulticlassgrid
, links will be loaded as labels if they end in.json
, else they will try and be automatically loaded as an image directory.imagelabeler
, links will be loaded as a label if they end in.json
, an image if they end in.png
or.jpg
, or will prompt the user to select whether to load a folder as an image directory or annotation directory.and try navigating to a link like
s3://qasm-demo/grid-data/demo-1/images/
package.json
fields bc I was sick ofelectron-builder
complainingWhy?
Checks:
npm run qasm-push -- --config_path "./default-config.json"
to update the Demo siteBreaking Changes
To ensure that the protocol is properly removed on uninstall, a custom uninstall script had to be added. This seems to cause some collisions when trying to run
qasm-build
for an app that is already installed locally, and so existing apps with the same name must first be properly uninstalled using the app's uninstaller.