Skip to content
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

Devices should belong to users #8

Closed
jwjimmy opened this issue Mar 15, 2017 · 3 comments
Closed

Devices should belong to users #8

jwjimmy opened this issue Mar 15, 2017 · 3 comments

Comments

@jwjimmy
Copy link
Owner

jwjimmy commented Mar 15, 2017

How to extend the Device model:
https://django-fcm.readthedocs.io/en/latest/extending_device.html

This is an example of someone extending the Device model to have User as a foreign key: Chitrank-Dixit/django-fcm#29

@jwjimmy
Copy link
Owner Author

jwjimmy commented Mar 15, 2017

My current issue is that the built in serializers in django-fcm do not support my custom Device model.

@jwjimmy
Copy link
Owner Author

jwjimmy commented Mar 20, 2017

I fixed the serializer issue in my fork of django-fcm (https://github.com/jwjimmy/django-fcm), and submitted PRs for my changes. Everything is fine and dandy when I run my app locally. On Heroku it recognizes the CounselDevice extension of Device but does not register my updates to django-fcm for some reason.

I will have to investigate later.

@jwjimmy
Copy link
Owner Author

jwjimmy commented Mar 20, 2017

Yes!!!
Forcing editable mode caused the changes to register on the deployed app.
27e1106

I have no clue why this is the case... supposedly Heroku is fetching all of the code from the git repo I specify in requirements.txt either way.

But prepending -e causes it to work.

@jwjimmy jwjimmy closed this as completed Mar 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant