You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's make sure that all dfx commands that need it will work on mainnet by adding the --network option (look at other places that we have already done this). Also we should probably not use the canister name but the canister id in our dfx commands, and we might want to get that from the CANISTER_ID whatever it is called environment variable.
are we sure that the authenticated file uploader will work in production? addController doesn't seem like it will work. We need to make sure that all functions in the dfx directory will work in production
Are we sure we should be using canister names for our dfx operations? It seems much safer to use canister ids,
The text was updated successfully, but these errors were encountered:
Let's make sure that all dfx commands that need it will work on mainnet by adding the --network option (look at other places that we have already done this). Also we should probably not use the canister name but the canister id in our dfx commands, and we might want to get that from the CANISTER_ID whatever it is called environment variable.
The text was updated successfully, but these errors were encountered: