USER STORY: <Registration>

[BjornRodin]

As a Site User I can register to the site so that I can book a session

Acceptance Criteria

• Acceptance Criteria 1: Can register with their name, email and password.

Tasks

• [x] Task 1
• [x] Task 2
• [x] Task 3

[BjornRodin]

I will most likely make the email mandatory because in a real life scenario that would be good to have both for the user if they need to recover their password but also for the admin/owner when they want to contact the user that has made a booking. I feel it is better to get the email from the start already because that means that when the user want to book a session they dont have to fill in information that we already have in the database.

[BjornRodin]

I will not make this email required. Might get back to it at a later stage but i like how it is at the moment.

[BjornRodin]

Realized a late error where when the user registers an account and adds an email i was getting connection issues:

ConnectionRefusedError at /accounts/signup/ [Errno 111] Connection refused

After alot of trial an error looking through the code for what might be wrong I was starting to look at all the connections for the databases aswell but no luck. When looking online i finally found a solution here: https://stackoverflow.com/questions/57405472/connectionrefusederror-at-accounts-register Where a soultion was mentioned to add these lines to the settings.py file and now it works like a charm again. EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' ACCOUNT_EMAIL_VERIFICATION = "none"