Initialize DB when VATZ is initialized.

[rootwarp]

1. Type of change

Please delete options that are not relevant.

• New feature
• Enhancement
• Bug/fix (non-breaking change which fixes an issue)
• others (anything other than above)

---

2. Summary

Please include a summary of the changes and which issue is fixed or solved.

Related: # (issue)

close #421

Summary

Initialize DB when vatz init executed.

---

3. Comments

Please, leave a comments if there's further action that requires.

[rootwarp]

ok      github.com/dsrvlabs/vatz/utils  (cached)
?       github.com/dsrvlabs/vatz        [no test files]
ok      github.com/dsrvlabs/vatz/cmd    3.137s  coverage: 19.1% of statements
ok      github.com/dsrvlabs/vatz/manager/api    0.501s  coverage: 0.0% of statements [no tests to run]
ok      github.com/dsrvlabs/vatz/manager/config 0.268s  coverage: 91.2% of statements
ok      github.com/dsrvlabs/vatz/manager/dispatcher     0.894s  coverage: 7.8% of statements
ok      github.com/dsrvlabs/vatz/manager/executor       1.144s  coverage: 68.9% of statements
ok      github.com/dsrvlabs/vatz/manager/healthcheck    0.628s  coverage: 46.5% of statements
ok      github.com/dsrvlabs/vatz/manager/plugin 7.026s  coverage: 67.4% of statements
?       github.com/dsrvlabs/vatz/manager/types  [no test files]
?       github.com/dsrvlabs/vatz/mocks  [no test files]
ok      github.com/dsrvlabs/vatz/monitoring/prometheus  1.300s  coverage: 0.0% of statements
ok      github.com/dsrvlabs/vatz/rpc    2.632s  coverage: 67.2% of statements
ok      github.com/dsrvlabs/vatz/utils  1.671s  coverage: 13.3% of statements
go build -ldflags="-X 'github.com/dsrvlabs/vatz/utils.Version=issue#421' -X 'github.com/dsrvlabs/vatz/utils.Commit=a06a1fe'" -v
rootwarp@Mindhack2021 ~/g/d/vatz issue#421 >

[heejin-github]

LGTM

[xellos00]

@rootwarp
I think I should have catch this error,
but is this command shouldn't valid for when I init to other directory?

or we skipped --home command?

 ./vatz init --home /Users/dongyookang/test
Error: unknown flag: --home
Usage:
   init [flags]

Flags:
  -h, --help            help for init
  -o, --output string   New config file to create (default "default.yaml")

panic: unknown flag: --home

goroutine 1 [running]:
main.main()
        /Users/dongyookang/ffplay/GolandProjects/dsrvlabs/vatz/main.go:20 +0x3a
 ✘ dongyookang DK 🚀   ~/ffplay/GolandProjects/dsrvlabs/vatz   main ✚
 

[rootwarp]

@rootwarp I think I should have catch this error, but is this command shouldn't valid for when I init to other directory?

or we skipped --home command?

 ./vatz init --home /Users/dongyookang/test
Error: unknown flag: --home
Usage:
   init [flags]

Flags:
  -h, --help            help for init
  -o, --output string   New config file to create (default "default.yaml")

panic: unknown flag: --home

goroutine 1 [running]:
main.main()
        /Users/dongyookang/ffplay/GolandProjects/dsrvlabs/vatz/main.go:20 +0x3a
 ✘ dongyookang DK 🚀   ~/ffplay/GolandProjects/dsrvlabs/vatz   main ✚
 

@xellos00 Thanks for the review.
--home flag should be available, so I'll be back with a new commit. 👍

[rootwarp]

@xellos00 I'm considering for adding --home flag, but we need to discuss more before implementing it.

When we try to execute vatz start command, we can use --config flag to choose the exact configuration file. So, if we try to make the home directory selectable, the selected directory should be written on the config file and vatz should load home directory and use it to load DB and configs.

Moreover, if we add home field on the config file, we may update other commands because those are just using the VATZ home directory as $HOME/.vatz implicitly.

So, whole steps I expected are,

1. Add --home flag on init command. The init command initializes DB and creates new configs. And it also adds home field on the new configs.
2. Update plugin command to load home directory from config.
3. Update start command to load home directory from config.

[xellos00]

@xellos00 I'm considering for adding --home flag, but we need to discuss more before implementing it.

When we try to execute vatz start command, we can use --config flag to choose the exact configuration file. So, if we try to make the home directory selectable, the selected directory should be written on the config file and vatz should load home directory and use it to load DB and configs.

Moreover, if we add home field on the config file, we may update other commands because those are just using the VATZ home directory as $HOME/.vatz implicitly.

So, whole steps I expected are,

1. Add --home flag on init command. The init command initializes DB and creates new configs. And it also adds home field on the new configs.
2. Update plugin command to load home directory from config.
3. Update start command to load home directory from config.

@rootwarp
In fact, I understood your expected behaviors regarding --home flag in command init, start.
yet I am little bit confused after I read your comment.

let's have further discussion tomorrow for this.
I sent invitation as below.

[xellos00]

Confirmed!!

 dongyookang DK 🚀   ~/ffplay/GolandProjects/dsrvlabs/vatz   issue#421 ±✚
 ./vatz init       
2023-04-11T06:35:58-05:00 INF init module=main
2023-04-11T06:35:58-05:00 INF create file default.yaml module=main
2023-04-11T06:35:58-05:00 INF initDB /Users/dongyookang/.vatz/vatz.db module=db
2023-04-11T06:35:58-05:00 INF newWriter /Users/dongyookang/.vatz/vatz.db module=db
2023-04-11T06:35:58-05:00 INF Create DB Instance module=db
 dongyookang DK 🚀   ~/ffplay/GolandProjects/dsrvlabs/vatz   issue#421 ±✚
 ./vatz plugin list
2023-04-11T06:36:12-05:00 INF List plugins module=plugin
2023-04-11T06:36:12-05:00 INF List module=plugin
2023-04-11T06:36:12-05:00 INF newReader /Users/dongyookang/.vatz/vatz.db module=db
2023-04-11T06:36:12-05:00 INF Create DB Instance module=db
2023-04-11T06:36:12-05:00 INF List Plugin module=db
+------+--------------+------------+---------+
| NAME | INSTALL DATA | REPOSITORY | VERSION |
+------+--------------+------------+---------+
+------+--------------+------------+---------+
 dongyookang DK 🚀   ~/ffplay/GolandProjects/dsrvlabs/vatz   issue#421 ±✚
 

 dongyookang DK 🚀   ~
 ls -al | grep .vatz
drwxr-xr-x    3 dongyookang  staff      96 Apr 11 06:26 .vatz
drwxr-xr-x    5 dongyookang  staff     160 Dec  1 22:11 .vatz_backup
 dongyookang DK 🚀   ~
 rm -rf .vatz     
 dongyookang DK 🚀   ~
 ls -al | grep .vatz
drwxr-xr-x    5 dongyookang  staff     160 Dec  1 22:11 .vatz_backup
 dongyookang DK 🚀   ~
 ls -al | grep .vatz
drwxr-xr-x    3 dongyookang  staff      96 Apr 11 06:35 .vatz
drwxr-xr-x    5 dongyookang  staff     160 Dec  1 22:11 .vatz_backup
 dongyookang DK 🚀   ~
