New answers tagged django
Solved edited /var/lib/pgsql/9.3/data/postgresql.conf unix_socket_directories = '/tmp,/var/pgsql_sock' mkdir /var/pgsql_sock/ chown postgres:postgres /var/pgsql_sock edited setting.py in my django app .....HOST='/var/pgsql_sock' Now works fine with httpd.service thanks @MichaelHampton @TimBrigham
I'm mostly a fan of using local TCP connections as Michael Hampton pointed out, however you can manually specify another directory and / or symbolically link to another location that'll work around this issue. For example: mkdir /var/pgsql_socket/ ln -s /tmp/.s.PGSQL.5432 /var/pgsql_socket/ And point Apache at /var/pgsql_socket
You cannot use /tmp to store sockets for interprocess communication in this scenario, because Apache uses private /tmp directories, a security feature that ensures that a process can only see its own /tmp directory; it cannot see what other processes write into /tmp because those other processes are actually writing into different directories. This means ...
I suspect it's because the A record in DNS for www.media-rewards.com doesn't point to 220.127.116.11, but rather 18.104.22.168. # dig www.media-rewards.com ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> www.media-rewards.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: ...
A good way to analyze the error would be making a copy of settings.py calling it "settings_test.py" for example. Then, set this copy to DEBUG=True and from a shell run - you can use some other port different than 80 or 443: python manage.py runserver 0.0.0.0:5678 --settings relative.path.to.settings_test or: python django-admin.py runserver 0.0.0.0:5678 ...
I would check the configuration of the virtualhost in /etc/nginx/sites-available and the corresponding symlink in /etc/nginx/sites-enabled. Also check out the configuration of /bin/gunicorn-start and make sure the parameters match your setup. There is more comprehensive information about configuring django with nginx and gunicorn following this link.
So Google thinks you are sending enough mail to qualify as a bulk sender. So you need to setup a SPF record at least for the domain you are sending from and preferably also a DKIM record in DNS. Those pretty much allow Google to query your DNS zone file for the domain and ask.. is this sender valid to send email from this domain.
You can use my plugin for dokku (https://github.com/sibeliusseraphini/dokku-custom-procfile-plugin) you just need to set a PROCFILE="web: npm start" env var using dokku config:set $APP (or heroku config:set $APP PROCFILE="...")
Top 50 recent answers are included