Eric Swanson

The use of "remote canisters" might be a good fit here: https://github.com/dfinity/sdk/blob/master/CHANGELOG.adoc#feat-remote-canister-support

> @bitdivine I think you recently did some work to deploy Internet identity from dfx, is that correct? @ericswanson-dfinity would that be the solution here? That work is pretty specific...

dfx 0.10.1 included these three tarballs (see https://github.com/dfinity/sdk/blob/0.10.1/nix/sources.json) - https://github.com/dfinity/motoko/releases/download/0.6.28/motoko-base-library.tar.gz - https://github.com/dfinity/motoko/releases/download/0.6.28/motoko-macos-0.6.28.tar.gz - https://github.com/dfinity/motoko/releases/download/0.6.28/motoko-linux64-0.6.28.tar.gz And this is what's in Text.mo around line 83: ``` /// Returns the order of `t1`...

> I've fixed the issue of calling `moc --print-deps` more than once for a given file. However a small issue remains: it outputs `Building dependencies graph.` twice on `dfx deploy`....

> actually, it seems like `dfx nn install` expects port `8080`. can we change this please? By "change this," what do you mean exactly? Change the document here? Or change...

In a default project, the frontend has a dependency on the backend. The call may be to `moc --print-deps` while building the dependencies graph. ``` "frontend": { "dependencies": [ "backend"...

Trying to repro, I get stuck at step > 5. Open local "website" canister in browser, sign-in, and register a user name

I don't know who decides this stuff. This was copied from https://github.com/dfinity-lab/common/blob/master/pkgs/overlays/packages/cargo-deny/buildtime.toml