Gigya Job Openings

Staging Release Environment Setup

Skip to end of metadata
Go to start of metadata

Description

When Gigya releases a major update to our core product, we give you an opportunity to try out the new release in a staging environment to ensure that your code base and site configuration remain compatible with the new release, prior to it being launched.

Availability

The staging environment is typically available two weeks prior to a major release.

Once you receive notification that a new release is in staging, you can access the staging environment by following the steps below. 

Access to Gigya's Staging

You can access Gigya's Console on staging environment directly on the staging domains. In addition, you can edit your HOSTS file so that it loads the staging web SDK (e.g., cdns.us1-st1.gigya.com), so as to test changes to your site without making changes to live sites. 

Gigya staging Console:

Gigya staging CDNS:

Editing the HOSTS File

You can access Gigya's staging environment, by updating the HOSTS file of all machines on which you will be testing the new release. This will redirect all requests to Gigya's servers to the Gigya staging environment, for all data centers. If you are using server-side API calls, you will also need to edit the hosts file on your organization's staging server. 

  1. Backup your current hosts file and then create a new one using this data, so that when the staging period is over, you can replace the development hosts file with your original.
  2. Update the hosts file with the configurations detailed below.
  3. Clean your browser cache and restart the browser. In some cases, you will need to restart your computer.

    Opening and closing Fiddler after closing the browser also cleans the hosts cache.

  4. After the staging period is over, make sure to comment out or delete the additional lines in the hosts file and, again, clean both browser and hosts cache.

 

  • You cannot work simultaneously on both staging and production environments when using the HOSTS file.
  • In order for the environment to work, you have to manually accept each one of the certificates for the URL CNAMEs.

 

Staging Environment HOSTS Configuration

Unable to render {include} The included page could not be found.

 

#Gigya Staging Hosts# 
#--- ST1 18.205.215.220
#--- CDN_Gigya_US_EU_AU -> 18.205.215.220
18.205.215.220                       cdn.gigya.com
18.205.215.220                       cdns.gigya.com
18.205.215.220                       cdn.us1.gigya.com
18.205.215.220                       cdns.us1.gigya.com
18.205.215.220                       cdn1.gigya.com
18.205.215.220                       cdn2.gigya.com
18.205.215.220                       cdn3.gigya.com
18.205.215.220                       cdn4.gigya.com
18.205.215.220                       cdn5.gigya.com
18.205.215.220                       cdns1.gigya.com
18.205.215.220                       cdns2.gigya.com
18.205.215.220                       cdns3.gigya.com
18.205.215.220                       cdns4.gigya.com
18.205.215.220                       cdns5.gigya.com
18.205.215.220                       cdn.us1.gigya.com
18.205.215.220                       cdns.us1.gigya.com
18.205.215.220                       cdn1.us1.gigya.com
18.205.215.220                       cdn2.us1.gigya.com
18.205.215.220                       cdn3.us1.gigya.com
18.205.215.220                       cdn4.us1.gigya.com
18.205.215.220                       cdn5.us1.gigya.com
18.205.215.220                       cdns1.us1.gigya.com
18.205.215.220                       cdns2.us1.gigya.com
18.205.215.220                       cdns3.us1.gigya.com
18.205.215.220                       cdns4.us1.gigya.com
18.205.215.220                       cdns5.us1.gigya.com

18.205.215.220                       cdn.eu1.gigya.com
18.205.215.220                       cdns.eu1.gigya.com
18.205.215.220                       cdn1.eu1.gigya.com
18.205.215.220                       cdn2.eu1.gigya.com
18.205.215.220                       cdn3.eu1.gigya.com
18.205.215.220                       cdn4.eu1.gigya.com
18.205.215.220                       cdn5.eu1.gigya.com
18.205.215.220                       cdns1.eu1.gigya.com
18.205.215.220                       cdns2.eu1.gigya.com
18.205.215.220                       cdns3.eu1.gigya.com
18.205.215.220                       cdns4.eu1.gigya.com
18.205.215.220                       cdns5.eu1.gigya.com

