Saturday, November 30, 2019

Re: no such table: main.auth_user__old

Hi,
plz use python 3.7.

On Sun, Dec 1, 2019, 01:53 Chetan Rokade <rokade.chetan12@gmail.com> wrote:
Hi Friends
Getting below error while adding new user  from admin page. I am using python 3.8 with django 2.1 version
Exception Value:
no such table: main.auth_user__old   


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9b9e2d7b-89bd-41c5-bd0f-ce8a865570fb%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWq_FDrUW8aKDKKV03WQNEAOB3U2x9k5-wbF9kKxO32oWg%40mail.gmail.com.

Re: How can I host my application in web hosting?

Deb,

Digital Ocean will allow you to run what you can install.  If you can get it on the server, you can use it.

Heroku and Python Anywhere do have specific services that are available.  You can check out their documentation to see what they are.

I don't know much about AWS, so that I will not be able to answer.

Hope it helps!

-Jorge

On Sat, Nov 30, 2019 at 6:01 AM Debabrata Chakraborty <debobroto.c.in@gmail.com> wrote:
Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a6ccc082-ae9d-4f67-8038-9db16008b956%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANfN%3DK9JwU8_NbuTUwhuO7YB_WiUKthkNNSwhO0OPE49pgd8tA%40mail.gmail.com.

RE: Question

No problem))

 

 

Sent from Mail for Windows 10

 

From: kennedy musyoki
Sent: Saturday, November 30, 2019 10:15 PM
To: django-users@googlegroups.com
Subject: Re: Question

 

Thanks, it has worked.

 

 

On Wed, Nov 27, 2019 at 8:36 AM Allaberdi Yazhanow <allaberdi16yazhanow@gmail.com> wrote:

