<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: stephin007</title>
    <description>The latest articles on DEV Community by stephin007 (@stephin007).</description>
    <link>https://dev.to/stephin007</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F413638%2F262fff15-1e9e-461d-85bb-6d84b45d0ba6.png</url>
      <title>DEV Community: stephin007</title>
      <link>https://dev.to/stephin007</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/stephin007"/>
    <language>en</language>
    <item>
      <title>How to deploy multiple sites to firebase hosting?</title>
      <dc:creator>stephin007</dc:creator>
      <pubDate>Mon, 04 Jan 2021 02:45:08 +0000</pubDate>
      <link>https://dev.to/forcommunity/how-to-deploy-multiple-sites-to-firebase-hosting-38l3</link>
      <guid>https://dev.to/forcommunity/how-to-deploy-multiple-sites-to-firebase-hosting-38l3</guid>
      <description>&lt;p&gt;Wait, what..is that even possible... Cause one project in firebase means only one hosting for that particular project, Right..!&lt;br&gt;
Well, my fellow reader, Firebase has this feature to deploy multiple sites in a single firebase hosting. You might be wondering why do we need multiple websites for a single project, yeah I thought that too, so apparently, there might be situations, in which the user might need 2 separate apps i.e. one for customers, one for admin employees - both of which share the same database and functions.&lt;/p&gt;

&lt;p&gt;In this blog, let me walk through the steps which you will need to follow strictly to deploy the sites correctly to their respective domains.&lt;/p&gt;
&lt;h4&gt;
  
  
  &lt;em&gt;&lt;strong&gt;NOTE: I ASSUME THAT YOU HAVE ALREADY DEPLOYED ONE OF YOUR APPS TO YOUR FIREBASE PROJECT, OTHERWISE, YOU WON'T BE ABLE TO DEPLOY MULTIPLE SITES&lt;/strong&gt;&lt;/em&gt;
&lt;/h4&gt;

&lt;p&gt;Great, I hope you are still with me, Lets Begin.&lt;/p&gt;
&lt;h2&gt;
  
  
  1 Define Your Site Name(s)
&lt;/h2&gt;

&lt;p&gt;Assume, there is an e-commerce vendor, whose consumer app is done and deployed on firebase, now you are working on the admin site for the vendor which will help the user to add products to his e-commerce website.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In the Firebase Hosting Console, scroll to the bottom under the &lt;strong&gt;Advanced Section&lt;/strong&gt; you will find an option to &lt;em&gt;Add Another Site&lt;/em&gt; , When you click that, you will see the below screen.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609696086198%2FnuTKbffL8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609696086198%2FnuTKbffL8.png" alt="multisite-hosting.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Add the site name for ex:  &lt;em&gt;admin-multi-site-magic&lt;/em&gt; , then you will see the site will be added like this.
&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609696215168%2FRCnnQS150.png" alt="multi-siteimage2.png"&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Wait, it's not over yet, you have just added the site, you have not deployed anything to your new site, lets see how that's done&lt;/p&gt;
&lt;h2&gt;
  
  
  2 Install the latest Firebase Tools and Initialize hosting
&lt;/h2&gt;

&lt;p&gt;You need Firebase Tools v4.2 or later for multisite hosting.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm i -g firebase-tools@latest
firebase -v

firebase init hosting
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;&lt;p&gt;One thing to note here, to make sure you add the word &lt;em&gt;hosting&lt;/em&gt; in the last command since firebase has a lot of functions so when you add hosting after init, it will understand that it needs to only initialize the hosting.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;It will prompt you some questions to select the project where you want to host it, make sure to select the correct project.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3 Update the firebase.json
&lt;/h2&gt;

&lt;p&gt;As soon as you complete the above step, you will see that firebase adds 2 files to your project directory i.e. &lt;code&gt;.firebaserc&lt;/code&gt; &lt;code&gt;firebase.json&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Now we just need to update this &lt;code&gt;firebase.json&lt;/code&gt; by adding a field called &lt;code&gt;target&lt;/code&gt;. Firebase uses this target, (yes you guessed it probably) to target the site to which your code needs to be deployed.&lt;/p&gt;

