I have worked with XAMPP, WAMPP, MAMPP, etc., and I'm starting to look at Django.
Most of the work we do is very CMS oriented; although we were told not to use third-party CMS (mainly due to the fact that it is difficult for the user to use other problems), I found that I can encode a very simple CMS using Cake, CodeIgniter or one of the other PHP frameworks.
And yet I am becoming more and more disappointed in how much coding I need to do to get something to start and run, and I was told that Django is a good Python framework to use. It looks like it also gets a lot of noise from reddit.
I have some problems and questions about migrating from XAMPP to Django.
1) Security
Any web application must be defense-encoded. Over the past few years, we have seen a movement to protect against XSS, SQL injection, fakes on cross sites, session fixation, hi-jacking session, hi-jacking cookie; The amount of security required can be overwhelming.
What does Django do to prevent / limit XSS, SQL injections, Javascript injections and sanitizing input; commonly associated with securing PHP web applications? I need to worry something, or Django does it all out of the box.
2) What is included in the / www / public folder?
In the manual, I read that he said that do not put the manage.py file or another .py file in the main webroot, so this means that I put everything outside the web root; so what's going on there?
Am I putting the / templates / directory inside webroot? How does the server know what to start?
3) .htaccess Django? Apache , .htaccess?
4) Cronjobs
cronjobs Python/Django?
5) perl/
PHP , curl, ffmpeg, ImageMagik, ; Python/Django?
6)
Django ; ? .
7) , Facebook, Twitter, OpenID, captcha ..
PHP , DisQuss, Facebook, Twitter; ?
8) , SSL
, Django? CMS/Blog, . , , Protx/Paypal Worldpay.
; Protx, Paypal, Worldpay .. PHP - Django?
9) ?
Django XAMPP? , ?
.