base on null ## Availup To run an Avail light client, simply run the following command: ```bash curl -sL1 avail.sh | bash ``` or, with `wget`: ```bash wget --secure-protocol=TLSv1_2 -q -O - avail.sh | bash ``` You can pass additional flags to the script like: ```bash curl -sL1 avail.sh | bash -s -- --network turing ``` Currently available flags are: * `network`: can be one of the following: [`mainnet`, `turing`, `local`] * `config`: path to the configuration file, availup will generate a config if this flag is not specified * This flag is always required when running a local testnet * `config_url`: URL to a valid YAML configuration file, availup will download the config if this flag is specified * If the configuration is invalid, the script will exit * This flag will only work with mainnet configurations * `identity`: path to the identity file, availup will generate a config if this flag is not specified * It is important to keep your identity file safe! * `app_id`: application ID to run the light client (defaults to `0`) * It is recommended to not change this flag unless you require the app-specific mode. * `upgrade`: takes `y` and `yes` as valid arguments, indicating that the `avail-light` binary should be upgraded * Using this flag wipes your existing data and config, use with caution! This flag does not guarantee that the binary will be upgraded. * `force_wsl`: takes `y` and `yes` as valid arguments, the script exits on WSL systems by default. This flag can removed in the future. * `tracking_service`: takes `y` and `yes` as valid arguments, enabling `avail-light` tracking on a provided server * `tracking_service_address`: URL to the tracker server, i.e. `http://127.0.0.1:8989` * `operator_address`: Address of the Light Client operator; this field is sent to the tracking service You can use a custom config by passing it to `availup` as a flag: ```bash # create the config: touch ~/config.yml # edit the config: nano ~/config.yml # and rerunning the script: curl -sL1 avail.sh | bash -s -- --config ~/config.yml ``` > ⚠️ It is not recommended to modify the default config stored in `~/.avail/config/config.yml` as that gets wiped on > each run. If you have a seed phrase that you'd like to use instead of the generated one, you can modify `~/.avail/identity/identity.toml`, alternatively, you can pass it as a flag: ```bash # edit default identity nano ~/.avail/identity/identity.toml # the script picks up the new identity automatically: curl -sL1 avail.sh | bash # create a new identity touch ~/identity.toml nano ~/identity.toml # the script uses the identity at the path curl -sL1 avail.sh | bash -s -- --identity ~/identity.toml ``` > ℹ️ The script persists your identity file between runs. Deleting the file will cause a new one to be generated on > the next run. Alternatively, you can pass a specific application ID with `availup`: ```bash rm ~/.avail/turing/config.yml # and rerunning the script with flags: curl -sL1 avail.sh | bash -s -- --app_id 1 ``` > ℹ️ Adding an app ID disables the LC mode and runs your client in an app-specific mode, this might not be your > intention. In availup, binary upgrades are enabled by default to ensure you always have the latest supported version. In order to skip default upgrades you can simply pass the `--upgrade` flag like: ```bash curl -sL1 avail.sh | bash -s -- --upgrade n ``` > ℹ️ Upgrading the LC only works if the binary was installed with the latest `availup` script or cargo. If default updates are skipped, everytime the user will be prompted for a permission to upgrade once a new release is made available. To run the light client on WSL systems, use the `--force_wsl` flag like: ```bash curl -sL1 avail.sh | bash -s -- --force_wsl y ``` > ℹ️ Running this flag on any other system does nothing. To load a configuration from a URL, use the `--config_url` flag like: ```bash curl -sL1 avail.sh | bash -s -- --config_url https://raw.githubusercontent.com/availproject/availup/main/configs/sophon.yml ``` > ℹ️ The configuration file must be a valid YAML file, otherwise the script will exit. ", Assign "at most 3 tags" to the expected json: {"id":"9107","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"