kegberry upgrade takes care of stepping into the virtualenv for you – once again, this is assuming you installed with kegberry install.
To put it another way, if you know where your virtualenv is and how to step into it, you can ignore the kegberry helper tool and just follow the upgrade procedure that you outlined.
Has the new version not hit your servers yet because I’m trying to upgrade and I get an error that I already have version 1.1b2 installed.
pi@raspi // $ kegberry upgrade
oOOOOOo
,| oO Kegberry v2.0.0b3 - http://kegberry.com
//| |
\\| | "Who cares how time advances? I am drinking ale today."
`| | -- Edgar Allen Poe
`-----`
INFO : Checking for `kegberry` command update
INFO : Updating kegbot-server distribution ...
INFO : Updating kegbot-pycore distribution ...
INFO : Running `kegberry kegbot upgrade` ...
Version 1.1b2 already installed.
I’ve tried upgrading both in the virtualenv and with the kegberry wrapper as posted above. Am I missing something?
Sorry for the confusion. The kegbot user doesn’t have a password.
You should run kegberry upgrade as the default login user (root on Digital Ocean). The command handles running sudo when necessary – which root can do, but kegbot cannot.
Hope that makes sense. I’ll try to make this a little less painful in future revisions…
I created my server on Digital Ocean and followed those instructions during setup so I started by using a portion of those instructions that briefly discussed upgrading. I typed in the following commands:
I then followed the pip install upgrade procedure from the link above in the thread from mikey. The first time I tried this it didn’t work, but out of frustration in trying other procedures and getting the “password” I tried it again and it worked. Not exactly sure why since I’m kind of flying by the seat of my pants when it comes to programming.