feat: enable viking bot onboard command

[zhougit86]

Description

enable bot cli to create a init config

Related Issue

NA

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test update

Changes Made

-enable bot onboard command to create a initial config template in the config dir

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this on the following platforms:
  • Linux
  • macOS
  • Windows

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Screenshots (if applicable)

Additional Notes

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

xiaogang.zhou seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[chenjw]

Hi @zhougit86 , thank you so much for your contribution!
The onboard logic has been moved to vikingbot's gateway, and ov.conf will now be initialized automatically either when the gateway starts or when a chat is initiated. As a result, the onboard step has been simplified.
Additionally, regarding the changes to nanobot: we have removed the original config.json file, and all its configurations have been migrated to the bot key in ov.conf.

[zhougit86]

Hi @zhougit86 , thank you so much for your contribution! The onboard logic has been moved to vikingbot's gateway, and ov.conf will now be initialized automatically either when the gateway starts or when a chat is initiated. As a result, the onboard step has been simplified. Additionally, regarding the changes to nanobot: we have removed the original config.json file, and all its configurations have been migrated to the bot key in ov.conf.

Hi @chenjw thanks for reply, I think use vikingbot gateway to generate a default config can be a little bit confusing. use a seperate command to create a config and let user to key in configs can be more understandable? let me know your thinking

[zhougit86]

@chenjw Hi , I have create another PR to create a default value in init config. #600 please help comment. thanks