>
> But the following is still saying, “Forbidden”:
>
>
> https://www.angeles4four.info/static/admin/
>
This is normal. The reason is not the filesystem permissions, but that Apache is
configured to not list files inside that directory (to change that you'd need to
use "Options Indexes" somewhere,
The username on my droplet is ‘tranq’ but there is a line in both my vhost
config files which reads:
So I swapped out ‘user’ for ‘tranq’. That line now reads:
Now some of my static files are accessible. For example you can see here:
You’re right, @Antonis, that I don’t want my Django source code exposed. No
sysadmin would. I have since moved my Django project folder to my home
user’s directory. However (out of curiosity), if I continued to house
Django in my public_html folder (which I am not any more, but say if i did)
Hi
If you use ssl on apache, the ssl terminate only on apache request from
client, then the wsgi from apache is no https.
So ssl handled by your webserver service, whether the webserver you use is
apache or nginx.
Try access the static file with https is it working?
On 21 Jan 2018 4:26 pm,
Hello,
I'm not certain I understand what you are describing. Is Apache listening on
port 8000? How is it possible that you are using "runserver" when you are
running Django through mod_wsgi? Something is wrong there.
Also, don't put your Django app's files in public_html or any other directory
I’ve played with a little Django (v2.0.1) locally. Now I am trying to
implement a test case on my production Apache web server. I’m running an
Ubuntu 14.04 DigitalOcean droplet (will upgrade to 18.04 later this year).
I got Django running.
Here it is: http://www.angeles4four.info:8000/
Before
6 matches
Mail list logo
