Automatic subdomain for each user

I am faced with a requirement where each user is required to use the application under his own subdomain. Whenever a user registers, he gets username.domain.com and he can add staff, manage reports, etc under his subdomain. What is the best approach to you can suggest please? -- You

Not sure if I am doing django-paypal correctly

Hello all, I decided to try and accept payments on my web application. I have chosen the django-paypal application to help me out with this task. I found a decent walkthrough at: how-to-accept-paypal-payments-on-your-django-application

Re: Automatic subdomain for each user

On 2021-12-29 15:02, Sherif Adigun wrote: > I am faced with a requirement where each user is required to use > the application under his own subdomain. Whenever a user registers, > he gets username.domain.com and he can add staff, manage reports, > etc under his subdomain. > > What is the best

Re: Not sure if I am doing django-paypal correctly

Hello I'm a Django Noobie and maybe I'm completely wrong about this but in my app named "core", I have a file called apps.py where I register my signals. I just followed a tutorial as well so I can't yet explain what it does but if I had to guess is just to register the app with my signals.

Re: are migrations the same regardless of database type?

Thanks to all for your replies. Using the "sqlmigrate" command, as far as I can see, there are no differences between database types. I asked this question initially because I was unable to set up postgresql locally. I have solved those issues now and will follow your advice on using the same