# Launching a Wordpress app on StackOS

{% embed url="<https://youtu.be/_zhES8f8ayU?t=383>" %}
Video demonstation of the deployment process
{% endembed %}

## Steps to deploy a WordPress Application on StackOS  <a href="#id-64d6" id="id-64d6"></a>

### **1. Go to** [**app.stackos.io**](https://app.stackos.io/)&#x20;

### **2. Connect with Metamask**&#x20;

Select the Smart Chain, if you don’t have the Smart Chain follow this simple guide: <https://academy.binance.com/en/articles/connecting-metamask-to-binance-smart-chain>.

![](/files/-Ml9qsjbTdbytYNNuw0G)

### **3.** Buy $STACK and $BNB&#x20;

You need Stack tokens and  BNB in your Metamask wallet on the Smart Chain. These can be bought on [Pancakeswap](https://pancakeswap.finance/swap).&#x20;

Guid&#x65;**:** <https://youtu.be/09dZWYwI2AE?t=124>

**4.** **To launch an application, you need compute resources; these can be bought under the ‘Upgrade’ tab.**

![](/files/-Ml9r3R0qWkUDt8cIueq)

&#x20;**5.** **Buy the number of resources you need. For the Wordpress application in our App Store, you need 1100 CPU, 1100 MB memory, 5GB disk space, and 100GB bandwidth. Click on the ‘Upgrade’ button, a Metamask window should pop up, asking for permission to spend the tokens, click on the ‘Confirm’ button. After that, another Metamask window will appear, asking permission for the actual payment. Click on the ‘Confirm’ button again.**

![](/files/-Ml9rUycUPHIgTb6qWhv)

&#x20;**6.** **You will get a pop-up confirming the upgrade of your resources; congratulations! Now click on ‘App Store’ at the top of the page. When the dashboard is loaded, click on ‘Wordpress.’ A window appears where you can type the name of your application, the Host URL where people can find the application, and if you want, a specific database username and password. If you need more than the standard compute resources for your app you can switch to the advanced tab and increase the CPU and RAM. When you filled in this information, click the ‘Deploy App’ button. Step 7 is relevant if you want to add your own URL.**

![](/files/-Ml9riG2xDVGHujPlEpH)

&#x20;**7.** **This step is only important when you want to use your own domain name. Type in the Host URL you want to use. Then click on ‘Verify’. If it can not automatically be verified, you have to change some settings at your DNS provider:** [**https://medium.com/stackos/managing-dns-on-stackos-518d027c4a08**](https://medium.com/stackos/managing-dns-on-stackos-518d027c4a08)

![](/files/-Ml9t26Em4wEuZIiLGc6)

![](/files/-Ml9t6YVtRAgXUSDvhTz)

**8. Congratulations! Your application is now deployed on the decentralized cloud of StackOS! The application will appear on your dashboard to keep an eye on the activity and change settings when necessary.**

![](/files/-Ml9tKg8NJ1ceSpq9PTl)

&#x20;**9. To enter the back-end of your Wordpress application type in the URL and add /wp-admin to it.**&#x20;

**For example: Wordpress.stackos.io/wp-admin. From here you start the set-up process of your website.**

<br>

## ✅ For More Information

Wordpress has many details that are not obvious to those who are "moving" from a pre-built site to another provider (which includes StackOS).

We have documented some commonly helpful knowledge which may help your migration to any other host, with some tips especially for StackOS.

This effort was made due to many admins having experience setting up WordPress, but not having the opportunity to "migrate" installations.

{% content-ref url="/pages/dsCPNqOelVyElWKUg6Pf" %}
[WordPress Migration](/stackos-docs/wordpress/wordpress-migration.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stackos.io/stackos-docs/wordpress/launching-a-wordpress-app-on-stackos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
