Link Engine and Install a WordPress Server
In this guide we will link an existing Origo OS installation, what we call an “engine”, to the Origo Registry at origo.io. Linking an engine gives you access to more standard stacks, like a WordPress stack, and allows you to sync user accounts between multiple engines, i.e. one for development and one for testing. It also gives your engine access to the DNS services the registry provides.
Once the engine is linked and stacks are downloaded, we will install a WordPress server as an example of how Stacks work.
Objectives
- Link an engine to the Origo Registry and download stacks
- Install a WordPress server from a downloaded stack
Prerequisites
- A single-node Stabile installation
- Solid Internet connectivity
- At least 500 Gb free storage on the partion used for image storage
Source code
- The source code responsible for generating the Ubuntu Server stack is available in our Git repository .
Link your engine
- First go to https://www.origo.io/signup and sign up
- For now this requires that you either are located in Scandinavia or have a valid promocode
- Now go to the web client (https://your-engine’s-address/stabile)
- If you are currently logged into your Origo OS installation with the same username (i.e. your email address) you just signed up with at origo.io, skip to step 8.
- Go to the “Users” tab in the web client, click on “New user” and create a user with the username you signed up with at origo.io.
- Now in the user list click on the username you are currently logged in with and add your origo.io username to the field “Other accounts”. Fill out the field “Privileges to other accounts” with an “a”. Click “Save”
- Reload the web client, i.e. reload the current web page.
- Click your username in the upper right corner, and select the username you signed up to origo.io with, in order to switch to that account.
- In the dashboard click on “Link Engine…” in the right pane.
- Type the password you signed up with at origo.io and click “Link”.
- Several images should now start downloading from the registry.
Install a WordPress server
- Go to the images tab, select “All” from the “Show: ” dropdown.
- Wait for the WordPress image to complete downloading.2
- Once the image is downloaded (you should get an alert), click on “Install Stack”, select “WordPress”, from the drop-down, type a name for your server, click on “Install” and wait for the stack UI to load. The rest of this guide takes place in the stack UI.
- Once the stack UI is loaded, click on the “wordpress” drop-down and select “configure default website” – the WordPress install page should load.
- Complete the WordPress install process.
- You are now be the proud owner of a WordPress website. To visit your website, click on the “Go” menu in the upper right corner and select “to default WordPress website”.
- To access your site by a simpler name than your server’s default domain name, add an alias to “Aliases for the website”, and click on “Set!”. If the alias is available, the registry will register the name in DNS, and your website will be available at “the-alias.uncloud.co” (assuming your default DNS zone is “uncloud.co”).
- To add a new and completely separate WordPress website, select “Add new website…” from the “WordPress” drop-down.
- Type the name you want to use to access your new website, and click “Create website”. If the name is not available, try again with another name.
- Complete the WordPress installation process.
- You now have two independent WordPress websites and can of course add more if you like.
About domain names
When you add an alias to the default website, or add a new websited, and the name is not a FQDN (i.e. a fully qualified domain name), the WordPress stack integrates with the Origo Registry in order to register the name in the default DNS zone, so you end up with a domain name like “the-name.uncloud.io”. This of course only works if the name is available. If you use a FQDN as alias or name for your website, the WordPress stack will not do anything, and assumes that you have registered this name separately, and pointed it to the IP address of your server. In other words – it assumes you know, what you are doing.
About SSL
By default the WordPress stack does not configure your websites to use SSL. This is because getting a SSL-certificate from Let’s Encrypt requires your server to have a public IP address, and a FQDN pointing to it. This in turn requires your engine to allocate public IP addresses to your servers from public IP ranges.
If your engine is configured with a public IP range, you should go ahead, and configure your WordPress websites to use SSL. You do this by selecting “WordPress security” from the “WordPress” drop-down in the stack UI. You should then first “Get Let’s Encrypt certificate and enable TLS for all sites”. If this is succesfull, you should go ahead and check “Redirect http → https for all sites”.
