New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TurboGears 2.2.2 #11
Comments
Now that I have pulled the repo, when I visit localhost:8080 I'm met with an error message in the browser saying Requested resource does not exist: /services `starting h1 20:34:47,663 INFO [bq.preference] FINISHED: http://127.0.0.1:8080/preference?view=deep |
I tried again today. Browser says same thing, and terminal has a lot of output. I'm actually gonna post the whole thing cause there seem to be some import errors and stuff going on before "starting h1"
|
I pulled the github fresh this morning, and I pulled the container to make sure it's working. When I open Bisque, a red error box pops up telling me "requested resource does not exist: /services" or something along those lines. It goes away when I try to copy/paste. I'll paste the logs from my terminal.
|
Stale issue message |
TurboGears 2.2.2
This is the second upgrade in the process. If you have any questions, tag @amilworks on here.
Current Version:
TurboGears2==2.2.0
Upgrade Version:
TurboGears2==2.2.2
As you are going through, check off what Step you completed to make it easier for us to help, and for you to feel accomplished.
Getting Started
Step 1. Clone the Repo
GOAL
cd tg-upgrade
and you should see a folder structure like thisStep 2. Verify Everything Works
GOAL
You have two choices to verify that the repo is working.
Option 1. Pull the Latest Docker Build (Recommended)
The repo is rebuilt and pushed automatically after a successful push/merge on GitHub. Download the latest image by running the following command:
You can run this image to verify BisQue is working and able to run locally on your system by running:
You should see BisQue on http://localhost:8080/ in your browser. If not, paste the logs below and we will take a look.
Option 2. Build the Image
Building the image from scratch is what you will end up doing throughout the upgrade process. Luckily, we automated it to where you run a
Makefile
.If you
vim Makefile
, you will see it's a series of basic commands. I suggest you Edit this file and--tag
the image something different and update the version you are upgrading instead ofamilworks/bisque05-caffe-xenial:flour-tg2.2
. You can leave it but it's kind of long. Once the build is done, verify that BisQue comes up on your local system just as above:You should see BisQue on http://localhost:8080/ in your browser. If not, paste both the Build and Run Logs below and we will take a look.
Step 3. Make Changes/Break Stuff
GOAL
TurboGears2==2.2.2
, fix problems that arise, document changes.Create a new branch
Creating a new branch will enable you to make changes, nuke your own branch over and over again, and maintain a clean copy of the original branch when you need to start fresh for the millionth time.
Open
source/requirements.txt
with your favorite editor (hopefully Vim). Change the version to the one you are assigned, and save the file.Here is the link to the line you will update.
Push to GitHub
You made changes and you want to have version control. Push your new branch and changes to GitHub by running:
Step 4. Build and Run!
GOAL
Once you made your changes, make sure you
cd ..
out ofsource/
and are back to the tree view displayed above. You should see a file calledMakefile
. You can Edit this file as mentioned inOption 2.
or simply run the following command to build the image with your updated TurboGears2.While its building, make sure that there are no errors during the
pip installs
. Typically errors are skipped over in favor of a successful build. I know, right?Next, once the build is finished, run the image and verify BisQue comes up on your local system:
If everything is successful, push your branch to GitHub if you have not already, file a pull request, and pat yourself on the back. Job well done. We will review it and test it on our production-like setup and give feedback if any issues arise.
Post Upgrade
Use this issue to document any issues you faced during the upgrade process. Log dumps can be thrown here as well. Try to use the code syntax for large blocks of code so we can easily read through it. Otherwise, go crazy.
The text was updated successfully, but these errors were encountered: