Deploying Django through the Linode Marketplace
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Django is a web development framework for the Python programing language. It enables rapid development, while favoring pragmatic and clean design. Django was initially developed for use in a newspaper’s website division, and as a result the Django framework is very well suited to developing content-centric applications. It’s also very flexible in its ability to facilitate many complex content management operations.
Deploying the Django Marketplace App
The Linode Marketplace allows you to easily deploy software on a Linode using the Linode Cloud Manager.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Compute Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Fill out all required Options for the selected app as well as any desired Advanced Options (which are optional). See the Configuration Options section for details.
Complete the rest of the form as discussed within the Getting Started > Create a Linode.
Click the Create Linode button. Once the Linode has provisioned and has fully powered on, wait for the software installation to complete. If the Linode is powered off or restarted before this time, the software installation will likely fail. To determine if the installation has completed, open the Linode’s Lish console and wait for the system login prompt to appear.
Follow the instructions within the Getting Started After Deployment section.
Software installation should complete within 2-5 minutes after the Linode has finished provisioning.
Configuration Options
Django Options
You can configure your Django App by providing values for the following fields:
Field | Description |
---|---|
Django USER | Username for your Django application. Required. |
Django Password | Password for the Django USER. Required. |
Django USER email | Email address for the Django USER. The format for the email must be in the form user@email.tld. Required. |
General Options
For advice on filling out the remaining options on the Create a Linode form, see Getting Started > Create a Linode. That said, some options may be limited or recommended based on this Marketplace App:
- Supported distributions: Debian 10
- Recommended minimum plan: All plan types and sizes can be used.
Getting Started after Deployment
Access Django
NoteThe Django Marketplace App will assignDjangoApp
as the Django project name.
After Django has finished installing, you will be able to access your Django site at your Linode’s IPv4 address, for instance: http://yourlinodeip:8000
.
To find your Linode’s IPv4 address. Click on the Linodes link in the sidebar. You will see a list of all your Linodes.
Find the Linode you just created when deploying your app and select it.
Navigate to the Networking tab.
The IP address will be displayed under the Address column in the IPv4 table.
Copy and paste the IPv4 address into a browser window followed by
:8000
. You should see the Django test page appear.Once you have verified that you can access your Django site via the browser, you can log in using the admin credentials you created when deploying your app. Update the address in the browser to:
http://yourlinodeip:8000/admin
.Once logged in, you will have access to the Admin console. Now you can begin configuring your site.
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on