<p>Today we're going to deploy a website to the google firebase. Google firebase is free &amp; easy to use. Google firebase provides the free hosting upto 1GB space, if you need more there are some plans provided by firebase. You can use as per your requirements.</p>

<p>Before starting, I assume you already have a google firebase account and a website ready to be host.</p>

<p>let's start hosting a website to google firebase.</p>

<h3>1. Create a Build</h3>

<p>Open cmd prompt in your website folder and run the below command</p>

<pre class="wp-block-code"><code>npm run build</code></pre>

<p>It will create a <strong>build</strong> folder which contains all the website data ready to be host. All website data means html, js, css, images files.</p>
<p><img src="../../../../uploads/1744736389804-create-build-1024x516.png" alt="" width="1024" height="516"></p>

<h3>2. Create Project in Firebase</h3>

<p>Login to your Firebase Console &amp; add a new project. If you have already created a project, just choose that.</p>
<p><img src="../../../../uploads/1744736425550-add-new-project-in-firebase-1024x470.png" alt="" width="1024" height="470"></p>

<h3>3. Open Hosting Page</h3>

<p>You can find a <strong>Hosting</strong> link in the left side menu. Click on it and open the hosting page.</p>
<p><img src="../../../../uploads/1744736456047-here.png" alt="" width="960" height="439"></p>

<h3>4. Set up firebase hosting.</h3>

<p>Open cmd in your project folder and install the Firebase CLI into website.</p>

<h4>1. Install Firebse CLI</h4>

<pre class="wp-block-code"><code>npm install -g firebase-tools</code></pre>

<h3><strong><img src="../../../../uploads/1744736520931-firebase-installation-1024x240.png" alt="" width="1024" height="240"></strong></h3>
<h4><strong>2.&nbsp;</strong>Initialize the Project</h4>

<p>Open a terminal window and navigate to or create a root directory for your web app</p>

<h5>A. Sign in to Google</h5>

<p>It will take you to Google Login page and log you in into the app.</p>

<pre class="wp-block-code"><code>firebase login</code></pre>

<h5>B. Initiate your project</h5>

<pre class="wp-block-code"><code>firebase init</code></pre>

<ul>
<li>Go to hosting by up-down arrow key</li>
<li>Select <strong>Hosting</strong> by clicking the <strong>space</strong> button on keyboard and hit <strong>Enter</strong></li>
<li>It will ask you to select the hosting folder, write <strong><em>build</em></strong></li>
<li>Next <em>Configure as a single-page app</em>, write <strong><em>Y</em></strong></li>
<li>Next <em>Overwrite the index.html, </em>write <strong><em>N</em></strong></li>
<li>Firebase initialisation is complete. Now, deploy the website in next step.</li>
</ul>
<p><img src="../../../../uploads/1744736581454-firebase-initialisation-1024x517.png" alt="" width="1024" height="517"></p>

<h4>3. Deploy to Firebase Hosting</h4>

<p>Run this command from your app&rsquo;s root directory:</p>

<pre class="wp-block-code"><code>firebase deploy</code></pre>

<h3><img src="../../../../uploads/1744736632941-firebase-deployemnt-1024x309.png" alt="" width="1024" height="309"></h3>
<h4>4. Open and run your website.</h4>

<p>After successful deployment, firebase will provide you a <strong>link</strong> and you can use it to see your live website in action.</p>

<p>This link will be a subdomain of google domains. It will be look like <strong>your-project-id.web.app</strong></p>

<p>If you want to add your custom domain to this website, you can follow the link <a href="../../../../blog/google-firebase-custom-domain-subdomain-mapping-with-godaddy">Map custom domain to firebase hosting.</a></p>

<p>Have any questions? Write into the comment section.</p>

Today we're going to deploy a website to the google firebase. Google firebase is free &amp; easy to use. Google firebase provides the free hostin...

How to deploy websites to Google Firebase - TCMHACK

How to deploy websites to Google Firebase

<p>Google is building a new ad-blocker for Chrome that will specifically target ads that use too many system resources.</p>



<p>Chrome is <a rel="noreferrer noopener" aria-label=" (opens in a new tab)" href="https://www.techradar.com/in/news/im-sick-of-chrome-eating-all-my-ram-its-time-for-me-to-ditch-it-for-firefox-or-even-edge" target="_blank">notoriously RAM-hungry</a>, which can result in sluggish performance but the blame doesn't lie entirely with the browser. Sometimes ads can be responsible for sites slowing to a crawl.</p>



<p>As&nbsp;<a href="https://9to5google.com/2019/10/30/heavy-ad-blocker-chrome/" target="_blank" rel="noreferrer noopener">9to5Google</a>&nbsp;explains, Chrome's developers are working on a tool that will address this problem by not loading 'heavy ads' that put excessive demands on the user's device.</p>



