Guides - Deploy OpenLiteSpeed Django through the Linode Marketplace
Quickly deploy a Compute Instance with many various software applications pre-installed and ready to use.
The OpenLiteSpeed Django app automatically installs Linux, the performance web server OpenLiteSpeed, Python LSAPI, and CertBot. OpenLiteSpeed Django features HTTP/3 support and easy setup for SSL and RewriteRules. It’s flexible enough to host multiple Django apps and supports many other apps including Node.js, Ruby, and CMS software like WordPress.
Deploying a Marketplace App
The Linode Marketplace allows you to easily deploy software on a Compute Instance using the Cloud Manager. See Get Started with Marketplace Apps for complete steps.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Complete the form by following the steps and advice within the Creating a Compute Instance guide. Depending on the Marketplace App you selected, there may be additional configuration options available. See the Configuration Options section below for compatible distributions, recommended plans, and any additional configuration options available for this Marketplace App.
Click the Create Linode button. Once the Compute Instance has been provisioned and has fully powered on, wait for the software installation to complete. If the instance is powered off or restarted before this time, the software installation will likely fail.
To verify that the app has been fully installed, see Get Started with Marketplace Apps > Verify Installation. Once installed, follow the instructions within the Getting Started After Deployment section to access the application and start using it.
Configuration Options
- Supported distributions: Ubuntu 22.04 LTS
- Suggested plan: All plan types and sizes can be used.
OpenLiteSpeed Django Options
- Django User (required): Username for Django app.
- SOA Email Address: (required): Email address for free Let’s Encrypt SSL certificates.
Limited Sudo User
You need to fill out the following fields to automatically create a limited sudo user, with a strong generated password for your new Compute Instance. This account will be assigned to the sudo group, which provides elevated permissions when running commands with the sudo
prefix.
Limited sudo user: Enter your preferred username for the limited user. No Capital Letters, Spaces, or Special Characters.
Locating The Generated Sudo Password A password is generated for the limited user and stored in a
.credentials
file in their home directory, along with application specific passwords. This can be viewed by running:cat /home/$USERNAME/.credentials
For best results, add an account SSH key for the Cloud Manager user that is deploying the instance, and select that user as an
authorized_user
in the API or by selecting that option in the Cloud Manager. Their SSH pubkey will be assigned to both root and the limited user.Disable root access over SSH: To block the root user from logging in over SSH, select Yes. You can still switch to the root user once logged in, and you can also log in as root through Lish.
Accessing The Instance Without SSH If you disable root access for your deployment and do not provide a valid Account SSH Key assigned to theauthorized_user
, you will need to login as the root user via the Lish console and runcat /home/$USERNAME/.credentials
to view the generated password for the limited user.
Custom Domain (Optional)
If you wish to automatically configure a custom domain, you first need to configure your domain to use Linode’s name servers. This is typically accomplished directly through your registrar. See Use Linode’s Name Servers with Your Domain. Once that is finished, you can fill out the following fields for the Marketplace App:
- Linode API Token: If you wish to use the Linode’s DNS Manager to manage DNS records for your custom domain, create a Linode API Personal Access Token on your account with Read/Write access to Domains. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See Get an API Access Token. If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
- Subdomain: The subdomain you wish to use, such as www for
www.example.com
. - Domain: The domain name you wish to use, such as example.com.
"
) within any of the App-specific configuration fields, including user and database password fields. This special character may cause issues during deployment.Getting Started after Deployment
Accessing the OpenLiteSpeed Django App
Log in to your Compute Instance over SSH, using the sudo user created during deployment or
root
. See Connecting to a Remote Server Over SSH for assistance. You should see output similar to the following:********************************************************* Akamai Connected Cloud OpenLiteSpeed Django Marketplace App App URL: * The OpenLiteSpeed Web Admin: https://$EXAMPLE_DOMAIN:7080 * The sample Django site: https://EXAMPLE_DOMAIN/ * The Django admin user: $DJANGO_USER * The sample Django admin page: https://$EXAMPLE_DOMAIN/admin Credentials File: /home/$SUDO_USER/.credentials Documentation: https://www.linode.com/marketplace/apps/linode/openlitespeed-django/ *********************************************************
To delete this message of the day, use
rm /etc/motd
.The Django page is automatically configured with the custom domain provided during deployment, or the default rDNS.
Note For more documentation on how to assign a domain to your Linode, please review the DNS Manager guide for instructions on setting up your DNS records in the Cloud Manager, and read through DNS Records: An Introduction for general information about how DNS works.
Now that you’ve accessed your OpenLiteSpeed Django instance, check out the official OpenLiteSpeed Django documentation for further configuration steps.
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