convore.json/groups/django-community/best-practice-for-admin-on-deployed-site/messages.json

[{"user_id": 13006, "stars": [], "topic_id": 43838, "date_created": 1313428880.9481411, "message": "Hi my customer is nervous about /admin being available on a deployed site even \nthough we are running under https My solution is remmove the /admin URL and do a\n separate \"admin\" site running off a different domain.\nOther suggestion including obscuring the admin the admin url e.g /mynewadmin or \nonly allowing the admin url only \nif the request comes for a designated IP.\nSo what is the django best practice as regardss /admin in production sites?\n", "group_id": 81, "id": 1877155}, {"user_id": 27916, "stars": [], "topic_id": 43838, "date_created": 1313429532.7896349, "message": "I restrict by IP in the webserver config (nginx or apache)", "group_id": 81, "id": 1877212}, {"user_id": 1126, "stars": [], "topic_id": 43838, "date_created": 1313441826.0827911, "message": "Place it at a non-standard URL and lock it down by IP (I've used a middleware in the past to handle this with the INTERNAL_IPS setting: http://djangosnippets.org/snippets/2095/ )", "group_id": 81, "id": 1878501}, {"user_id": 13006, "stars": [], "topic_id": 43838, "date_created": 1313481557.6608169, "message": "my problem is the smaller customers may have dynamic IPs", "group_id": 81, "id": 1882045}, {"user_id": 5863, "stars": [], "topic_id": 43838, "date_created": 1313918374.7532001, "message": "I've generally gone for a separate domain and access via VPN", "group_id": 81, "id": 1921632}, {"user_id": 13006, "stars": [], "topic_id": 43838, "date_created": 1314110466.5540869, "message": "i think i'm following @garethr,  and go with a separate  site", "group_id": 81, "id": 1940116}]