fixtures working #42
fixtures working #42
Conversation
Update: I think I've found a potential solution in here: going to implement that tonight |
I've got this, can I merge? |
{{ message }}
Merged
This file contains 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
etrepum
reviewed
Aug 28, 2019
etrepum
approved these changes
Aug 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've got fixtures working, and that's all I've included in this PR. You should be able to run
docker-compose upfollowed bydocker-compose run web python3 manage.py loaddata fixtures.jsonand it'll be up and running. All the passwords for the users are "topsecret123".Comment on future PR:
This application also needs to be able to sync with the salesforce database, which I attempted to do first with django-q (which was giving an error when I tried to schedule a task that made it possible to only schedule tasks to work once -- it wasn't recognizing a parameter that is automatically passed when a task is scheduled for Daily or Hourly). I think this is a problem with Django-q, and because they don't seem to be supporting the library anymore, I decided to try to switch to Celery. This is what has taken time, as I have another issue there. In another PR (which I may create this evening) I will upload some code that outlines the issue I am having with Celery and perhaps you could fix it quickly or point me in the right direction. I believe the issue I'm having is caused by Celery trying to access the database from the same port as Docker.