From Documentation
m |
|||
Line 1: | Line 1: | ||
Deploying a Web Server | Deploying a Web Server | ||
− | =Dependencies= | + | =Dependencies - Launch Cloud Instance= |
− | Before deploying a web server, first a cloud instance must be lauched. [[ | + | Before deploying a web server, first a cloud instance must be lauched. The instruction to do this can be found [[Carpet|here]]. |
+ | # login to cloud.sharcnet.ca | ||
+ | # Don’t forget volume size | ||
+ | # Choose Debian 9.2.2 (not required, but the remaining instructions are Debian centric). | ||
+ | # Choose persistent (ephemeral is for shorter jobs) (4C-8GB) | ||
+ | # Setup keypair | ||
+ | # Associate floating ip | ||
+ | |||
+ | ==(Optional) Apply IP Address to your name server== | ||
+ | If you have a registered domain name you should apply your floating IP address to it so that you can use the "let's encrypt" service to | ||
+ | enable the secure socket layer without client side warnings. It is often best to do this at the beginning as there is typically a delay | ||
+ | in updating the name service. | ||
+ | |||
+ | =Login to Server & perform preliminaries= |
Revision as of 08:44, 28 May 2018
Deploying a Web Server
Dependencies - Launch Cloud Instance
Before deploying a web server, first a cloud instance must be lauched. The instruction to do this can be found here.
- login to cloud.sharcnet.ca
- Don’t forget volume size
- Choose Debian 9.2.2 (not required, but the remaining instructions are Debian centric).
- Choose persistent (ephemeral is for shorter jobs) (4C-8GB)
- Setup keypair
- Associate floating ip
(Optional) Apply IP Address to your name server
If you have a registered domain name you should apply your floating IP address to it so that you can use the "let's encrypt" service to enable the secure socket layer without client side warnings. It is often best to do this at the beginning as there is typically a delay in updating the name service.