18.205.215.220                       cdn.au1.gigya.com
18.205.215.220                       cdns.au1.gigya.com
18.205.215.220                       cdn1.au1.gigya.com
18.205.215.220                       cdn2.au1.gigya.com
18.205.215.220                       cdn3.au1.gigya.com
18.205.215.220                       cdn4.au1.gigya.com
18.205.215.220                       cdn5.au1.gigya.com
18.205.215.220                       cdns1.au1.gigya.com
18.205.215.220                       cdns2.au1.gigya.com
18.205.215.220                       cdns3.au1.gigya.com
18.205.215.220                       cdns4.au1.gigya.com
18.205.215.220                       cdns5.au1.gigya.com
 
#--- AU1 -> 54.206.53.60
18.205.215.220                       console.gigya.com
54.206.53.60                         gscounters.au1.gigya.com
54.206.53.60                         gm.au1.gigya.com
54.206.53.60                         comments.au1.gigya.com
54.206.53.60                         gcs.au1.gigya.com
54.206.53.60                         ds.au1.gigya.com
54.206.53.60                         reports.au1.gigya.com
54.206.53.60                         socialize.au1.gigya.com
54.206.53.60                         accounts.au1.gigya.com
54.206.53.60                         ids.au1.gigya.com
54.206.53.60                         admin.au1.gigya.com
54.206.53.60                         fidm.au1.gigya.com
 
#--- EU1 -> 54.229.81.86
18.205.215.220                       console.gigya.com
54.229.81.86                         gscounters.eu1.gigya.com
54.229.81.86                         gm.eu1.gigya.com
54.229.81.86                         comments.eu1.gigya.com
54.229.81.86                         gcs.eu1.gigya.com
54.229.81.86                         ds.eu1.gigya.com
54.229.81.86                         reports.eu1.gigya.com
54.229.81.86                         socialize.eu1.gigya.com
54.229.81.86                         accounts.eu1.gigya.com
54.229.81.86                         ids.eu1.gigya.com
54.229.81.86                         admin.eu1.gigya.com
54.229.81.86                         fidm.eu1.gigya.com
 
#--- US1  -> 18.205.215.220
18.205.215.220                       console.gigya.com
18.205.215.220                       gscounters.us1.gigya.com
18.205.215.220                       gm.us1.gigya.com
18.205.215.220                       comments.us1.gigya.com
18.205.215.220                       gcs.us1.gigya.com
18.205.215.220                       ds.us1.gigya.com
18.205.215.220                       reports.us1.gigya.com
18.205.215.220                       socialize.us1.gigya.com
18.205.215.220                       accounts.us1.gigya.com
18.205.215.220                       ids.us1.gigya.com
18.205.215.220                       admin.us1.gigya.com
18.205.215.220                       fidm.us1.gigya.com
18.205.215.220                       console.gigya.com
18.205.215.220                       gscounters.gigya.com
18.205.215.220                       gm.gigya.com
18.205.215.220                       comments.gigya.com
18.205.215.220                       gcs.gigya.com
18.205.215.220                       ds.gigya.com
18.205.215.220                       reports.gigya.com
18.205.215.220                       socialize.gigya.com
18.205.215.220                       login.gigya.com
18.205.215.220                       soc.li
18.205.215.220                       fw.to
18.205.215.220                       accounts.gigya.com
18.205.215.220                       admin.gigya.com

#If you are using a CNAME in your production environment (and have "Enable CNAME" checked in the social provider configuration), then in order to test social login against staging, you will need to add another line to the hosts file in the following format:

#US Customers
#18.205.215.220  <CNAME>
 
#EU Customers
#54.229.81.86  <CNAME>

#AU Customers
#54.206.53.60  <CNAME>


#For example:
#18.205.215.220   login.mysite.com

#If you are using a custom API domain prefix, you will need to add another line to the hosts file in the following format: 
#US Customers
#18.205.215.220  <API Domain Prefix>

#EU Customers
#54.229.81.86  <API Domain Prefix>

#AU Customers
#54.206.53.60  <API Domain Prefix>


#For example:
#18.205.215.220   gigya.mysite.com

#For the RU datacenter

