Domain & Host Registration, WordPress Installation, Email & SSL Setup
I. Registrar (Namecheap.com)
- Set up account & contact information.
- Purchased domain name (AncientGreekKeyboard.com).
- Turned off Parking Page.
II. Hosting Company (SiteGround.com)
- Set up account & contact information.
- Set up cPanel & FTP passwords.
- Located DNS records for hosted site.
III. Registrar
- Pasted DNS address from the hosting company into the Custom DNS nameservers.
- Clicked checkmark to save the new DNS addresses.
IV. Hosting Company
- Reviewed online directions for installing WordPress manually.
- Accessed cPanel.
- Downloaded WordPress installation ZIP file. Unzipped it.
- Set up WordPress database & recorded database credentials.
- Added these credentials to WP-CONFIG.PHP and saved the file.
- Uploaded WordPress files & folders to Host.
- Manually installed WordPress.
- Logged into WordPress.
- Installed & activated the Coming Soon plugin.
- Set up email accounts on cPanel.
- Accessed cPanel.
- Mail > Email Accounts
- Set up email address, password, size.
- Created email account.
- Beside new account, clicked More > Access Webmail.
- Chose Default Webmail Application.
- Sent email configuration information to a different email address.
- Tested email to make sure it was working correctly.
- Set up SSL on WordPress
- Activated SSL with “Let’s Encrypt” on cPanel.
- Forced SSL login via code in WP-CONFIG.PHP.
- Uploaded WP-CONFIG.PHP.
- Logged into WP and updated WordPress Address (URL) & Site Address (URL) to HTTPS.
- Installed & activated Velvet Blues Update URLs plugin.
- Clicked “UPDATE URLS” link & updated links on WP from HTTP to HTTPS.
- Used HTACCESS to redirect HTTP to HTTPS.
- Verified Permalinks were set to HTTPS & were using the desired format.
- Verified that HTTP links on the site were correctly redirecting to HTTPS.
- Manually updated STYLE.CSS so that background images loaded from HTTPS rather than the development site (Did this on Day 2).
UPDATE: In hindsight, the following actions should have been performed on this day:
- HTACCESS should have been set at this point to deny access to the site to everyone but myself until the the site was ready to go live.
- The WWW version of the site should have been created instead of the non-WWW version. (The site must be WWW if it is ever configured for Cloudflare.)
Other posts in this series:
- Manual eCommerce Site Setup On SiteGround: Day 1
- Manual eCommerce Site Setup On SiteGround: Day 2
- Manual eCommerce Site Setup On SiteGround: Day 3
- Manual eCommerce Site Setup On SiteGround: Day 4
- Manual eCommerce Site Setup On SiteGround: Day 5
- Manual eCommerce Site Setup On SiteGround: Day 6
- Manual eCommerce Site Setup On SiteGround: Day 7
- Manual eCommerce Site Setup On SiteGround: Day 8: (Site brought live)
- Manual eCommerce Site Setup On SiteGround: Week 2
- Manual eCommerce Site Setup On SiteGround: Week 3
- Manual eCommerce Site Setup On SiteGround: Week 4
- Week 5: Speed optimization tests
- Manual eCommerce Site Setup On SiteGround: Week 6
- How to convert a non-WWW WordPress site to WWW