<p>The tool was first mentioned in <a rel="noreferrer noopener" href="https://chromium-review.googlesource.com/c/chromium/src/+/1675916" target="_blank">a message from a Chromium developer</a>.  And Google has now <a rel="noreferrer noopener" href="https://github.com/johnivdel/heavy-ad-intervention/blob/master/README.md#proposed-thresholds" target="_blank">published a short guide</a> explaining it further and defining exactly what is meant by 'heavy'.</p>



<p>According to the guide, ads will be blocked if they use the main processor thread for more than 60 seconds in total. Or use the main thread for more than 15 seconds in any 30-second window, or use more than 4MB network bandwidth to load resources. Blocked ads will be replaced with an error message explaining why Chrome has removed it.</p>



<p><a rel="noreferrer noopener" href="https://techdows.com/2019/10/chrome-80-gets-heavy-ad-intervention-feature-in-canary.html" target="_blank">Techdows</a> has also noticed two new flags in <a rel="noreferrer noopener" href="https://www.google.com/chrome/canary/" target="_blank">Chrome Canary</a>.  It's relating to the 'heavy ad' blocker, which you can enable to try the feature now. However, it's worth bearing in mind that the blocker is still at an experimental stage. It isn't likely to appear in the release version of Chrome for several months. It might not work perfectly yet, and Google might choose to adjust its definition of a 'heavy ad' before then.</p>



<h2 id="you-vs-the-advertisers">You vs the advertisers</h2>



<p>Google faces a tricky dilemma with advertising. It makes up the bulk of the company's income but it can spoil the browsing experience for Chrome users. Particularly when it compromises their privacy or affects browsing speeds.</p>



<p>Google has suggested a way to serve targeted ads to users without monitoring their online activity using tracking cookies (a method it calls a '<a rel="noreferrer noopener" aria-label=" (opens in a new tab)" href="https://www.techradar.com/in/news/google-wants-chrome-to-feed-you-targeted-ads-while-somehow-respecting-your-privacy" target="_blank">privacy sandbox</a>'). But moving to such a model would require an overhaul of the whole online advertising industry. If any company has the power to bring that about, it's Google, but such a huge change isn't likely to happen any time soon.</p>



<p>For now, Google appears to have resigned itself to tackling the most obtrusive ads. It seems to be experimenting with a tool that will let users <a rel="noreferrer noopener" aria-label=" (opens in a new tab)" href="https://www.techradar.com/in/news/chrome-is-taking-a-page-out-of-firefoxs-book-and-making-your-privacy-a-priority" target="_blank">block third-party cookies</a>. It's an option that's already enabled by default in rival browsers such as Firefox.</p>



<p>Hopefully this, combined with the 'heavy ad' blocker, will let Google strike a reasonable compromise, improving the experience for its users without putting too large a dent in its ad business.</p>

Google is building a new ad-blocker for Chrome that will specifically target ads that use too many system resources.



Chrome is notoriously RAM...

Chrome is getting a 'heavy ad' blocker to speed up browsing, and you can try it now - TCMHACK

Chrome is getting a 'heavy ad' blocker to speed up browsing, and you can try it now

<p>Google is working on a dark mode for desktop versions of its browsers and its ChromeOS operating system.</p>



<p>For a few months it's been possible to activate a dark mode for Chrome on Android that changes the color of webpages. And according to <a rel="noreferrer noopener" href="https://9to5google.com/2019/07/29/google-chromes-dark-mode-for-the-web-is-coming-to-desktop-and-chrome-os/" target="_blank">9to5Google</a>, that feature will soon become cross-platform.</p>



<p>Currently, it's possible to activate dark mode on Chrome for Android by enabling a 'flag' (an experimental feature) in the browser. This Android-specific flag has now been replaced by one that will work across all platforms.</p>



<h2 id="a-walk-on-the-dark-side">A walk on the dark side</h2>



<p>When Android Q is released (possibly within the next few weeks), it will include&nbsp;<a href="https://www.techradar.com/in/how-to/dark-theme">a system-wide dark theme</a>, which swaps the operating system's default bright white design to something easier on the eyes.</p>



<p>If you've experimented with the dark mode for Android, you may have noticed that it's not quite ready for release yet; some controls are tricky to see with the new colors, and websites are sometimes rendered hard to read where colors are inverted.</p>



<p>With Android Q now imminent, hopefully those issues will be resolved very soon and we'll be able to enjoy browsing the web in dark mode on all our devices.</p>

Google is working on a dark mode for desktop versions of its browsers and its ChromeOS operating system.



For a few months it's been possible t...

