According to the Django documentation (here):
django.contrib.sites registers a post_migrate signal handler which creates a default site named example.com with the domain example.com. This site will also be created after Django creates the test database. To set the correct name and domain for your project, you can use a data migration.
Isn't it safe to directly change the default values from the Django admin panel? why?
Here is my answer. First option is to change them on Django Admin site. Second option is to create a migration file manually and run your migrations. Let me describe the second option here. Firstly, create an empty migration using following command.
$ python manage.py makemigrations --empty --name update_site_name app_name Next, refer to this blog to edit the migration file.
Finally, run your migrations.
Thank you.
Finally, I changed the site_name directly in my database. I realized that a site can have a migration to define a default site_name from scratch, but for a case like mine in which there are a lot of data it's not necessary to add a migration. In other words, you should add a migration when you are developing your site, not when it's on the production stage.
Thanks to @markwalker for his comment
You can also change the site name from the shell if you prefer working with the shell, run python manage.py shell, get the existing site object(s) and change the names.
>>> from django.contrib.sites.models import Site >>> my_site = Site.objects.get(name='example.com') >>> my_site.name = 'mysite.com' >>> my_site.domain = 'mysite.com' >>> my_site.save() or you can create a new site object having your custom name. If you're creating a new site object, make sure the SITE_ID in settings.py corresponds to its id:
>>> custom_site = Site.objects.create(name='mysite.com', domain='mysite.com') >>> custom_site.save() 