BB2-823: Attempt to fix docker issues#3
Conversation
|
@bfausett77 I think the readme could use a little work, here are a couple of things I would add:
|
Excellent suggestions. I've updated the README accordingly. |
dtisza1
left a comment
There was a problem hiding this comment.
@bfausett77 I was able to get the client & server to startup OK. However, I'm not seeing any data in the app. From the docker-compose logging, it looks OK to me, but not seeing data returned.
Also, you can copy some of the python related configs from the BB2 .gitignore file so that "*.pyc" and other files don't get included in the repo.
LINK: https://github.com/CMSgov/bluebutton-web-server/blob/master/.gitignore
For example, I think everything could be included up to the "# Djano" comment and maybe some other items.
|
@dtisza1 I had the same thing happen on mine... @bfausett77 i'm wondering if you setup something locally that isn't checked in that we didn't setup on ours? |
I have updated the .gitignore file and removed the folders/files that shouldn't be there. |
Worked with you to find the issue in the views.py file - it was the if-else statement that was the issue |
|
@bfausett77 Just tried it after your last updates. Still having an issue. It looks related to the callback and exchanging the code for an access token with the /v2/o/token/ endpoint (gets a 400 response code per the Splunk logging. My Sandbox app has this added to the redirect URI's list, which I believe is good: "http://localhost:3001/api/bluebutton/callback/" Below are the docker-compose logs: |
|
@bfausett77 Where did you get the logger factory class from? Also looks like it has some commented out lines |
|
@bfausett77 Looking around I noticed quite a few commented out items in different files - maybe take a clean up pass through? |
|
@bfausett77 All the changes helped! It's now working for me |
This should now be resolved as the changes I made yesterday |
I just completed this. Take a look and let e know if you have any other suggestions. |
nbragdon
left a comment
There was a problem hiding this comment.
Left some non-required things to think about in the comments. Take a look and if you want to change them 👍 , otherwise it should be fine merging this in.
These should all be cleaned up now. |
dtisza1
left a comment
There was a problem hiding this comment.
@bfausett77 I just tested and not having that callback URI placement issue anymore. It's working as expected.
This is looking good to me, except that .pyc files should be removed from this repo.
While looking through the files, I put this list and command line together that will remove them below:
git rm server/src/__pycache__/__init__.cpython-39.pyc server/src/app/__pycache__/__init__.cpython-39.pyc server/src/configs/__pycache__/__init__.cpython-39.pyc server/src/configs/__pycache__/config.cpython-39.pyc server/src/data/__pycache__/Database.cpython-39.pyc
server/src/data/__pycache__/User.cpython-39.pyc server/src/data/__pycache__/__init__.cpython-39.pyc server/src/entities/__pycache__/AuthorizationToken.cpython-39.pyc server/src/entities/__pycache__/Settings.cpython-39.pyc server/src/entities/__pycache__/__init__.cpython-39.pyc server/src/prestart/__pycache__/__init__.cpython-39.pyc server/src/prestart/__pycache__/setenv.cpython-39.pyc server/src/shared/__pycache__/LoggerFactory.cpython-39.pyc server/src/shared/__pycache__/__init__.cpython-39.pyc server/src/utils/__pycache__/__init__.cpython-39.pyc server/src/utils/__pycache__/bb2Util.cpython-39.pyc server/src/utils/__pycache__/configUtil.cpython-39.pyc server/src/utils/__pycache__/generatePKCE.cpython-39.pyc server/src/utils/__pycache__/userUtil.cpython-39.pyc
# Then commit and push up changes.
dtisza1
left a comment
There was a problem hiding this comment.
@bfausett77 This looks good to me! Great job on this!
This is more of a PR to review the entire 'Server' side of this application. To get this to run follow the README.
Let me know if you have questions, issues, suggestions.