#--- RU1  -> 95.213.238.72
95.213.238.72                       console.ru1.gigya.com
95.213.238.72                       gscounters.ru1.gigya.com
95.213.238.72                       gm.ru1.gigya.com
95.213.238.72                       comments.ru1.gigya.com
95.213.238.72                       gcs.ru1.gigya.com
95.213.238.72                       ds.ru1.gigya.com
95.213.238.72                       reports.ru1.gigya.com
95.213.238.72                       socialize.ru1.gigya.com
95.213.238.72                       accounts.ru1.gigya.com
95.213.238.72                       ids.ru1.gigya.com
95.213.238.72                       admin.ru1.gigya.com
95.213.238.72                       fidm.ru1.gigya.com
95.213.238.72                       console.gigya.com
95.213.238.72                       gscounters.gigya.com
95.213.238.72                       gm.gigya.com
95.213.238.72                       comments.gigya.com
95.213.238.72                       gcs.gigya.com
95.213.238.72                       ds.gigya.com
95.213.238.72                       reports.gigya.com
95.213.238.72                       socialize.gigya.com
95.213.238.72                       login.gigya.com
95.213.238.72                       soc.li
95.213.238.72                       fw.to
95.213.238.72                       accounts.gigya.com
95.213.238.72                       admin.gigya.com

#--- RU CDN_Gigya -> 95.213.238.72
95.213.238.72                       cdn.gigya.com
95.213.238.72                       cdns.gigya.com
95.213.238.72                       cdn1.gigya.com
95.213.238.72                       cdn2.gigya.com
95.213.238.72                       cdn3.gigya.com
95.213.238.72                       cdn4.gigya.com
95.213.238.72                       cdn5.gigya.com
95.213.238.72                       cdns1.gigya.com
95.213.238.72                       cdns2.gigya.com
95.213.238.72                       cdns3.gigya.com
95.213.238.72                       cdns4.gigya.com
95.213.238.72                       cdns5.gigya.com
95.213.238.72                       cdn.ru1.gigya.com
95.213.238.72                       cdns.ru1.gigya.com
95.213.238.72                       cdn1.ru1.gigya.com
95.213.238.72                       cdn2.ru1.gigya.com
95.213.238.72                       cdn3.ru1.gigya.com
95.213.238.72                       cdn4.ru1.gigya.com
95.213.238.72                       cdn5.ru1.gigya.com
95.213.238.72                       cdns1.ru1.gigya.com
95.213.238.72                       cdns2.ru1.gigya.com
95.213.238.72                       cdns3.ru1.gigya.com
95.213.238.72                       cdns4.ru1.gigya.com
95.213.238.72                       cdns5.ru1.gigya.com
 

#If you are using a CNAME in your production environment (and have "Enable CNAME" checked in the social provider configuration), then in order to test social login against staging, you will need to add another line to the hosts file in the following format:


#RU Customers
#95.213.238.72  <CNAME>

#For example:
#95.213.238.72   login.mysite.com

#If you are using a custom API domain prefix, you will need to add another line to the hosts file in the following format: 


#RU Customers
#95.213.238.72  <API Domain Prefix>

#For example:
#95.213.238.72   gigya.mysite.com
 
 
#For the CN datacenter
139.196.75.254                      console.gigya-api.cn
139.196.75.254                      gscounters.gigya-api.cn
139.196.75.254                      gm.gigya-api.cn
139.196.75.254                      gcs.gigya-api.cn
139.196.75.254                      ds.gigya-api.cn
139.196.75.254                      reports.gigya-api.cn
139.196.75.254                      socialize.gigya-api.cn
139.196.75.254                      accounts.gigya-api.cn
139.196.75.254                      ids.gigya-api.cn
139.196.75.254                      admin.gigya-api.cn
139.196.75.254                      fidm.gigya-api.cn
139.196.75.254                      login.gigya-api.cn
 
#--- CN CDN_Gigya -> 139.196.75.254
139.196.75.254                      cdn.gigya-api.cn
139.196.75.254                      cdns.gigya-api.cn
139.196.75.254                      cdn1.gigya-api.cn
139.196.75.254                      cdn2.gigya-api.cn
139.196.75.254                      cdn3.gigya-api.cn
139.196.75.254                      cdn4.gigya-api.cn
139.196.75.254                      cdn5.gigya-api.cn
139.196.75.254                      cdns1.gigya-api.cn
139.196.75.254                      cdns2.gigya-api.cn
139.196.75.254                      cdns3.gigya-api.cn
139.196.75.254                      cdns4.gigya-api.cn
139.196.75.254                      cdns5.gigya-api.cn

It is important to configure your CName, if you are using one, as described at the end of the file.

If your site uses a data center other than US1, ensure that you remove the entries corresponding to other data centers in your hosts file to avoid the DNS pointing to an incorrect IP address.

 

 

  • No labels