"go run . serve" could emit the config values that it is using to the console.

[gedw99]

"go run . serve" could emit the config values that it is using to the console when it starts up.

I was just going though making a .vscode folder with a launch.json and a .env to make it easy to debug things, and found it easier to manage whats being used if the "serve" command also printed the values it is using.

[gernest]

Can you elaborate ? I'm confused what this is about.

[gedw99]

thanks for asking ...

So these are the possible args...

go run . serve -h
NAME:
   vince serve - Starts vince web server

USAGE:
   vince serve [command [command options]] 

OPTIONS:
   --listen value                       host:port to dind the servser (default: ":8080") [$VINCE_LISTEN]
   --data value                         directory to store data (default: "vince-data") [$VINCE_DATA]
   --autoTLS                            enables automatic tls (default: false) [$VINCE_AUTO_TLS]
   --acmeEmail value                    email address for atomatic tls [$VINCE_ACME_EMAIL]
   --acmeDomain value                   domain for atomatic tls [$VINCE_ACME_DOMAIN]
   --url value                          url resolving to this vince instance (default: "http://localhost:8080") [$VINCE_URL]
   --demo value                         Website to use as a demo (default: "vinceanalytics.com") [$VINCE_DEMO_URL]
   --domains value [ --domains value ]  list of domains to create on startup [$VINCE_DOMAINS]
   --profile                            registrer http profiles on /debug/ path (default: false) [$VINCE_PROFILE]
   --adminName value                    administrator name [$VINCE_ADMIN_NAME]
   --adminPassword value                administrator password [$VINCE_ADMIN_PASSWORD]
   --help, -h                           show help (default: false)

This is what it does right now if you just start it.

apple@apples-MacBook-Pro vince % go run . serve
2024/12/04 13:05:50 [JOB 1] WAL 000067 stopped reading at offset: (vince-data/ops/000067.log: 0); replayed 0 keys in 0 batches
2024/12/04 13:05:50 [JOB 1] WAL 000002 stopped reading at offset: (data/000002.log: 0); replayed 0 keys in 0 batches
2024/12/04 13:05:50 INFO loading translation data
2024/12/04 13:05:50 INFO complete loading translation elapsed=36.083µs keys=0
2024/12/04 13:05:50 INFO starting event processing loop
2024/12/04 13:05:50 INFO starting server addr=:8080

It's not telling me what values it is using.

It would be useful if always printed each one when it starts up.

It does not have to tell you if its from the flags or .env or something else because thats overkill.

what do you think ? It's an easy change but just makes it easy to know where .env values re being applied. Also good for when deployed with docker and k8, etc

[gernest]

thanks for asking ...

So these are the possible args...

go run . serve -h
NAME:
   vince serve - Starts vince web server

USAGE:
   vince serve [command [command options]] 

OPTIONS:
   --listen value                       host:port to dind the servser (default: ":8080") [$VINCE_LISTEN]
   --data value                         directory to store data (default: "vince-data") [$VINCE_DATA]
   --autoTLS                            enables automatic tls (default: false) [$VINCE_AUTO_TLS]
   --acmeEmail value                    email address for atomatic tls [$VINCE_ACME_EMAIL]
   --acmeDomain value                   domain for atomatic tls [$VINCE_ACME_DOMAIN]
   --url value                          url resolving to this vince instance (default: "http://localhost:8080") [$VINCE_URL]
   --demo value                         Website to use as a demo (default: "vinceanalytics.com") [$VINCE_DEMO_URL]
   --domains value [ --domains value ]  list of domains to create on startup [$VINCE_DOMAINS]
   --profile                            registrer http profiles on /debug/ path (default: false) [$VINCE_PROFILE]
   --adminName value                    administrator name [$VINCE_ADMIN_NAME]
   --adminPassword value                administrator password [$VINCE_ADMIN_PASSWORD]
   --help, -h                           show help (default: false)

This is what it does right now if you just start it.

apple@apples-MacBook-Pro vince % go run . serve
2024/12/04 13:05:50 [JOB 1] WAL 000067 stopped reading at offset: (vince-data/ops/000067.log: 0); replayed 0 keys in 0 batches
2024/12/04 13:05:50 [JOB 1] WAL 000002 stopped reading at offset: (data/000002.log: 0); replayed 0 keys in 0 batches
2024/12/04 13:05:50 INFO loading translation data
2024/12/04 13:05:50 INFO complete loading translation elapsed=36.083µs keys=0
2024/12/04 13:05:50 INFO starting event processing loop
2024/12/04 13:05:50 INFO starting server addr=:8080

It's not telling me what values it is using.

It would be useful if always printed each one when it starts up.

It does not have to tell you if its from the flags or .env or something else because thats overkill.

what do you think ? It's an easy change but just makes it easy to know where .env values re being applied. Also good for when deployed with docker and k8, etc

Do you realise all default values that vince uses are right there on the output you shared?

So all default values can be seen, the rest you provide your self. I don't see the need to go further than that.

[gedw99]

main...gedw99:vince:main

I am adding .vscode debugging. both with cli args and .env file. Makes it easy to work on the code with you.

Can PR it if you want. It does not touch the code..

[gernest]

I'm not sure what you are looking for. Default values are listed with -h flag. The rest should be on your control, there is no hidden values used by vince.

Basically what is in you .env or supplied on the commands is what is used.

[gedw99]

It only prints these 2 currently:

2024/12/04 13:29:03 [JOB 1] WAL 000116 stopped reading at offset: (vince-data/ops/000116.log: 0); replayed 0 keys in 0 batches
2024/12/04 13:29:03 [JOB 1] WAL 000002 stopped reading at offset: (data/000002.log: 0); replayed 0 keys in 0 batches
2024/12/04 13:29:03 INFO loading translation data
2024/12/04 13:29:03 INFO complete loading translation elapsed=27.042µs keys=0
2024/12/04 13:29:03 INFO starting event processing loop
2024/12/04 13:29:03 INFO starting server addr=:8090
Detaching and terminating target process
connection error: Error: read ECONNRESET
dlv dap (42959) exited with code: 0

.env file :)

VINCE_LISTEN=:8090
VINCE_DATA=vince-data

But as we know there are many ore values possible to be passed in

VINCE_LISTEN=:8080
VINCE_DATA=vince-data
VINCE_AUTO_TLS=false
VINCE_ACME_EMAIL=
VINCE_ACME_DOMAIN=
VINCE_URL=http://localhost:8080
VINCE_DEMO_URL=vinceanalytics.com
VINCE_DOMAINS=vinceanalytics.com
VINCE_PROFILE=
VINCE_ADMIN_NAME=acme
VINCE_ADMIN_PASSWORD=1234

So it would be useful if the first thing it did is tell you the values it using.

[gernest]

Oh! I see your point now.

You want to be able to see what final values that vince actually applied right ?

For now I am only focusing on stability, I have no need for this at the moment so it is not possible to do so and It does not align with current roadmap.

If you have other questions regarding your use for vince please feel free to ask.

[gedw99]

Oh! I see your point now.

You want to be able to see what final values that vince actually applied right ?

Yes

For now I am only focusing on stability, I have no need for this at the moment so it is not possible to do so and It does not align with current roadmap.

If you have other questions regarding your use for vince please feel free to ask.