forked from openedx/openedx-platform
-
Notifications
You must be signed in to change notification settings - Fork 15
Skip login after registration (mostly for NYIF) #174
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
Merged
tkeemon
merged 5 commits into
appsembler/ficus/develop
from
appsembler/ficus/feature/nyif-reg-workflow
Oct 19, 2017
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
a05f9fa
try to import user-org backend and create obj at registration time
tkeemon 6b25443
bypass auto login after registration with APPSEMBLER_FEATURE flag
tkeemon 425efc5
conditionally import our custom org middleware
tkeemon 0dbd8c5
fix formatting; include exception type in try/except
tkeemon e8fd8a0
remove unnecessary try/except
tkeemon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not specific to this PR at all. But we do need to DRY in the
envs/*_appsembler.pyfiles.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. And @johnbaldwin has raised this same point as well:
https://trello.com/c/wfj1jPTd/98-dry-up-awsappsembler-and-devstackappsembler-py-files
That's what I was attempting to do with the
appsembler.pyfile. Initially, this file was supposed to be imported by bothaws_appsembler.pyanddevstack_appsembler.py, so settings could be shared across both of production and devstack deployments.But with this setup we were running into some problems. I can't remember specifically, but I think it was related to the fact that this file was called without importing
common.py, so variables likeINSTALLED_APPSdidn't yet exist. And if we definedINSTALLED_APPSinappsembler.py, then it would nuke all of the values fromcommon.pyandaws.pywhen imported intoaws_appsembler.py.We can definitely do this, we just need to be careful about how we structure the imports.