If you want to run django Server you have to write command like this ( cd "location file manage.py " then ( python manage.py runsever 

Sent from my iPhone


On Nov 26, 2019, at 4:52 PM, kennedy musyoki <kennedymusyoki8@gmail.com> wrote:

I am new in Django and programming as well, I am to run the following code in cd but getting the error below, please advise

 

C:\Users\Kennedy>py Mysite.py runserver

C:\Users\Kennedy\AppData\Local\Programs\Python\Python38\python.exe: can't open file 'Mysite.py': [Errno 2] No such file or directory

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/540c87a7-3dca-48b8-86f1-bfaac650e3d2%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/45BE71BF-9038-4C10-9B92-DCED37B05221%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANTE21SP9UAap_umECf09tW0D-eu7cUhok8XFm-uHgUKY3ZiVg%40mail.gmail.com.

 

Re: Question

Thanks, it has worked.


On Wed, Nov 27, 2019 at 8:36 AM Allaberdi Yazhanow <allaberdi16yazhanow@gmail.com> wrote:
If you want to run django Server you have to write command like this ( cd "location file manage.py " then ( python manage.py runsever 

Sent from my iPhone

On Nov 26, 2019, at 4:52 PM, kennedy musyoki <kennedymusyoki8@gmail.com> wrote:

I am new in Django and programming as well, I am to run the following code in cd but getting the error below, please advise

C:\Users\Kennedy>py Mysite.py runserver
C:\Users\Kennedy\AppData\Local\Programs\Python\Python38\python.exe: can't open file 'Mysite.py': [Errno 2] No such file or directory

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/540c87a7-3dca-48b8-86f1-bfaac650e3d2%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/45BE71BF-9038-4C10-9B92-DCED37B05221%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANTE21SP9UAap_umECf09tW0D-eu7cUhok8XFm-uHgUKY3ZiVg%40mail.gmail.com.

Re: django.db.utils.ProgrammingError: relation "django_content_type" already exists

Hi Integr,

Thank you for your email.

Your mean these steps have to be run again?

4. 'loaddata'command in virtualenv to load the data to Postgress.
5. ~/vkproject/manage.py makemigrations
6. ~/vkproject/manage.py migrate

~Ram

On Sat, Nov 30, 2019 at 11:28 AM Integr@te System <datacentralize@gmail.com> wrote:
Hi issuer,

You do step 4 and step 5 with the same goal!?

On Sun, Dec 1, 2019, 00:03 Ram <ram.mullapudi@gmail.com> wrote:
 Hi,

I'm blocked with this issue in my newly hosting site. Here is my scenario.

  1. I've working site with MySQL database in our development localhost.
  2. I created new hosting server in Digital Ocean's Ubuntu 18.04 droplet with Postgres db.
  3. I tested the server with empty database and empty Django site when I build this hosting server.
  4. I manually migrated MySQL database to Postgres using pgAdmin tool and ran 'loaddata'command in virtualenv to load the data to Postgress.
  5. Now when I ran the following commands I see the same issue as reported here.

  6. (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py makemigrations
    No changes detected
    (vkenv) shami@ubuntu-wed-01~$ ~/vkproject/manage.py migrate
    Operations to perform:
      Apply all migrations: admin, auth, contenttypes, pages, sessions
    Running migrations:
      Applying contenttypes.0001_initial...Traceback (most recent call last):
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
        return self.cursor.execute(sql)
    psycopg2.errors.DuplicateTable: relation "django_content_type" already exists

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/home/shami/vkproject/manage.py", line 21, in <module>
        main()
      File "/home/shami/vkproject/manage.py", line 17, in main
        execute_from_command_line(sys.argv)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
        utility.execute()
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
        self.fetch_command(subcommand).run_from_argv(self.argv)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
        self.execute(*args, **cmd_options)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
        output = self.handle(*args, **options)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
        res = handle_func(*args, **kwargs)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
        fake_initial=fake_initial,
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
        state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
        state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
        state = migration.apply(state, schema_editor)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
        operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/operations/models.py", line 92, in database_forwards
        schema_editor.create_model(model)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 307, in create_model
        self.execute(sql, params or None)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 137, in execute
        cursor.execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 99, in execute
        return super().execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 67, in execute
        return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
        return executor(sql, params, many, context)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
        return self.cursor.execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
        raise dj_exc_value.with_traceback(traceback) from exc_value
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
        return self.cursor.execute(sql)
    django.db.utils.ProgrammingError: relation "django_content_type" already exists

  7.     (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py showmigrations      admin       [ ] 0001_initial       [ ] 0002_logentry_remove_auto_add       [ ] 0003_logentry_add_action_flag_choices      auth       [ ] 0001_initial       [ ] 0002_alter_permission_name_max_length       [ ] 0003_alter_user_email_max_length       [ ] 0004_alter_user_username_opts       [ ] 0005_alter_user_last_login_null       [ ] 0006_require_contenttypes_0002       [ ] 0007_alter_validators_add_error_messages       [ ] 0008_alter_user_username_max_length       [ ] 0009_alter_user_last_name_max_length       [ ] 0010_alter_group_name_max_length       [ ] 0011_update_proxy_permissions      contenttypes       [ ] 0001_initial       [ ] 0002_remove_content_type_name      pages       [ ] 0001_initial       [ ] 0002_auto_20190504_1638       [ ] 0003_auto_20190504_1645       [ ] 0004_auto_20190504_1651       [ ] 0005_auto_20190506_1451       [ ] 0006_auto_20190506_1558       [ ] 0007_auto_20190506_1803       [ ] 0008_auto_20190508_1455       [ ] 0009_auto_20190508_1554       [ ] 0010_rim_banners       [ ] 0011_rim_banners_link_id       [ ] 0012_auto_20190520_1137       [ ] 0013_auto_20190520_1144       [ ] 0014_rim_transactions_cj       [ ] 0015_auto_20190617_1756       [ ] 0016_auto_20190619_1433       [ ] 0017_rim_cj_feed      sessions       [ ] 0001_initial      (vkenv) shami@ubuntu-wed-01:~$ 
                  (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py --version      2.2.7

I appreciate if someone can provide a clue here.

Thanks in advance,

~Ram

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BOi5F2GuoQAaiDY_cWzemddpKhrjwWixJMmdyrDRJoT98zs_w%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWqak322yfhhmbFapEZ9VWH-NBTGLyTqq4KS2oQf%2BFHqjA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BOi5F2qDKBZUbXBh5qrPe%2BQ1vwWCVuXbE_JAxhN6%3DKePBdbvg%40mail.gmail.com.

Re: django.db.utils.ProgrammingError: relation "django_content_type" already exists

Hi issuer,

You do step 4 and step 5 with the same goal!?

On Sun, Dec 1, 2019, 00:03 Ram <ram.mullapudi@gmail.com> wrote:
 Hi,

I'm blocked with this issue in my newly hosting site. Here is my scenario.

  1. I've working site with MySQL database in our development localhost.
  2. I created new hosting server in Digital Ocean's Ubuntu 18.04 droplet with Postgres db.
  3. I tested the server with empty database and empty Django site when I build this hosting server.
  4. I manually migrated MySQL database to Postgres using pgAdmin tool and ran 'loaddata'command in virtualenv to load the data to Postgress.
  5. Now when I ran the following commands I see the same issue as reported here.

  6. (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py makemigrations
    No changes detected
    (vkenv) shami@ubuntu-wed-01~$ ~/vkproject/manage.py migrate
    Operations to perform:
      Apply all migrations: admin, auth, contenttypes, pages, sessions
    Running migrations:
      Applying contenttypes.0001_initial...Traceback (most recent call last):
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
        return self.cursor.execute(sql)
    psycopg2.errors.DuplicateTable: relation "django_content_type" already exists

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/home/shami/vkproject/manage.py", line 21, in <module>
        main()
      File "/home/shami/vkproject/manage.py", line 17, in main
        execute_from_command_line(sys.argv)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
        utility.execute()
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
        self.fetch_command(subcommand).run_from_argv(self.argv)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
        self.execute(*args, **cmd_options)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
        output = self.handle(*args, **options)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
        res = handle_func(*args, **kwargs)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
        fake_initial=fake_initial,
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
        state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
        state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
        state = migration.apply(state, schema_editor)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
        operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/operations/models.py", line 92, in database_forwards
        schema_editor.create_model(model)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 307, in create_model
        self.execute(sql, params or None)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 137, in execute
        cursor.execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 99, in execute
        return super().execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 67, in execute
        return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
        return executor(sql, params, many, context)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
        return self.cursor.execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
        raise dj_exc_value.with_traceback(traceback) from exc_value
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
        return self.cursor.execute(sql)
    django.db.utils.ProgrammingError: relation "django_content_type" already exists

  7.     (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py showmigrations      admin       [ ] 0001_initial       [ ] 0002_logentry_remove_auto_add       [ ] 0003_logentry_add_action_flag_choices      auth       [ ] 0001_initial       [ ] 0002_alter_permission_name_max_length       [ ] 0003_alter_user_email_max_length       [ ] 0004_alter_user_username_opts       [ ] 0005_alter_user_last_login_null       [ ] 0006_require_contenttypes_0002       [ ] 0007_alter_validators_add_error_messages       [ ] 0008_alter_user_username_max_length       [ ] 0009_alter_user_last_name_max_length       [ ] 0010_alter_group_name_max_length       [ ] 0011_update_proxy_permissions      contenttypes       [ ] 0001_initial       [ ] 0002_remove_content_type_name      pages       [ ] 0001_initial       [ ] 0002_auto_20190504_1638       [ ] 0003_auto_20190504_1645       [ ] 0004_auto_20190504_1651       [ ] 0005_auto_20190506_1451       [ ] 0006_auto_20190506_1558       [ ] 0007_auto_20190506_1803       [ ] 0008_auto_20190508_1455       [ ] 0009_auto_20190508_1554       [ ] 0010_rim_banners       [ ] 0011_rim_banners_link_id       [ ] 0012_auto_20190520_1137       [ ] 0013_auto_20190520_1144       [ ] 0014_rim_transactions_cj       [ ] 0015_auto_20190617_1756       [ ] 0016_auto_20190619_1433       [ ] 0017_rim_cj_feed      sessions       [ ] 0001_initial      (vkenv) shami@ubuntu-wed-01:~$ 
                  (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py --version      2.2.7

I appreciate if someone can provide a clue here.

Thanks in advance,

~Ram

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BOi5F2GuoQAaiDY_cWzemddpKhrjwWixJMmdyrDRJoT98zs_w%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWqak322yfhhmbFapEZ9VWH-NBTGLyTqq4KS2oQf%2BFHqjA%40mail.gmail.com.

no such table: main.auth_user__old

Hi Friends
Getting below error while adding new user  from admin page. I am using python 3.8 with django 2.1 version
Exception Value:
no such table: main.auth_user__old   


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9b9e2d7b-89bd-41c5-bd0f-ce8a865570fb%40googlegroups.com.

django.db.utils.ProgrammingError: relation "django_content_type" already exists

 Hi,

I'm blocked with this issue in my newly hosting site. Here is my scenario.

  1. I've working site with MySQL database in our development localhost.
  2. I created new hosting server in Digital Ocean's Ubuntu 18.04 droplet with Postgres db.
  3. I tested the server with empty database and empty Django site when I build this hosting server.
  4. I manually migrated MySQL database to Postgres using pgAdmin tool and ran 'loaddata'command in virtualenv to load the data to Postgress.
  5. Now when I ran the following commands I see the same issue as reported here.

  6. (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py makemigrations
    No changes detected
    (vkenv) shami@ubuntu-wed-01~$ ~/vkproject/manage.py migrate
    Operations to perform:
      Apply all migrations: admin, auth, contenttypes, pages, sessions
    Running migrations:
      Applying contenttypes.0001_initial...Traceback (most recent call last):
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
        return self.cursor.execute(sql)
    psycopg2.errors.DuplicateTable: relation "django_content_type" already exists

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/home/shami/vkproject/manage.py", line 21, in <module>
        main()
      File "/home/shami/vkproject/manage.py", line 17, in main
        execute_from_command_line(sys.argv)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
        utility.execute()
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
        self.fetch_command(subcommand).run_from_argv(self.argv)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
        self.execute(*args, **cmd_options)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
        output = self.handle(*args, **options)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
        res = handle_func(*args, **kwargs)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
        fake_initial=fake_initial,
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
        state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
        state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
        state = migration.apply(state, schema_editor)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
        operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/migrations/operations/models.py", line 92, in database_forwards
        schema_editor.create_model(model)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 307, in create_model
        self.execute(sql, params or None)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 137, in execute
        cursor.execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 99, in execute
        return super().execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 67, in execute
        return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
        return executor(sql, params, many, context)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
        return self.cursor.execute(sql, params)
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
        raise dj_exc_value.with_traceback(traceback) from exc_value
      File "/home/shami/vkproject/vkenv/lib/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
        return self.cursor.execute(sql)
    django.db.utils.ProgrammingError: relation "django_content_type" already exists

  7.     (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py showmigrations      admin       [ ] 0001_initial       [ ] 0002_logentry_remove_auto_add       [ ] 0003_logentry_add_action_flag_choices      auth       [ ] 0001_initial       [ ] 0002_alter_permission_name_max_length       [ ] 0003_alter_user_email_max_length       [ ] 0004_alter_user_username_opts       [ ] 0005_alter_user_last_login_null       [ ] 0006_require_contenttypes_0002       [ ] 0007_alter_validators_add_error_messages       [ ] 0008_alter_user_username_max_length       [ ] 0009_alter_user_last_name_max_length       [ ] 0010_alter_group_name_max_length       [ ] 0011_update_proxy_permissions      contenttypes       [ ] 0001_initial       [ ] 0002_remove_content_type_name      pages       [ ] 0001_initial       [ ] 0002_auto_20190504_1638       [ ] 0003_auto_20190504_1645       [ ] 0004_auto_20190504_1651       [ ] 0005_auto_20190506_1451       [ ] 0006_auto_20190506_1558       [ ] 0007_auto_20190506_1803       [ ] 0008_auto_20190508_1455       [ ] 0009_auto_20190508_1554       [ ] 0010_rim_banners       [ ] 0011_rim_banners_link_id       [ ] 0012_auto_20190520_1137       [ ] 0013_auto_20190520_1144       [ ] 0014_rim_transactions_cj       [ ] 0015_auto_20190617_1756       [ ] 0016_auto_20190619_1433       [ ] 0017_rim_cj_feed      sessions       [ ] 0001_initial      (vkenv) shami@ubuntu-wed-01:~$ 
                  (vkenv) shami@ubuntu-wed-01:~$ ~/vkproject/manage.py --version      2.2.7

I appreciate if someone can provide a clue here.

Thanks in advance,

~Ram

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BOi5F2GuoQAaiDY_cWzemddpKhrjwWixJMmdyrDRJoT98zs_w%40mail.gmail.com.

Re: Which Cloud Service Provider should be chosen to host Django Application

Thanks a million ke1g!

That was really helpful. I am definitely going to use PostgreSQL now.

Only one question remains. I'm willing to deploy my site in any reasonably priced virtual server hosting. You mentioned using VPS means I can install what I want.

So does that mean - it doesn't matter which version of Django (i.e. Django 2.2.5) I use for the site development, they will all be equally supported inside a VPS hosting plan?

Also, what is the least complicated, least technically challenging Django hosting option for a beginner like me?

Thanks again

Deb


On Saturday, November 30, 2019 at 8:01:15 PM UTC+5:30, ke1g wrote:

SQLite is fine for development, but, unless things have changed, it is single threaded, and unsuitable for a production environment.  Most folks seem to go for MySQL, though the fork MariaDB is usually preferred no that Oracle owns MySQL.  I prefer PostgreSQL (or just Postgres) because I think that it comes closest to the SQL standard and is competitive in other respects.  Any of these have to be "administered" (though is many cases the provider helps with this), so if this is for a toy installation, SQLite may be OK.

SQLite, however, is built into Python these days, and even in older Python versions it was just a pop install, so providers can't squawk about the version.  But shared hosting (as opposed to virtual server) will mean that a particular python version is installed, and the SQLite version in that version of Python is what you are going to get.  But SQLite handles queries written for older versions well, and you will wind up with a quite recent version, so you are unlikely to be using any features that are too new for the installed version.

Virtual server hosting means that you can install what you want, but does mean that you will be administering the whole OS as well as the database, the http server, and even the version of Python, installing new versions when there are security updates, etc.

I, personally, haven't used any of the providers that you mentioned.  The last time I deployed on a shared host I used WebFaction, and was quite satisfied.  Today I use Linode, who provide a virtual server, and are also quite satisfactory (though you must, last time I checked, use Linux, which I consider a plus).



On Sat, Nov 30, 2019 at 9:02 AM Debabrata Chakraborty <debobr...@gmail.com> wrote:

Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e0918e60-bdf4-4721-a931-1e030d697558%40googlegroups.com.

Re: Hosting recommendations please

Hi Deb,

Appropriate answer on service provider, bc of your requirement and their service alway mutability.

On Sat, Nov 30, 2019, 21:01 Debabrata Chakraborty <debobroto.c.in@gmail.com> wrote:
Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb



On Tuesday, April 2, 2019 at 12:39:39 PM UTC+5:30, Mike Dewhirst wrote:
I have to move three Django websites away from my current VM service
provider by the end of April because he is going out of the VM business.

One is a plain Mezzanine CMS on one VM running Nginx/Gunicorn and the
other two are on the second VM running Apache and mod_wsgi.

I'm most familiar with Ubuntu 16.04 and hope to go to 18.04.

I think the RAM requirements are around 4GB for the Apache sites and
half that for Nginx. Haven't done any profiling.

I'm in Australia. I'm after stability and reliability and if I'm lucky,
scalability.

If you have any negative comments about providers please send them off-list.

Many thanks

Mike


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/15cc566b-b17e-45f0-bc68-aba926dbe7f1%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWrGsEYGrCSVLqNv6kVRBJaEeX_4NgO5JHcRQ%2BgBnTe2AA%40mail.gmail.com.

Re: Which Cloud Service Provider should be chosen to host Django Application

SQLite is fine for development, but, unless things have changed, it is single threaded, and unsuitable for a production environment.  Most folks seem to go for MySQL, though the fork MariaDB is usually preferred no that Oracle owns MySQL.  I prefer PostgreSQL (or just Postgres) because I think that it comes closest to the SQL standard and is competitive in other respects.  Any of these have to be "administered" (though is many cases the provider helps with this), so if this is for a toy installation, SQLite may be OK.

SQLite, however, is built into Python these days, and even in older Python versions it was just a pop install, so providers can't squawk about the version.  But shared hosting (as opposed to virtual server) will mean that a particular python version is installed, and the SQLite version in that version of Python is what you are going to get.  But SQLite handles queries written for older versions well, and you will wind up with a quite recent version, so you are unlikely to be using any features that are too new for the installed version.

Virtual server hosting means that you can install what you want, but does mean that you will be administering the whole OS as well as the database, the http server, and even the version of Python, installing new versions when there are security updates, etc.

I, personally, haven't used any of the providers that you mentioned.  The last time I deployed on a shared host I used WebFaction, and was quite satisfied.  Today I use Linode, who provide a virtual server, and are also quite satisfactory (though you must, last time I checked, use Linux, which I consider a plus).

On Sat, Nov 30, 2019 at 9:02 AM Debabrata Chakraborty <debobroto.c.in@gmail.com> wrote:
Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c55f1dae-8fc9-4fbe-85df-f6ee86ce9b53%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAB%2BAj0tPho%2Bs1Q9bej55TE90-HC1XcYww-BArZ8RK7n91dyrzQ%40mail.gmail.com.

Re: Update _id field before .save() for ForeignKey

Thanks, its interest to know more about pk management, but this is another case. Now I update pk for child objects and this is fastest way, what I found. If django will reread .pk before save, it will the same.

Want to know, maybe my logic can be altered from the start. How peoples create batch of objects with relations to insert it in one request? I think, this is popular task.


On Sat, Nov 30, 2019 at 6:27 PM Integr@te System <datacentralize@gmail.com> wrote:
Hi ,

Please lookandfeel on 

Moving an object from one database to another



On Sat, Nov 30, 2019, 15:39 Dvenum <dvenum.at@gmail.com> wrote:
Integr@te System,

This is True: id(company) == id(company_value.company)
So, we have exact the same object company, .id is ready on .save() call, but internal meta dictionary still has None, because it was none when company_value created.

On Sat, Nov 30, 2019 at 2:39 PM Integr@te System <datacentralize@gmail.com> wrote:
Hi Dvenun,

Bc of  Django implement accord to python, of cause child inherit from parent existence.




On Sat, Nov 30, 2019, 13:30 Dvenum <dvenum.at@gmail.com> wrote:
Interest idea and it works, but not necessary:
    company = Company()
    #company.id is None
    companies.append(company)
    Company.objects.bulk_create(companies)
    #company.id is 1

Instead to ask pk from database, it can be used from company_value.company.id. Django save pk value to internal meta (models/base.py) and does not update it. This works too:
value.company = value.company     # pk updated

I want to ask, each child object should be created only when parent is saved to db? Maybe django has something to cover this case?


On Sat, Nov 30, 2019 at 7:52 AM Charles Lee <CharlesLee522@gmail.com> wrote:
I have an idea.
  1. `bulk_create` all companies.
  2. `Filter`(SELECT) all `Company` and make it dictionary for retrieving company fast.
    1. company_dict = {
        'Name': 'pk',
        ...
      }
  3. Create a list of `CompanyValue` with company name and company_dict.
  4. `bulk_create` the list.

I'm not sure if it will work because I haven't implemented it, but I hope it helps. 

2019년 11월 29일 금요일 오후 9시 42분 0초 UTC+9, Maxim Bulatov 님의 말:
Hello,

I have lot of lists like follow:
(Name1): (V1, V2, V3, V4, ..)

And I use many threads to create many db objects:
company = Company(Name)
for x in vector:
    v = CompanyValue(company=company, value=x)
    values.append(v)

class CompanyValue(models.Model):
    company = models.ForeignKey('Company', on_delete=models.CASCADE)
    value = FloatField

This pool of threads return all lists, what I combine, filter and want put to database in one bulk_create call.
Suddenly, I found, company.id is not ready to be linked in CompanyValue, follow code does not works:
Company.objects.bulk_create(companies)
CompanyValue.objects.bulk_create(values)      # value.company_id is null here

No way to save objects in my threads, because I need to filter objects and can do it only when all of them are collected. Also, it has performance issues 100k+ of requests is slowly enough. I have two ways to resolve:
1. I can make intermediate class or tuple and create CompanyValue objects only when companies is saved to db. Hard to support, hard to filter, not so clean.
2. I can use dirty hack to update _id field:
    for v in values:
        v.company = v.company

Can you advice more ways for me? It seems, I don't know something from django features to make it elegant.
I see 11 years old issue here (https://code.djangoproject.com/ticket/9553) and it marked as intended behaviour.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/af2a0f27-7234-4210-8627-1ad8982da805%40googlegroups.com.


--

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHBRYSd1MC5mL3oWTfzqc%2BXXcWxVnDqLpJ5HsEGk2GHFd917eQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWqW7gZVR1u6-%2BAkMhB5dZeRHiXzLrSQvmiL7O3diT9OfA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHBRYSf9iMaMmT1osqvP2uiu%2BbyN%2BKDkMOqZXdYcfo8Pt%2B1_Sw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWq01D-mbPRA-mV_vfn-a7jKj52n-ayk_mH7_SmWn9GD2A%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHBRYSf4FG4a4CS93%2BfQb6cJi17hiQq7VVvjTjEUuyeVgEso-w%40mail.gmail.com.

Re: How can I host my application in web hosting?

Thanks a bunch Jorge,

That was very helpful.

Best

Deb

On Sun, Dec 1, 2019 at 11:31 AM Jorge Gimeno <jlgimeno71@gmail.com> wrote:
Deb,

Digital Ocean will allow you to run what you can install.  If you can get it on the server, you can use it.

Heroku and Python Anywhere do have specific services that are available.  You can check out their documentation to see what they are.

I don't know much about AWS, so that I will not be able to answer.

Hope it helps!

-Jorge

On Sat, Nov 30, 2019 at 6:01 AM Debabrata Chakraborty <debobroto.c.in@gmail.com> wrote:
Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a6ccc082-ae9d-4f67-8038-9db16008b956%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANfN%3DK9JwU8_NbuTUwhuO7YB_WiUKthkNNSwhO0OPE49pgd8tA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAPDzUOhBsOxyyTDAZdbLXNU1WgfBDfT_o9V7WMitB%3DQsYyuCKQ%40mail.gmail.com.

Re: raise ValueError("Missing staticfiles manifest entry for '%s'" % clean_name)

Hi man,

Check on staticfile.json to see manifest at runtime, to disable error on section storage.ManifestStaticFilesStorage.manifest_strict


On Sat, Nov 30, 2019, 17:14 Kevin Dublin <kevdublin@gmail.com> wrote:
Hi Django Users,

It looks like from Stack Overflowing searching this is an error that people come across deploying to heroku and because I'm fairly new to Django, I think it might be something simple that I'm missing:



This is from my heroku logs. I currently have collectstatic disabled and debug collectstatic on. When I set Debug = True in my settings.py, it will load just fine but exposes variables and such when there are errors or something fails. Does anyone know why this is happening or have encountered it before? I really want to send my web app out to beta test next week.

I get this:

raise ValueError("Missing staticfiles manifest entry for '%s'" % clean_name)
ValueError: Missing staticfiles manifest entry for 'icons/favicon.ico'

I'm using whitenoise for static files and my relevant static settings are:

STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles')
STATIC_URL = "/static/"

STATICFILES_DIRS = (
    os.path.join(BASE_DIR, '../apps/core/static'),
)

STATICFILES_STORAGE = 'whitenoise.storage.CompressedStaticFilesStorage'

Any help would be greatly appreciated! I've tried a number of things over the week from changing static settings to almost everything suggested on Stackoverflow. I learned to stop worrying and just get back to developing, but now I'm worrying again.

Hope you all had a great week!

Cheers,

Kevin Dublin
Etched Press Editor
Follow me @parteverything

Happiness is a state of being, just be.
Believe it, and it will be.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANips4%2BJNTM97huCyBskWv0JxbtqtLP6FUdb0CYq8FhDjAMpWw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP5HUWphFxJfAda7n%3DUcQyL-eHCR3KcQcxXnqMFHX7wcc3xrPw%40mail.gmail.com.

Re: How can I host my application in web hosting?

Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a6ccc082-ae9d-4f67-8038-9db16008b956%40googlegroups.com.

Re: Which Cloud Service Provider should be chosen to host Django Application

Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c55f1dae-8fc9-4fbe-85df-f6ee86ce9b53%40googlegroups.com.

Re: Hosting recommendations please

Hi everyone,

I'm a beginner Django developer. So my apologies in advance for newbie like questions.

I am building my site with " Django version 2.2.5 " and " SQLite 3.30 " in back-end. My question is -

# Do services like "Heroku", "Digital Ocean", "Python Anywhere" and "AWS" - have limitation on which version of Django  or which DBMS I can use?

I've seen this before with PHP/MySQL hosting where some hosting companies will limit which version of PHP or MySQL one can use. Is the same applicable to Django hosting in the above mentioned hosting platforms as well?

I will very much grateful if you can help me out with this confusion.

Best

Deb



On Tuesday, April 2, 2019 at 12:39:39 PM UTC+5:30, Mike Dewhirst wrote:
I have to move three Django websites away from my current VM service
provider by the end of April because he is going out of the VM business.

One is a plain Mezzanine CMS on one VM running Nginx/Gunicorn and the
other two are on the second VM running Apache and mod_wsgi.

I'm most familiar with Ubuntu 16.04 and hope to go to 18.04.

I think the RAM requirements are around 4GB for the Apache sites and
half that for Nginx. Haven't done any profiling.

I'm in Australia. I'm after stability and reliability and if I'm lucky,
scalability.

If you have any negative comments about providers please send them off-list.

Many thanks

Mike


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/15cc566b-b17e-45f0-bc68-aba926dbe7f1%40googlegroups.com.