ICPHackthonAICertification

Welcome to your new ICPHackthonAICertification project and to the Internet Computer development community. By default, creating a new project adds this README and some template files to your project directory. You can edit these template files to customize your project and to include your own code to speed up the development cycle.

To get started, you might want to explore the project directory structure and the default configuration file. Working with this project in your development environment will not affect any production deployment or identity tokens.

To learn more before you start working with ICPHackthonAICertification, see the following documentation available online:

• Quick Start
• SDK Developer Tools
• Rust Canister Development Guide
• ic-cdk
• ic-cdk-macros
• Candid Introduction

If you want to start working on your project right away, you might want to try the following commands:

cd ICPHackthonAICertification/
dfx help
dfx canister --help

Running the project locally

If you want to test your project locally, you can use the following commands:

# Starts the replica, running in the background
dfx start --background
# Or
dfx start --clean
# To stop
dfx stop
sudo kill [pid]

# Generate types declatations to use on the FE
dfx generate ICPHackthonAICertification_backend

# Deploys your canisters to the replica and generates your candid interface
dfx deploy --playground
# Or
dfx deploy ICPHackthonAICertification_backend --playground
dfx deploy ICPHackthonAICertification_frontend --playground

# Deply to IC and stop canisters
dfx deploy --network ic
dfx canister stop --network ic --all
# Re-start
dfx canister start --network ic --all
https://bt6zq-vaaaa-aaaaj-azueq-cai.icp0.io/
https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.icp0.io/?id=bu77e-yyaaa-aaaaj-azuea-cai

# Troubleshooting
cargo build
sudo apt install build-essential
rustup target add wasm32-unknown-unknown

Once the job completes, your application will be available at http://localhost:4943?canisterId={asset_canister_id}.

If you have made changes to your backend canister, you can generate a new candid interface with

npm start

at any time. This is recommended before starting the frontend development server, and will be run automatically any time you run dfx deploy.

If you are making frontend changes, you can start a development server with

npm start

Which will start a server at http://localhost:8080, proxying API requests to the replica at port 4943.

Note on frontend environment variables

If you are hosting frontend code somewhere without using DFX, you may need to make one of the following adjustments to ensure your project does not fetch the root key in production:

• setDFX_NETWORK to ic if you are using Webpack
• use your own preferred method to replace process.env.DFX_NETWORK in the autogenerated declarations
  • Setting canisters -> {asset_canister_id} -> declarations -> env_override to a string in dfx.json will replace process.env.DFX_NETWORK with the string in the autogenerated declarations
• Write your own createActor constructor