Google Chrome for desktop is finally getting a dark mode - TCMHACK

Google Chrome for desktop is finally getting a dark mode

<p>Google Registry has made the .new domain extension available for anyone to use to create custom shortcuts.</p>

<p>Google originally launched the .new extension to be used as shortcuts for its own services. For example, to create a new document or a spreadsheet, you can simply go to .doc or .sheets.</p>

<p>Now, any company can&nbsp;<a href="https://www.registry.google/" target="_blank" rel="noopener">register</a>&nbsp;a .new domain to create similar shortcuts for their own offerings and some companies have already started doing so. Here are some examples that have been created already:</p>

<ul>
<li>Word.new: Create a new document in Microsoft Word</li>
<li>Playlist.new: Create a new Spotify playlist</li>
<li>Sell.new: Create a new product listing on eBay</li>
<li>Link.new: Create a new short link with Bitly</li>
<li>Reservation.new: Make a reservation with OpenTable<br>And others</li>
</ul>

<p>Google notes that, similar to its .app, .page, and .dev extensions, all .new extensions will be served over HTTPS by default.</p>

<p>Registrations of .new domains are available first to trademark owners for a limited time. From December 2, 2019 to January 14, 2020, trademark owners can apply for their trademarked .new domains.</p>

<p>Presumably, all available .new domains will be up for grabs after the limited registration period.</p>

Google Registry has made the .new domain extension available for anyone to use to create custom shortcuts.

Google Lets Anyone Register a .New Domain to Create Custom Shortcuts - TCMHACK

Google Lets Anyone Register a .New Domain to Create Custom Shortcuts

<p>Recently, Google has involved itself in numerous privacy and security changes within Google Chrome. The most important of these was the emphasis on HTTPS for websites. Now, they have announced another strict move in this connection. Google intends to block HTTPS mixed content within their Chrome browser. </p>



<h2>Google To Block Mixed Content</h2>



<p>Reportedly, Google plans to block mixed content for HTTPS in the future. According to a recent <a href="https://security.googleblog.com/2019/10/no-more-mixed-messages-about-https_3.html" target="_blank" rel="noreferrer noopener" aria-label="blog post (opens in a new tab)">blog post</a> by the Chrome Security Team, Google will eventually block mixed content entirely within Chrome. This would ensure full HTTPS implementation only.</p>



<h2>What Is Mixed Content</h2>



<p>As explained separately, ‘<a rel="noreferrer noopener" aria-label="Mixed Content (opens in a new tab)" href="https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content" target="_blank">Mixed Content</a>’ refers to the type of content on websites using HTTPS where certain elements on the web page load over HTTP.</p>



<blockquote class="wp-block-quote"><p>Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS. </p></blockquote>



<h2>How It Affects Browser Security</h2>



<p>Although, Chrome used to notify users about the presence of such content. It couldn’t protect the users from the potential evils of HTTP content on the web page. Thus, the existence of such content downgrades the extent of security as ensured with full HTTPS sites.</p>



<blockquote class="wp-block-quote"><p>Requesting subresources using the insecure HTTP protocol weakens the security of the entire page, as these requests are vulnerable to man-in-the-middle attacks, where an attacker eavesdrops on a network connection and views or modifies the communication between two parties.</p></blockquote>



<p>Eventually, the presence of such content could even allow an adversary to take complete control of the affected page. </p>



<p>Google explained that such content also affects the browser security UX. The browser could neither present it as HTTPS, nor HTTP. </p>



<h2>Implementation To Happen Gradually </h2>



<p>While Google has announced their plans to ensure no mixed content, it will do so in a number of different steps. Consequently, HTTPS websites with mixed content have enough time to modify the affected pages accordingly. </p>



<p>As per the disclosed timeline, initially, Google will roll out settings for users to unblock mixed content on sites. This will take place with Chrome 79 releasing in December 2019. </p>



<p>Then, with Chrome 80, Google will block audio/video resources that fail to load over HTTPS by default. Users would still be able to unblock the content via given settings. However, it will allow the mixed images, where the browser will prompt the site as ‘Not Secure’. </p>



<p>Finally, with Chrome 81 coming in February 2020, Google will block mixed images as well. </p>



<p>For convenience, Google has shared detailed guides for <a rel="noreferrer noopener" aria-label="migrating to HTTPS (opens in a new tab)" href="https://developers.google.com/web/fundamentals/security/encrypt-in-transit/enable-https" target="_blank">migrating to HTTPS</a> and <a href="https://developers.google.com/web/fundamentals/security/prevent-mixed-content/fixing-mixed-content" target="_blank" rel="noreferrer noopener" aria-label="preventing mixed content (opens in a new tab)">preventing mixed content</a> as well.</p>

