So we built out our custom Instance Type, let’s deploy the sucker and see it in action! Here we will begin to see some the advantages of doing it in the Morpheus way. We have will have a repeatable process, that tracks history of actions, provides cloud cost comparison, and can manage my application files if I need to update anything. This is all handled under Provisioning > Instances.
Select Add Instance and choose WordPressSelecting my Group and corresponding Cloud, naming my VM CtT-WordPressConfigure your VM specs. As you will see we have our only available Layout of “Single Node on CentOS.If you click the $ next to your price, we will get a cloud comparison at all of the locations we configured for this Instance Type.You can leave this page as defaults or configure Backups if you’d like.Final page gives one last run down, and resolves any naming schemes you may have on the instance.Clicking into the Instance after we submitted the job, we’ll see a progress of the deploy and finally our MetaData, IP, and additional placement information.Using the information from the Instance page, we can navigate to our IP address. and see WordPress is ready to start up! Also note, the IP redirects to HTTPS (though I did not have this run with Let’s Encrypt SSL).
Conclusion
There you have it! We’ve tied in WordPress and a custom Instance Type in Morpheus. This speeds up the deploy, makes it repeatable, and allows you to grant access to this library item to multiple users or tenants if you are running Morpheus in a production environment.
I hope this has been informative. I look forward to making this into a multi-tiered application in a future post!
Anonyx
says:interesting and very informative, this helped me a lot thanks