&lt;p&gt;If you are using React, your deployable code will be your &lt;code&gt;build&lt;/code&gt; folder&lt;br&gt;
and If you are using Angular, your deployable code will be your &lt;code&gt;dist&lt;/code&gt; folder.&lt;br&gt;
The name of the target can be anything, but better to keep it relevant to the site you are about to deploy. Add your target file as shown below, just above the public field&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;{
  "hosting": {
    "target": "admin",
    "public": "build",
    "ignore": [
      "firebase.json",
      "**/.*",
      "**/node_modules/**"
    ],
    "rewrites": [
      {
        "source": "**",
        "destination": "/index.html"
      }
    ]
  }
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4 Letting firebase know about the new target you just created.
&lt;/h2&gt;

&lt;p&gt;We need to associate the sites with a local target so Firebase knows which code to deploy where. We run the following command for each site: &lt;br&gt;
&lt;code&gt;firebase target:apply hosting &amp;lt;target-name&amp;gt; &amp;lt;resource-name&amp;gt;&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;firebase target:apply hosting admin admin-multi-site-magic

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;where the target-name is just a unique name you choose, and resource-name is the site from step 1.&lt;/p&gt;

&lt;h2&gt;
  
  
  5 Deploy to FIrebase
&lt;/h2&gt;

&lt;p&gt;We have done all the major steps, now we can deploy it to firebase to the targeted site.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;firebase deploy --only hosting
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And that's it, I hope you liked it if you do leave some reactions and comments. Also, I am open to collaboration you can mail us or ping us on any of the social media platforms.&lt;/p&gt;

</description>
      <category>firebase</category>
      <category>domain</category>
      <category>hosting</category>
    </item>
    <item>
      <title>How to sync your local git and remote git repository changes?</title>
      <dc:creator>stephin007</dc:creator>
      <pubDate>Fri, 01 Jan 2021 11:14:04 +0000</pubDate>
      <link>https://dev.to/forcommunity/how-to-sync-your-local-git-and-remote-git-repository-changes-4h37</link>
      <guid>https://dev.to/forcommunity/how-to-sync-your-local-git-and-remote-git-repository-changes-4h37</guid>
      <description>&lt;p&gt;Today we will focus on how we can synchronize our GitHub local repository master with an upstream repository branch of the GitHub project.&lt;br&gt;
Now, you might think what is an upstream branch,&lt;br&gt;
 &lt;strong&gt;Upstream branches&lt;/strong&gt; define the branch tracked on the remote repository by your local remote branch (also called the remote-tracking branch), the below figure will help ya'll understand.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609477544959%2FF3072bw2g.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609477544959%2FF3072bw2g.png" alt="upstream-1-768x527.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;** &lt;em&gt;NOTE&lt;/em&gt; : When we made any CLONE/PULL for the first time this is not required as we do fork the repository for the first time all the content in both will be the same.**&lt;/p&gt;

&lt;h4&gt;
  
  
  So, Why do we need this process to be done?
&lt;/h4&gt;




&lt;p&gt;This is very much necessary if you are working in a team and the teammates are working on different aspects of the project and you yourselves are working on something, &lt;br&gt;
Certain files will differ in both repositories as there are many other developers are merging the code upstream and your branch will not have that changes unless you sync the repository with the current upstream, so you might need to keep up with their code changes as well, this is called syncing your changes with your local and remote repo.&lt;/p&gt;

&lt;p&gt;Synching will override the local repository with a master remote repository. And if there are files in the local repository that do not exist in the remote repo, local files get removed&lt;/p&gt;

&lt;p&gt;If you don't, this will cause conflicts while you raise a PULL REQUEST.&lt;/p&gt;

&lt;p&gt;Now, let me walk you through how to sync your changes with other changes by other developers.&lt;br&gt;
Here I have the taken example of the &lt;strong&gt;Opencart&lt;/strong&gt; GitHub project. First, change your working directory to the file location where you want to clone the project with the command.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$ cd your/local/storage/path&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  STEP 1: Clone your project with the command.
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480354853%2FMd7b1oX8H.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480354853%2FMd7b1oX8H.png" alt="clone.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After the clone is completed then move to the Opencart folder&lt;br&gt;
This will move to the current working directory as &lt;code&gt;opencart&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  STEP 2: List the current configured remote repository for your fork.
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;$ git remote -v&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;This will list your forked repository response will be as below :&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480596471%2F_nY9P5z5H.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480596471%2F_nY9P5z5H.png" alt="remote.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is our repository branch content now we have to get a project from the upstream repository&lt;br&gt;
Now Specify a new remote upstream repository that will be synced with the fork. In Opencart Project this &lt;em&gt;&lt;a href="https://github.com/opencart/opencart.git" rel="noopener noreferrer"&gt;https://github.com/opencart/opencart.git&lt;/a&gt;&lt;/em&gt; is my upstream repository. Run the following command.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$ git remote add upstream https://github.com/opencart/opencart.git&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Now you cross-check that the new upstream repository created for your forked repo. To do this run the same command again as below.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$ git remote -v&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Now it will show the response as below and it will also include your upstream repository from your master project.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480801024%2Fwv6NPQDPH.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480801024%2Fwv6NPQDPH.png" alt="upstream.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  STEP 3: Make your origin repository the same as your upstream repository.
&lt;/h2&gt;

&lt;p&gt;Now we have created upstream branches for our local repository. Now we will match the content from the upstream repository to the local repository.  In this, we will have all the code which is not in our local repository from the upstream repository&lt;/p&gt;

&lt;p&gt;Run the commands as mentioned below.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$ git fetch upstream&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;This command will respond by fetching the content from the upstream for your Master repo. All the new branches and files, contents will the fetched from the upstream repository. And the response for the command as below.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480983405%2F8YXnCNyhE.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609480983405%2F8YXnCNyhE.png" alt="fetchupstream.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Now checkout to your master branch with the command (if not on the master branch)&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$ git checkout master&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;And run the command.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;$ git merge upstream/master&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609484801379%2FTF1Yf_fj5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fcdn.hashnode.com%2Fres%2Fhashnode%2Fimage%2Fupload%2Fv1609484801379%2FTF1Yf_fj5.png" alt="mergemaster.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This will sync all the changes to your local repository if any, Now your local repository is synced with the upstream repository.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;And that's it, If you have any queries let me know in the comments and it would be great if you leave a reaction as well  and follow our community&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>git</category>
      <category>upstream</category>
      <category>branching</category>
    </item>
    <item>
      <title>Connect your firebase Domain to any Custom Domain</title>
      <dc:creator>stephin007</dc:creator>
      <pubDate>Sat, 26 Dec 2020 08:12:25 +0000</pubDate>
      <link>https://dev.to/forcommunity/connect-your-firebase-domain-to-any-custom-domain-493b</link>
      <guid>https://dev.to/forcommunity/connect-your-firebase-domain-to-any-custom-domain-493b</guid>
      <description>&lt;p&gt;Firebase is a free hosting provider, through this you can deploy from simple static HTML to complex e-commerce website made on the latest tech stack.&lt;br&gt;
In this post, we will look into how to connect the firebase domain to the custom domain we bought from domain providers like &lt;strong&gt;Namecheap&lt;/strong&gt;, &lt;strong&gt;Hostinger&lt;/strong&gt;, &lt;strong&gt;Google Domains&lt;/strong&gt;, etc.&lt;/p&gt;

&lt;p&gt;We will add another post on how to deploy any website on firebase, stay tuned :)&lt;/p&gt;

