Re: Compatibility List

P.S. > > Effectively 2.2 is as far as you need to go for the time being because it is > an LTS release. Might make a convenient initial goal. Should be pain-free. > Unfortunately that’s not an option. -- You received this message because you are subscribed to the Google Groups "Django users"

Re: Compatibility List

Thanks for your response, Mike. I was using “changelog” and “release notes” interchangeably; sorry for the confusion. My question is more about packages that extend Django’s capabilities (i.e. django_csp, django_rq, etc.) as opposed to Django itself. Thankfully Django has great release notes, s

Re: Compatibility List

On 31/12/2020 2:16 pm, Benny M wrote: Hi all, I have a project that’s doing a rather sizable jump from 1.11.29 to 3.1. I’m aware of the internal gotchas (enforced on_delete, settings syntax, etc) - but I was curious if anyone knows of a package compatibility list exists? Something like caniuse

Compatibility List

Hi all, I have a project that’s doing a rather sizable jump from 1.11.29 to 3.1. I’m aware of the internal gotchas (enforced on_delete, settings syntax, etc) - but I was curious if anyone knows of a package compatibility list exists? Something like caniuse but for django-focused packages. Right n

Re: New Django Contract/Job Board

Hello Job, I'm interested in helping to maintain the site, thank you . On Tue, Dec 29, 2020, 21:01 Jacob Hyde wrote: > Hi everyone. > > I recently created a Django contract / job board ( > https://djangocontracts.com). It works very similar to larajobs, but is > for Django. You can create a FRE

Re: attempt to write a readonly database

It's a permissions error on the file. For those running Linux change to the directory and type *ls -l *.sqllite* so we can see who the owner and group are on the file. If you are running nginx it should be the same user as nginx is configured to run as (www-data) by default. If the owner (or

Re: Configuration Django with uwsgi + NGINX

Thank you very much Carlos On Wed, Dec 30, 2020 at 4:35 AM carlos wrote: > > https://www.digitalocean.com/community/tutorials/how-to-serve-django-applications-with-uwsgi-and-nginx-on-ubuntu-16-04 > > On Tue, Dec 29, 2020 at 4:57 AM Django-Learner_27 < > reachme.ven...@gmail.com> wrote: > >> >> H

Re: attempt to write a readonly database

I got the same error when I deployed my Django web app over Nginx server and tried to access Django admin. If anyone knows the solution please revert back. regards, govind On Wed, 30 Dec 2020 at 20:45, RANGA BHARATH JINKA wrote: > hi, > > Try running as the root user using sudo permissions. >

Django MQTT Broker

Hi guys, How r u all? Hope doing ok. Im working a iot project and I want to develp a panell of control with django. ¿Whats is the best or possible way to connect django to mqtt broker? Thanks in advance, Regards, -- You received this message because you are subscribed to the Google Groups

Re: Error After Heroku Deployment

Yes . I got the solution. Thanks On Wed, Dec 30, 2020, 8:43 PM RANGA BHARATH JINKA wrote: > Hi, > > Run > heroku run python manage.py makemigrations > heroku run python manage.py migrate > > All the best > > On Wed, Dec 30, 2020 at 8:18 PM Sumit Pande <2018bit...@sggs.ac.in> wrote: > >> Program

Re: attempt to write a readonly database

hi, Try running as the root user using sudo permissions. All the best On Wed, Dec 30, 2020 at 8:18 PM Steven Mapes wrote: > This normally means that the user you are running your project as does not > have access to the SQLLite database file. I can see that you are running on > windows so fine

Re: Error After Heroku Deployment

Hi, Run heroku run python manage.py makemigrations heroku run python manage.py migrate All the best On Wed, Dec 30, 2020 at 8:18 PM Sumit Pande <2018bit...@sggs.ac.in> wrote: > ProgrammingError at /accounts/login/ > relation "django_site" does not exist > LINE 1: ..."django_site"."domain", "dj

Re: attempt to write a readonly database

This normally means that the user you are running your project as does not have access to the SQLLite database file. I can see that you are running on windows so fine the database in the file system and check and change the owner as well as ensuring that the owner/group has read/write access to

Re: 127.0.0.1:8000 refused to connect

On 30/12/2020 08.44, Parul. wrote: I am not able to connect to localhost. i have put Allowed_hosts=['*'] still i am getting this error i am using command: python manage.py runserver python manage.py runserver 0.0.0.0:8000   python manage.py runserver 127.0.0.1:8000