(gs):Django GridContainer EOL FAQs

  • This page was last modified on March 7, 2011, at 13:09.
The (mt) Community Wiki is a collaborative project. Any (mt) Media Temple customer or employee may contribute. Not all articles and/or content have been tested for accuracy by (mt) Media Temple.

For officially moderated and tested articles, be sure to visit our KnowledgeBase.

From (mt) Community Wiki

Beginning early April 2011, (mt) Media Temple will no longer be offering the Django application GridContainer attached to your (gs) Grid-Service.

FAQs

What’s a GridContainer?
A GridContainer is a service attached to your (gs) that acts like a stand-alone virtual server for your application.
Which GridContainer do I have, and is it being used?
GridContainers are listed in the AccountCenter under your (gs) Grid-Service(s). If you have multiple (gs) services or multiple containers, feel free to contact support for assistance.
Why is (mt) Media Temple canceling my Django GridContainer?
Django container usage is very low on the (gs) and future Grid improvements will cause the Django and Ruby Containers to become obsolete. We are encouraging Django-savvy users to set up their apps on a (ve) Server, where they will find more resources and greater control.
How do I cancel my GridContainer?
You can request to close any service via the AccountCenter. For more information on closing a service, please read this article.
When will my Django GridContainer become unavailable?
No earlier than 4/1/11. Minimum 30 days notification will be given before any service is affected.
I want to keep my Django application running. How can I prepare for the change?
Support Agents will be glad to help you activate a (ve) Server where you can move your Django app. To learn more about installing Django on your (ve) Server, please refer to these articles:
Retrieved from "http://wiki.mediatemple.net/w/(gs):Django_GridContainer_EOL_FAQs"