&lt;p&gt;Assuming that you already have hosted your website on firebase, do the following steps:&lt;/p&gt;

&lt;h2&gt;
  
  
  - Add Domain
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Go to your &lt;a href="//console.firebase.com"&gt;firebase console&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Select your project from the list of projects.&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fyc86cfq4ru7an1s5f6ju.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fyc86cfq4ru7an1s5f6ju.png" alt="project list"&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;After you click on the desired project, select the &lt;em&gt;hosting&lt;/em&gt; option from the left panel&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fy490m1ve3jqazs5k3hc6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fy490m1ve3jqazs5k3hc6.png" alt="firebase"&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;CLick on Add custom domain, you will see the following window, add your custom domain name in the text field provided(make sure the spelling is correct)&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fp1nv441759tqqf3fkp0r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fp1nv441759tqqf3fkp0r.png" alt="adcd"&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  -Verify domain ownership
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;In your domain provider's site, locate the DNS management page.&lt;br&gt;
As soon as you click on continue, it will give you TXT value. This TXT value will be used by firebase to verify that you really own this domain.&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fpbjr5u0isufe5ojf8ik0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fpbjr5u0isufe5ojf8ik0.png" alt="connectdoamin"&gt;&lt;/a&gt;.&lt;br&gt;
In your domain provider's site, locate the DNS management page.&lt;br&gt;
Add this TXt value as a DNS record, you will see a bunch of options like A record, AAA record, etc. to add as a record, select TXT and then input&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; Type: TXT&lt;/li&gt;
&lt;li&gt; Value: It must be the value provided by the firebase.&lt;/li&gt;
&lt;li&gt; Host/Name: it should either &lt;code&gt;@&lt;/code&gt; or &lt;code&gt;yourdomainname.com&lt;/code&gt;(generally it's &lt;code&gt;@&lt;/code&gt; - it will already be prefilled)&lt;/li&gt;
&lt;li&gt;TTL Value: Keep it either &lt;code&gt;Automatic&lt;/code&gt; or to &lt;code&gt;3600&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Allow up to 24 hours for the propagation of your updated TXT records, then click Verify.&lt;br&gt;
It probably takes 15-20 mins, the trick is to continue clicking verify for few mins. eventually, it will get verified.&lt;br&gt;
If clicking Verify prompts an error message, your records have not propagated or your values may be incorrect.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  - Go Live
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;After your txt record gets verified, firebase will provide you with 2 A records which you have to add into your DNS Records of your domain provider by default the &lt;em&gt;QUICK SETUP MODE&lt;/em&gt; will be selected which is suitable for new websites.&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fr39x3bo788emfdk8pql1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fr39x3bo788emfdk8pql1.png" alt="arecord"&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Add A new record in your DNS Management Section, just as you added the &lt;code&gt;TXT&lt;/code&gt; record, this time add an &lt;code&gt;A&lt;/code&gt; Record and then input.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; Type: A&lt;/li&gt;
&lt;li&gt; Value: In this, you have to add the IP provided by Firebase, Your domain provider may list this term as "Data", "Points To", "Content", "Address", or "IP Address".&lt;/li&gt;
&lt;li&gt; Host/Name: it should either &lt;code&gt;@&lt;/code&gt; or &lt;code&gt;yourdomainname.com&lt;/code&gt;(generally it's &lt;code&gt;@&lt;/code&gt; - it will already be prefilled)&lt;/li&gt;
&lt;li&gt;TTL Value: Keep it either &lt;code&gt;Automatic&lt;/code&gt; or to &lt;code&gt;3600&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;

&lt;li&gt;&lt;p&gt;Do the above step twice, since firebase provides you with 2 IPs to add to your DNS.&lt;/p&gt;&lt;/li&gt;

&lt;/ul&gt;

&lt;h1&gt;
  
  
  Common domain providers.
&lt;/h1&gt;

&lt;p&gt;Here are some common domain providers and the types of input each might require. This information is kept up-to-date as much as possible, but refer to your domain provider's documentation for detailed instructions.&lt;/p&gt;

&lt;h2&gt;
  
  
  NameCheap
&lt;/h2&gt;

&lt;p&gt;DNS TXT record inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type TXT&lt;/li&gt;
&lt;li&gt;Host/Name    @&lt;/li&gt;
&lt;li&gt;Value verification value provided in Firebase console.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;DNS A records inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A @   151.101.1.195 &lt;/li&gt;
&lt;li&gt;A @   151.101.65.195&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hostinger
&lt;/h2&gt;

&lt;p&gt;DNS TXT record inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type TXT&lt;/li&gt;
&lt;li&gt;Host/Name    @&lt;/li&gt;
&lt;li&gt;Value verification value provided in Firebase console&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;DNS A records inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A @   151.101.1.195&lt;/li&gt;
&lt;li&gt;A @   151.101.65.195&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Note: if in case, your domain gets not connected, it's probably due to an existing &lt;code&gt;A&lt;/code&gt; record in your DNS Records, just delete that then you are good to go but make sure, the firebase A records are not deleted.&lt;/p&gt;

&lt;h2&gt;
  
  
  CloudFare
&lt;/h2&gt;

&lt;p&gt;DNS TXT record inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type TXT&lt;/li&gt;
&lt;li&gt;Host/Name    example.com&lt;/li&gt;
&lt;li&gt;Value verification value provided in Firebase console.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;DNS A records inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A example.com 151.101.1.195&lt;/li&gt;
&lt;li&gt;A example.com 151.101.65.195&lt;/li&gt;
&lt;li&gt;A www 151.101.1.195&lt;/li&gt;
&lt;li&gt;A www 151.101.65.195&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Google Domains
&lt;/h2&gt;

&lt;p&gt;DNS TXT record inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type TXT&lt;/li&gt;
&lt;li&gt;Host/Name    @&lt;/li&gt;
&lt;li&gt;Value verification value provided in Firebase console.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;DNS A records inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A @   151.101.1.195&lt;/li&gt;
&lt;li&gt;A www 151.101.1.195&lt;/li&gt;
&lt;li&gt;A www 151.101.65.195&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Google Cloud DNS
&lt;/h2&gt;

&lt;p&gt;DNS TXT record inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type TXT&lt;/li&gt;
&lt;li&gt;Host/Name    example.com&lt;/li&gt;
&lt;li&gt;Value verification value provided in Firebase console.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;DNS A records inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A example.com 151.101.1.195&lt;/li&gt;
&lt;li&gt;A example.com 151.101.65.195&lt;/li&gt;
&lt;li&gt;A www 151.101.1.195&lt;/li&gt;
&lt;li&gt;A www 151.101.65.195&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Squarespace
&lt;/h2&gt;

&lt;p&gt;DNS TXT record inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Type TXT&lt;/li&gt;
&lt;li&gt;Host/Name    @&lt;/li&gt;
&lt;li&gt;Value verification value provided in Firebase console.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;DNS A records inputs&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A @   151.101.1.195&lt;/li&gt;
&lt;li&gt;A @   151.101.65.195&lt;/li&gt;
&lt;li&gt;A www 151.101.1.195&lt;/li&gt;
&lt;li&gt;A www 151.101.65.195&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That's it for today!&lt;/p&gt;

&lt;p&gt;Hope you liked the post, if you’ve got any questions your can Mail us &lt;code&gt;mail@stephinreji.me&lt;/code&gt; or join our &lt;a href="https://discord.gg/8cjErAy8yA" rel="noopener noreferrer"&gt;Discord-server&lt;/a&gt; and do checkout our website &lt;a href="https://forcommunity.tech" rel="noopener noreferrer"&gt;forcommunity.tech&lt;/a&gt;&lt;/p&gt;

</description>
      <category>firebase</category>
      <category>domain</category>
      <category>customdomain</category>
      <category>hosting</category>
    </item>
    <item>
      <title>Currency Converter Using React JS</title>
      <dc:creator>stephin007</dc:creator>
      <pubDate>Tue, 15 Sep 2020 00:18:05 +0000</pubDate>
      <link>https://dev.to/stephin007/currency-converter-using-react-js-2a7f</link>
      <guid>https://dev.to/stephin007/currency-converter-using-react-js-2a7f</guid>
      <description>&lt;h3&gt;
  
  
  Currency convertor made by using open source Exchange rate API.
&lt;/h3&gt;

&lt;p&gt;It has real time exchange support of upto 33 countries.&lt;/p&gt;

&lt;p&gt;[&lt;strong&gt;Github&lt;/strong&gt;] : &lt;a href="https://github.com/stephin007/currencyconvertor"&gt;https://github.com/stephin007/currencyconvertor&lt;/a&gt;&lt;br&gt;
It would be great if you could 🌟 the repository.&lt;/p&gt;

&lt;p&gt;[&lt;strong&gt;Link&lt;/strong&gt;] : &lt;a href="https://currencyconvertor.stephinreji.me/"&gt;https://currencyconvertor.stephinreji.me/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>javascript</category>
      <category>html</category>
      <category>css</category>
    </item>
  </channel>
</rss>
