<?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>Forem: roshan092</title>
    <description>The latest articles on Forem by roshan092 (@roshan092).</description>
    <link>https://forem.com/roshan092</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%2F81217%2F26d2733f-91f1-46dc-9d47-b9a72015d919.png</url>
      <title>Forem: roshan092</title>
      <link>https://forem.com/roshan092</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/roshan092"/>
    <language>en</language>
    <item>
      <title>Is it just us that is affected by safari 12 ITP</title>
      <dc:creator>roshan092</dc:creator>
      <pubDate>Tue, 09 Oct 2018 13:02:27 +0000</pubDate>
      <link>https://forem.com/roshan092/is-it-just-us-that-is-affected-by-safari-12-itp-297m</link>
      <guid>https://forem.com/roshan092/is-it-just-us-that-is-affected-by-safari-12-itp-297m</guid>
      <description>&lt;p&gt;With the recent safari 12 release, apple has enabled ITP, which essentially is a machine learning system designed to block all tracking cookies. We use a third party Indentity provider to handle our registrations and authentication. This provider uses openid connect, which essentially relies on third party cookies for managing SSO between multiple domains. If in case the authication domain is black listed by ITP, it breaks the entire SSO flow. &lt;/p&gt;

&lt;p&gt;Was wondering if any of the dev s here are affected, and if yes what workarounds were used to mitigate the problem.&lt;/p&gt;

</description>
      <category>safari</category>
      <category>itp</category>
      <category>discuss</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Less for log debugging</title>
      <dc:creator>roshan092</dc:creator>
      <pubDate>Tue, 09 Oct 2018 11:32:24 +0000</pubDate>
      <link>https://forem.com/roshan092/less-for-log-debugging-327o</link>
      <guid>https://forem.com/roshan092/less-for-log-debugging-327o</guid>
      <description>

&lt;p&gt;Today there are a variety of tools like Kibana, splunk, sumo, cloudwatch for aws etc which are tailor mode to solve problems associated with log storage and analysis. With more and more companies moving towards cloud architecture, these tools are becoming increasingly popular. But the harsh reality is that, in majority of workplaces, you will still need to debug logs the old fashioned way - Log into the server and use a tool to search for the exact line. &lt;/p&gt;

&lt;p&gt;I have personally used less to analyse log files. Less does not load the entire file into memory and because log files are normally large, it makes it very efficient. Today after a long time I faced a similar situation and had to brush up myself with less before I could use it. Hence I thought of putting together a blog with the minimum commands required to search log files.&lt;/p&gt;

&lt;p&gt;Ok, Lets get started with the important bits first, entry and exit.&lt;/p&gt;

&lt;p&gt;To open: &lt;code&gt;less &amp;lt;filename&amp;gt;&lt;/code&gt;&lt;br&gt;
To exit: &lt;code&gt;q&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Next use the arrow keys to navigate up and down, if you want to jump pages&lt;br&gt;
To go to the Next page: &lt;code&gt;[Space bar]&lt;/code&gt;&lt;br&gt;
To go to the Previous page: &lt;code&gt;b&lt;/code&gt;&lt;br&gt;
To go to the beginning of the file: &lt;code&gt;g&lt;/code&gt;&lt;br&gt;
To go to the end of the file: &lt;code&gt;G&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;To search for a pattern from the start of the page use:&lt;br&gt;
&lt;code&gt;/pattern&lt;/code&gt;&lt;br&gt;
Next match: &lt;code&gt;n&lt;/code&gt;&lt;br&gt;
Previous match: &lt;code&gt;N&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Once you find your point of interest:&lt;br&gt;
Mark the line: &lt;code&gt;m&lt;/code&gt; followed by any letter&lt;/p&gt;

&lt;p&gt;In case you are lost and want to come back to the mark:&lt;br&gt;
&lt;code&gt;'&amp;lt;the letter&amp;gt;&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;To search for a pattern from the end of the page use:&lt;br&gt;
&lt;code&gt;?pattern&lt;/code&gt;&lt;br&gt;
Next match: &lt;code&gt;n&lt;/code&gt;&lt;br&gt;
Previous match: &lt;code&gt;N&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Since logs are constantly changing use 'r' to repaint the screen&lt;/p&gt;

&lt;p&gt;These basic commands should be enough for most of the cases.&lt;/p&gt;


</description>
      <category>lesslogsdebug</category>
    </item>
    <item>
      <title>My first blog </title>
      <dc:creator>roshan092</dc:creator>
      <pubDate>Tue, 09 Oct 2018 10:15:53 +0000</pubDate>
      <link>https://forem.com/roshan092/my-first-blog--39c9</link>
      <guid>https://forem.com/roshan092/my-first-blog--39c9</guid>
      <description>

&lt;p&gt;As a software developer there is a need to constantly update oneself in order to stay relevant in the industry. In my short career I have explored a variety interesting stuff, and because I like to be absolutely clear of the concepts, spend a lot of time researching multiple sources for the same. The problem is that I am very unorganised and tend to lose track of what I researched (the links, tutorials etc). &lt;/p&gt;

&lt;p&gt;Hence I have decided that whenever I explore something, I will be blogging down my thoughts - everything so that if I decide to use that feature someday in the future, I should be able to get most of the useful information from my blog. I also always wanted to have a technical blog, so I believe this is a good start.&lt;/p&gt;

&lt;p&gt;Giving it a shot, lets see how it goes. Cheers:-)&lt;/p&gt;


</description>
      <category>firstblogroshan</category>
    </item>
  </channel>
</rss>
