tl;dr - have a .bumpversion file which controls the version (along with the stirng in init /elsewhre)
back to my comment on #199 if you prefer I can use version from init in Vagrantfile
I was going to update the release.py and look into travis or something else to do it for every build.
But if there is a better way to do things, I’m all for it.
instead of passing it as version=x.y.z vagrant up centos
I can cook up a PR
@ceocoder It’s up to you. If it’s not too much work then go for it.
Otherwise I’ll do it manually.
not much work at all
In that case a PR would be much appreciated. :)
@earino There is already an issue for redshift. amjith/pgcli#18
I do a sudo pip install pgcli, but /usr/local/lib/python2.7/dist-packages/pgcli is created with 700 permissions and root owner. I know I can do a 755 on it, but wanted to point out that this is an issue.
Please ignore the earlier comment- apparently sudo preserves user's umask which is the cause of this problem.
btw, how do I resolve pkg_resources.DistributionNotFound: sqlparse>=0.1.14 ?
how do i view the log output when running pgcli?
ex. where would I see output of logger.info("hello") if I added that to pgcli code