Conversation
It was not the case until you came ;), the reason I was not merging to often is that I can then quickly update the app online and because I had no pressure since I was alone on the repo :P |
| @@ -2,13 +2,11 @@ | |||
| # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER | |||
There was a problem hiding this comment.
I will rebase your PR on change/improve-user-account-flow and remove this commit, the .po file has some items that must be handled manually (because some content is stored into variables I have to add this "manually" at the end of the file). My plan to deal with translation is to focus on it at once in a dedicated PR. It is good to add the translate tags in the html though, just no need to update the .po and .mon files
There was a problem hiding this comment.
OK, thanks for the info, I will not touch any po/mo files from now on.
| pip install black==19.3b pytest | ||
| pip install click==8.0.2 | ||
| pip install -r app/requirements/mysql.txt | ||
| pip install -r app/requirements/postgres.txt |
There was a problem hiding this comment.
I had done this with mysql because for testing purposes I could not find a way to generate automatically the postgres DB, whereas it was easy with mysql
There was a problem hiding this comment.
Yes, but with #183 this fails now, because dependencies are not met. Do you need help to fix this? Shall I look into this or do you want to fix it?
There was a problem hiding this comment.
Side note, I think because of #194 sqlite is used anyways.
app/epa/settings.py
Outdated
| CRISPY_TEMPLATE_PACK = "bootstrap4" | ||
|
|
||
| EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" | ||
| EMAIL_BACKEND = "django.core.mail.backends.console.EmailBackend" |
There was a problem hiding this comment.
We should use console only when debug is set to True (the credentials I used for stmp are obviously not stored in the github repo)
There was a problem hiding this comment.
Yes, your are right, I will set this PR to draft, fix this and then remove draft mode again and order an re-review.
I think it is a good idea, I will talk to him as I have to meet him soon anyway :) Thanks for the suggestion! |
|
@4lm - could you explain how I can test the features locally? How do I see the email confirmation link? |
Yes, thanks for the clarification. All good :D |
It will pop up in your console instead of being send to your inbox. This way you can also quickly invent some email addresses and test some workflows. Example log: |
…or email verification process
80f8b74 to
550941a
Compare
|
@4lm - I have rebased this PR now. For the email sending, in production I have been using (it was there already) |
Bachibouzouk
left a comment
There was a problem hiding this comment.
Thanks a lot for this feature @4lm !
Ok, I will have a look! |
Hi @Bachibouzouk,
Please review this PR and merge it if you approve.
This PR is based on the code of the open PRs #183 and #186. Those should be merged first. Also, the failing tests should be addressed. @Bachibouzouk can you address those tests before merging? It looks like they result from your code changes in #183.
I'm a friend of merging (if possible daily), even if something still needs to be finished. If we work in a team, merging branches that sit on a shell for too long often becomes very difficult.
Please speak up; if this process of merging your and my stuff often is not an option, then we have to find a different modus operandi.
Please also note:
/users/loginand/users/user_info) could be visually improved. Maybe a job for @bmlancien. I can write an issue and invite @bmlancien to work on it. What do you think?