DinoStore Build

Dino-Store Blog; 1: Provisioning Durable Storage with S3

First, we need to create a Bucket this is because we need to upload files, this creates a place to store them on AWS. We then have to locate the region as US West. Then turn on versioning and logging, just in case we need to version anything off for backup. Turn on logging so we can see if the logs have any issues.

Creating the Dino Sotre Buckets.PNG

Inside of the Resources Bucket we create five folders label them as;

  • * siteimages
  • * productimages
  • * css
  • * js
  • * configurations

After these are created we upload the content into the product images which we then put into the Amber’s Dino Store resources folder. There are two different folders which we upload into, these are called; Product images and Site images. The Site images are for the website banners.

Go into the Visual Studio program and then into the content folder, this will lead you to the bootstrap.css file where we will find the Source Background image. This is done via the Ctrl – f function. The Background picture will be replaced with the link for the Site image. You also need to go through and made sure everyone has permission to view this folder.

Once this is saved we need to upload the next files from the local folder and into the AWS container. These are the files below.

  • bootstrap.js,
  • Bootstrap.css
  • jquery-2.0.2.js

Creating the Dino Sotre Buckets

After this we need to find the Index file, this is under the Solution items. Then we need to delete the old link and replace with the new link to the AWS folder. We now have a folder which loads from the AWS, instead of the local, you can see this below.

The next step is to go into the other bucket “ambersdinostoredegraded“, and upload the Index file into it.  Once this is done you need to make sure the file is public, so go in and change the Permissions.

Making sure everyone has permissions ;5

Now we need to make the Bucket act as a website, this is done via the Properties which is inside the Bucket. Here you can have the option to upload your own Error page, this is shown below.

 

Static Web hosting; 5OK, so now we can see the permissions are set as Everyone Can View, this means everything can be seen. Now we need to go back into the Visual studio and look for the Site1.Master. You need to change the Javascript and Css links to re-link to the new file that has been put out in the AWS console.

Changing the Scripts again to the AWS Console ; 9.PNGNow we need to go into the SQl work bench, here we will go into the image reference for the individual Dinosaur. Then change the links from the local host to the AWS folder, this is shown below.

MYSQl COde change.PNG

Now we can build the project. You can go in and inspect the elements to see where they are pulling the different images from, they should be from the AWS.

This lab is finished.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s