config does not support pathing about pgrok HOT 6 CLOSED

sorry, mean ETCD server.

I saw how simpe the sql is and so its easier to use a simple store with basic search maybe.

from pgrok.

Also pgrokd -config pgrokd.exmaple.yml uses a different arg syntax. Would be nice if we used "--" for all config args ?

I believe both -config and --config works exactly the same, which is provided by the underlying CLI processing package we use.

Support expanding env vars for argument values should be easy using os.ExpandEnv, so pgrok --config $PWD/pgrok.example.yml would then work. Is this what you're thinking of / asking for?

from pgrok.

yes i think thats the nature of the problem. I need to go back into my test code though and check.

Can i ask something related ? It would be good is Postgresql was optional. Makes it much quicker to work without the extra complexity. I know that's more work though, so was wondering is there a way to run the code in a basic form without the need for Postgresql ?

from pgrok.

Can i ask something related ? It would be good is Postgresql was optional. Makes it much quicker to work without the extra complexity. I know that's more work though, so was wondering is there a way to run the code in a basic form without the need for Postgresql ?

I think the main point of using this tool is to have the concept of principals with SSO and thus stable URLs. So I guess it loses point in a "basic form" (whatever it means).

Is it because the external PostgreSQL requirement? Adding SQLite support is the most obvious choice but my deployments use PostgreSQL so I'd have to add bunch of DB integration tests to make sure other types of DB continues to work (as part of the support work).

from pgrok.

I still need to work on the issue, so will swing back to this.

its ok, am using cockroach with it without docker. I might add a simple ETC db later if your interested.

from pgrok.

I might add a simple ETC db later if your interested.

😁 What is a "ETC db later"?

from pgrok.