Recently, Google has involved itself in numerous privacy and security changes within Google Chrome. The most important of these was the emphasis ...

Google Plans To Block Mixed Content With HTTPS On Chrome Browser - TCMHACK

Google Plans To Block Mixed Content With HTTPS On Chrome Browser

<p id="speakable-summary">Over three years after&nbsp;Google&nbsp;&nbsp;<a href="http://www.businessinsider.com/google-just-paid-25-million-to-buy-the-entire-app-web-domain-2015-2" target="_blank" rel="noopener">paid $25 million</a>&nbsp;to gain the exclusive rights to the &ldquo;.app&rdquo; top-level domain, the company is at last making .app domains available to register starting today and running through May 7, at 9 AM PDT via Google&rsquo;s Early Access Program. The following day, May 8, the domains will go on sale for the general public, including through other registrars.</p>
<p>The new top-level domain (TLD) is an obvious choice for app developers and others in the tech industry, as it serves as an easy-to-remember alternative to .com domains &ndash; where inventory has long been running low for popular words. In addition to the expected demand, Google is requiring HTTPS for all. app websites. This built-in security protects against ad malware, tracking injection by internet service providers, and safeguards against spying on open Wi-Fi networks, the company explains. Google has been an advocate of pushing the web towards HTTPS adoption, noting last fall&nbsp;<a href="https://techcrunch.com/2017/10/20/https-is-booming-says-google/" target="_blank" rel="noopener">that 64 percent of traffic through its Chrome browser</a>&nbsp;on Android was protected, up from 42 percent the year before. Chrome traffic on Mac was up to 75 percent, and on Windows up to 66 percent at the same time. The increases were due to a number of actions on Google&rsquo;s part, including its&nbsp;decision&nbsp;to flag all websites using HTTP to transmit private information as &ldquo;insecure.&rdquo; This year,&nbsp;<a href="https://techcrunch.com/2018/02/08/chrome-will-soon-mark-all-unencrypted-pages-as-not-secure/" target="_blank" rel="noopener">Google said it would mark all pages without HTTPS</a>&nbsp;encryption as insecure starting in July with the launch of Chrome 68. Given its plans, it makes sense that Google&rsquo;s new domain addition would also include HTTPS protection built-in. Still, it&rsquo;s something of a milestone, Google notes. &ldquo;Because .app will be the first TLD with enforced security made available for general registration, it&rsquo;s helping move the web to an&nbsp;<a href="https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html" target="_blank" rel="noopener">HTTPS-everywhere future</a>&nbsp;in a big way,&rdquo; the company writes in its&nbsp;<a href="https://www.blog.google/topics/developers/introducing-app-more-secure-home-apps-web/" target="_blank" rel="noopener">announcement</a>&nbsp;of the new TLD. <img class="aligncenter wp-image-71 size-full" src="../../../../uploads/1744909050424-get-app-screenshot.png" alt="" width="1512" height="800"> Prior to the public launch of .app, Google had reached out to potential candidates, offering them a first crack at grabbing a .app domain in order to showcase the potential use cases. Some of those who are already live on .app domains include Outdoor Voices, Cash App, Sitata, Albert, Picnic, Trail, BNEXT, Bark, CallApp, The Podcast App, Pickle, MenaVR and many others from around the world. The company also removed the requirement that limited the domain to app developers, though Google suggests the name makes the most sense in that market. In an&nbsp;<a href="https://domainnamewire.com/2018/03/07/app-domains-are-coming-qa-with-google/" target="_blank" rel="noopener">interview last month with Domain Name Wire</a>, Google said that it aims to make .app domains affordable &ndash; it expects the pricing to be less than its other TLDs like .how or .soy, for example. The site said that would mean wholesale pricing would be around $10-12 and retail registrations would be $20. (Pricing was not detailed in today&rsquo;s announcement, however.) Interested .app domain shoppers can register their domain of choice today through May 7, 2018 starting at 9 AM PDT, if they want to pay the additional fee for early access ahead of the domain&rsquo;s launch to the public through other registrars. More info is on the&nbsp;<a href="https://get.app/" target="_blank" rel="noopener">get.app website</a>.</p>

Over three years after Google  paid $25 million to gain the exclusive rights to the “.app” top-level domain, the company is at last making .app d...

How to deploy websites to Google Firebase

Chrome is getting a 'heavy ad' blocker to speed up browsing, and you can try it now

Google Chrome for desktop is finally getting a dark mode

Google Lets Anyone Register a .New Domain to Create Custom Shortcuts

Google Plans To Block Mixed Content With HTTPS On Chrome Browser

Google is launching .app domains, the first TLDs secured with built-in HTTPS