kegadmin: interface refresh issues about kegbot-server HOT 7 CLOSED

fixed, thanks!

from kegbot-server.

Sweet!

So if I'm going to integrate this change into my production server, do i just pull the repos and restart the services, or do i need to do a build again?

from kegbot-server.

So if I'm going to integrate this change into my production server, do i just pull the repos
and restart the services, or do i need to do a build again?

Yep! Here are the basic steps which will work for 99% of code changes:

http://kegbot.org/docs/server-guide/upgrade-kegbot.html#upgrade-procedure

Since this change is just to the templates, there's no need to do migrate (datbase updates), kb_regen_stats, or collectstatic. But it doesn't hurt..

from kegbot-server.

I'm running a clone from github, not pip. I guess what I'm asking is that after i do a pull, do i need to run ./setup.py or can i just restart the services... does the code run from my cloned location or from somewhere else?

from kegbot-server.

That's covered in step 2 :) -- ./setup.py develop is what you need.

(And actually, when you installed with "develop", most code runs from your cloned location, so again you might not even need to do this step, depending on the update. If I introduce a new third party dependency, however, you definitely need to do it in order to bring it in. So to keep the instructions simple and easy to remember, I'd just do it out of habit.)

from kegbot-server.

Cool, Thx. I've been a professional software engineer for over 10 years, but this is, surprisingly, my first experience with both django & python!

from kegbot-server.

Cool, Thx. I've been a professional software engineer for over 10 years, but
this is, surprisingly, my first experience with both django & python!

It will get less weird :)

from kegbot-server.