Deploying a LAMP Stack 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.
A LAMP (Linux, Apache, MySQL, PHP) stack is a popular, free, and open-source web software bundle used for hosting websites on Linux. This software environment is a foundation for popular PHP application frameworks like WordPress, Drupal, and Laravel. After you deploy your LAMP Marketplace App, you can upload your existing PHP application code to it or use a PHP framework to write a new application on your Linode.
Deploying the LAMP Stack 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-3 minutes after the Linode has finished provisioning.
Configuration Options
LAMP Stack Options
You can configure your LAMP Stack App by providing values for the following fields:
| Field | Description |
|---|---|
| MySQL Root Password | The root password for your LAMP stack’s MySQL database. This is not the same as your Linode’s root password. Required. |
| E-Mail Address | E-Mail address for Let’s Encrypt SSL certificate. This is also used as the SOA email address if you also enter a domain. Required. |
| The limited sudo user to be created for the Linode | This is the limited user account to be created for the Linode. This account has sudo user privileges. |
| The password for the limited sudo user | Set a password for the limited sudo user. The password must meet the complexity strength validation requirements for a strong password. This password can be used to perform any action on your server, similar to root, so make it long, complex, and unique. |
| The SSH Public Key that will be used to access the Linode | If you wish to access SSH via Public Key (recommended) rather than by password, enter the public key here. |
| Disable root access over SSH? | Select Yes to block the root account from logging into the server via SSH. Select No to allow the root account to login via SSH. |
| Your Linode API Token | Your Linode API Token is needed to create DNS records. If this is provided along with the subdomain and domain fields, the installation attempts to create DNS records via the Linode API. If you don’t have a token, but you want the installation to create DNS records, you must
create one before continuing. |
| Subdomain | The subdomain you wish the installer to create a DNS record for during setup. The suggestion given is www. The subdomain should only be provided if you also provide a domain and API Token. |
| Domain | The domain name where you wish to host your website. The installer creates a DNS record for this domain during setup if you provide this field along with your API Token. |
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, Debian 11, Ubuntu 20.04 LTS
- Recommended plan: The Linode plan you deploy your LAMP stack on should account for the estimated workload. If you are standing up a simple web page, you can use a 1GB Linode (Nanode) or 2GB Linode. If you are standing up a larger or more robust web app, then consider a plan with higher RAM and CPU allocations.
Getting Started After Deployment
After your LAMP stack has finished deploying, you can:
Connect to your Linode via SSH. You will need your Linode’s root password to proceed. Note that your Linode’s web root will be located in the
/var/www/htmldirectory.Navigate to the public IP address or domain entered during creation of your Linode in a browser. You will see the default Apache webpage.
Consult the following guides to learn more about working with the various components of the LAMP stack:
Upload files to your web root directory with an SFTP application like FileZilla. Use the same root credentials that you would use for SSH.
Assign a domain name to your Linode’s IP address. 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.
Software Included
The LAMP Stack Marketplace App installs the following software on your Linode:
| Software | Description |
|---|---|
| Apache HTTP Server | Web server that can be used to serve your site or web application. |
| MySQL Server | Relational database. |
| PHP 7 | General purpose programming language. |
| UFW (Uncomplicated Firewall) | Firewall utility. Ports 22/tcp, 80/tcp, and 443/tcp for IPv4 and IPv6 will allow outgoing and incoming traffic. |
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