3 ms·
Nice writeup. Thankfully doesn't have a clear bias like most of these type of comparisons! A powerful Django feature (the admin) is rebutted by citing plugins i
by c4urself 15y ago
Nice writeup. Thankfully doesn't have a clear bias like most of these type of comparisons! A powerful Django feature (the admin) is rebutted by citing plugins in Ruby; I think that the fact that it's part of Django really makes a difference, with the smallest Django test project you can enable the '/admin/' and use the models. Either way I agree with the conclusion: for webapps you really can't go wrong with either
- sabat 15y agoThe difference is philosophy. The RoR guys think of things like built-in admin interfaces as appropriate for plugins because not every app needs such a thing. As a guy who happens to have a security background, I'd discourage admin interfaces built into the same app as the user app, especially when it's named /admin. Keep your admin functions in a separate and locked-down app if at all possible.
- jonknee 15y agoAt least for Django, there's no reason your built-in admin has to be on the same site (or /admin). You can just create a new project, add the same apps of your main in addition to the admin app and hook it up to the URL of your choice along with whatever authentication you want (even limit to internal IPs).
- robbles 15y agoThe admin functionality IS in a separate app. The app just happens to be bundled with Django. Take a look at the folder structure for the admin code in Django (contrib/admin). It has the same structure and conventions as any user app.