<?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: naveen sanjula</title>
    <description>The latest articles on DEV Community by naveen sanjula (@naveensanjula).</description>
    <link>https://dev.to/naveensanjula</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%2F859919%2Fc1e644bc-4406-468e-8f82-831bb6844bc2.jpg</url>
      <title>DEV Community: naveen sanjula</title>
      <link>https://dev.to/naveensanjula</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/naveensanjula"/>
    <language>en</language>
    <item>
      <title>Day 1: Linux User Setup with Non Interactive Shell</title>
      <dc:creator>naveen sanjula</dc:creator>
      <pubDate>Tue, 05 Aug 2025 12:36:37 +0000</pubDate>
      <link>https://dev.to/naveensanjula/100-days-of-devops-task-1-965</link>
      <guid>https://dev.to/naveensanjula/100-days-of-devops-task-1-965</guid>
      <description>&lt;p&gt;To create a user named &lt;code&gt;ravi&lt;/code&gt; with a &lt;strong&gt;non-interactive shell&lt;/strong&gt; on &lt;strong&gt;App Server 1&lt;/strong&gt;, follow these steps&lt;/p&gt;




&lt;h3&gt;
  
  
  ✅ Linux CLI
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Access App Server 1&lt;/strong&gt;
If you're managing multiple servers, first connect to App Server 1 via SSH
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   ssh user@stapp01  # Replace `user` with the appropriate username
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Create the user with a non interactive shell&lt;/strong&gt;
Use &lt;code&gt;/sbin/nologin&lt;/code&gt; or &lt;code&gt;/usr/sbin/nologin&lt;/code&gt; (depending on the distro)
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   sudo useradd -s /sbin/nologin ravi
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;-s /sbin/nologin&lt;/code&gt; sets the user's shell to "non interactive" (i.e., login access is disabled).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;ravi&lt;/code&gt; is the username.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;On some systems, the non interactive shell might be located at &lt;code&gt;/usr/sbin/nologin&lt;/code&gt;. Use that if &lt;code&gt;/sbin/nologin&lt;/code&gt; doesn't exist.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Verify the user and shell&lt;/strong&gt;
Run
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   grep ravi /etc/passwd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Expected output&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   ravi:x:1001:1001::/home/ravi:/sbin/nologin
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;








&lt;p&gt;&lt;code&gt;ssh steve@stapp02&lt;/code&gt;&lt;br&gt;
&lt;br&gt;
 (enter the password for steve user)&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;code&gt;sudo -i&lt;/code&gt;&lt;br&gt;
&lt;br&gt;
 (again enter the password for steve user)&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;code&gt;useradd amar -s /sbin/login&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;refer this &lt;a href="https://kodekloudhub.github.io/kodekloud-engineer/docs/projects/nautilus#infrastructure-details" rel="noopener noreferrer"&gt;link&lt;/a&gt; for usernames and passwords for different servers within nautilus.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How can I convert Pine Script to MQL4?</title>
      <dc:creator>naveen sanjula</dc:creator>
      <pubDate>Thu, 23 Feb 2023 17:42:03 +0000</pubDate>
      <link>https://dev.to/naveensanjula/how-can-i-convert-pine-script-to-mql4-1am7</link>
      <guid>https://dev.to/naveensanjula/how-can-i-convert-pine-script-to-mql4-1am7</guid>
      <description>&lt;p&gt;Pine Script and MQL4 are both programming languages used in financial trading. Pine Script is the programming language used for trading view while MQL4 is used in MetaTrader 4 platform. Sometimes, traders may have to switch between these two programming languages for their trading needs. This can be due to various reasons like the need to use a specific indicator or strategy that is only available in one platform. In such cases, it becomes important to know how to convert Pine Script to MQL4 or vice versa. In this article, we will discuss how to convert Pine Script to MQL4.&lt;/p&gt;

&lt;p&gt;Step-by-step guide to converting Pine Script to MQL4:&lt;/p&gt;

&lt;p&gt;1.Understand the Differences between Pine Script and MQL4:&lt;br&gt;
Before converting Pine Script to MQL4, it is important to understand the differences between these two programming languages. Pine Script is a relatively simple language and is used for developing scripts for TradingView. MQL4, on the other hand, is a more complex language and is used for developing Expert Advisors (EAs) and indicators for MetaTrader 4. MQL4 has a vast library of functions and features that are not available in Pine Script.&lt;/p&gt;

&lt;p&gt;2.Analyze the Pine Script Code:&lt;br&gt;
The first step in converting Pine Script to MQL4 is to analyze the Pine Script code. This involves understanding the logic and the purpose of the code. It is important to know what the code does and what its output is supposed to be. Once the code is understood, it becomes easier to convert it to MQL4.&lt;/p&gt;

&lt;p&gt;3.Translate Pine Script to MQL4:&lt;br&gt;
The next step is to translate the Pine Script code to MQL4. This involves replacing the Pine Script functions and features with their equivalent MQL4 functions and features. It is important to ensure that the syntax and logic of the code remain the same. This can be a tedious process, especially if the Pine Script code is complex.&lt;/p&gt;

&lt;p&gt;4.Test the MQL4 Code:&lt;br&gt;
After translating the Pine Script code to MQL4, it is important to test the MQL4 code. This involves compiling and running the MQL4 code in the MetaTrader 4 platform. The purpose of testing is to ensure that the MQL4 code produces the same output as the Pine Script code. Testing can also help to identify any errors or bugs in the code.&lt;/p&gt;

&lt;p&gt;5.Debug and Optimize the MQL4 Code:&lt;br&gt;
Once the MQL4 code has been tested and any errors have been identified, it is important to debug and optimize the code. This involves fixing any errors and optimizing the code for better performance. It is important to ensure that the code runs smoothly and efficiently.&lt;/p&gt;

&lt;p&gt;6.Final Testing and Deployment:&lt;br&gt;
The final step is to perform a final test of the MQL4 code and deploy it in the MetaTrader 4 platform. This involves running the code in a live trading environment to ensure that it works as expected. It is important to monitor the code and make any necessary adjustments to ensure that it continues to work properly.&lt;/p&gt;

</description>
      <category>pinescript</category>
      <category>mql</category>
    </item>
  </channel>
</rss>
