<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by M. Rehnert on Medium]]></title>
        <description><![CDATA[Stories by M. Rehnert on Medium]]></description>
        <link>https://medium.com/@cde13?source=rss-bd08e23926d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jFDkdZ1-W7ds0yVDtG1_MQ.jpeg</url>
            <title>Stories by M. Rehnert on Medium</title>
            <link>https://medium.com/@cde13?source=rss-bd08e23926d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:41:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cde13/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Six Useful Tips to Help ID Spam/Phishing Emails]]></title>
            <link>https://cde13.medium.com/six-useful-tips-to-help-id-spam-phishing-emails-f7424e6b4fd6?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7424e6b4fd6</guid>
            <category><![CDATA[spam]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[phishing]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Tue, 05 May 2026 14:20:03 GMT</pubDate>
            <atom:updated>2026-05-05T14:53:05.062Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ever gotten an email from a reputable company like Apple, Verizon, or Coinbase, but something feels a bit off about it?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WeDuXX_wwoj-2l0sMVxjkA.jpeg" /><figcaption>“@theRealAppleMusic”, adapted from “<a href="https://lirp.cdn-website.com/7825253e/dms3rep/multi/opt/UnKnown+Caller-1920w.jpg">UnKnown Caller</a>” by <a href="https://www.acdtn.com/contact#AboutUsPicanchor">Rick Patin</a>, used under <a href="http://creativecommons.org/licenses/by/4.0">CC BY 4.0</a>. “@theRealAppleMusic” is licensed under <a href="http://creativecommons.org/licenses/by/4.0">CC BY 4.0</a> by M. Rehnert.</figcaption></figure><p>Most of us are aware, to some extent, of the danger posed by suspicious emails. But if your inbox is like mine, with 20–30 new emails arriving daily, finding enough time to skim them can be overwhelming, much less tell which ones are suspect. Seems absurd, right?</p><h3>How to ID Spam/Phishing Email?</h3><p>Maybe, like I once did, you naïvely assume bad emails all magically end up in the Junk/Spam folder. But can we really trust our spam filter to catch ’em all? (<a href="https://scifi.stackexchange.com/q/137864">even Ash didn’t pull that one off</a>) Perhaps try the latest freemium plugin instead? As if any of us can even afford that after rent and bills, right? Not to worry, today I will walk you through an analysis of a real-life malicious email so you can learn to spot suspicious emails on your own! We will focus on two main areas: the preview and the message body.</p><h4>Check the Preview</h4><p>Ironically, I received an email earlier today that managed to bypass my spam filter, security add-ons, and custom rules and somehow landed in my Focused Inbox (the equivalent of ‘Important’ in Gmail). But as soon as I glanced at the preview, red flags started to pop up, including sloppy font styling, a vague subject line, and a deadline in mere hours. Let’s take a look.</p><figure><img alt="A preview of a suspected phishing email with three distinct red flags: 1) Inconsistent font size and weight. 2) Vague wording in the subject line. 3) Same-day deadline to force action." src="https://cdn-images-1.medium.com/max/800/1*tEFl4xcpJJODCeKlUM60wQ.jpeg" /><figcaption>Photo by <a href="https://medium.com/@cde13">M.Rehnert</a> on Medium</figcaption></figure><p>From this image, we learn the first three of our six useful tips to help ID spam/phishing emails: <br>1. Inconsistent use of font or styling.<br>2. Vague wording, especially in the subject line.<br>3. A sense of urgency, focusing on impending deadlines or dire warnings.</p><p>At this point, we already have sufficient circumstantial evidence to justify deleting the email without even opening it. <strong>Report the email as junk so that anything from that sender will be filtered automatically; then, delete it to avoid accidentally clicking on it later. </strong>Why waste time entertaining spam or potential malware?</p><h4>Check the Message Body</h4><p>Now let’s assume, for the sake of argument, that we decide to open the email, just to be sure before canning it. Can we expect to see any new red flags, or only some variation of the ones we covered previously? Let&#39;s see.</p><figure><img alt="The main body of a suspected phishing email with three additional red flags: 4) Fear of missing out (FOMO). 5) Apple Music icon color faded/edges blurred. 6) Wrong company, address, contact info." src="https://cdn-images-1.medium.com/max/800/1*pLUrAicWe7R0BrLjPKIs2A.jpeg" /><figcaption>Photo by <a href="https://medium.com/@cde13">M.Rehnert</a> on Medium</figcaption></figure><p>Thanks to this image, we discover the remaining three of our six useful tips to help ID spam/phishing emails: <br>4. Fear of missing out. (or any effort to provoke an emotion-based decision) 5. A faded, blurry, or discolored icon. <br>6. Incorrect company details like legal name, address, or contact info.</p><p>After the FOMO pitch, the fake Apple Music icon, and the wildly inaccurate company details in the footer, I was positive that Apple did not send this email. A reputable company would never be so sloppy.</p><h3>Why Bother to ID Spam/Phishing Email?</h3><p>It is easy to forget the true nature of what we are up against. Suspicious emails are way more than annoying digital garbage cluttering up our inboxes. One wrong click is all it takes to escalate into a very serious situation. What if, half-awake or intoxicated, I had instead chosen to <em>Renew my subscription</em>? Suddenly, I became curious about the demise someone evidently had in mind for me.</p><blockquote>Disclaimer: Never intentionally interact with suspected spam or malicious content unless you understand the risks and have a valid reason for doing so.</blockquote><p>Using extreme caution to avoid actually clicking the link, I combed through the original message using source view, located the embedded URL, and submitted it to <a href="https://www.virustotal.com/gui/url/de3d5e9726eb4f433e8565bd4cdf9d9d0b340efcfbdb243f01a627322c22a323/details">VirusTotal</a> for analysis.</p><h4>Malicious Intent</h4><p>The verdict was returned in under a minute, with vendor flags thrown for malicious content and phishing.</p><figure><img alt="A VirusTotal report shows two cybersecurity providers flagging the URL as malicious or phishing." src="https://cdn-images-1.medium.com/max/800/1*g5gg8elOEo3dzo0xG6PKBQ.jpeg" /><figcaption>Photo by <a href="https://medium.com/@cde13">M.Rehnert</a> on Medium</figcaption></figure><p>We see that two hits are returned, labeling the URL as phishing and malicious and confirming our suspicions that the email is spammy at best or, worse, blatantly malicious.</p><h4>Hostile Takeovers</h4><p>Digging deeper into the analysis, we can better understand what happens after the embedded link is clicked.</p><figure><img alt="A VirusTotal report detailing the malware behavior to include dropping the list of trusted root certificates and disallowed certificates." src="https://cdn-images-1.medium.com/max/800/1*Z6lG-Unad6NzOfg9WxAvIA.jpeg" /><figcaption>Photo by <a href="https://medium.com/@cde13">M.Rehnert</a> on Medium</figcaption></figure><p>Behind the scenes, chaos quietly ensues as the malware deletes trusted/disallowed certificate lists on the victim’s computer, limiting secure authentication and leaving a foothold for further exploits.</p><h4>Global Threat Actors</h4><p>One last noteworthy item is the actual destination of the link from the email. Check it out.</p><figure><img alt="A VirusTotal report showing the final URL resolving to a domain owned by an Indian company that makes industrial ball bearings in Chinese factories." src="https://cdn-images-1.medium.com/max/676/1*YnBpgbZ3YSee2r56es1IGA.png" /><figcaption>Photo by <a href="https://medium.com/@cde13">M.Rehnert</a> on Medium</figcaption></figure><p>Far removed from any domain associated with Apple, it rather belongs to a ball-bearing manufacturer in India. Clearly, the rabbit hole goes very deep, far beyond even my expectations. Okay, on that note, let’s recap.</p><h3>Summary</h3><p>So the next time those unread emails start piling up, apply what we learned today. Scan the previews, look for red flags, and deal with any obvious spam first.</p><h4>In the Preview</h4><p><em>🚩 — Visible changes in font size and thickness<br>🚩 — Unclear or vague origin and subject line<br>🚩 — Deadline in a few hours to trigger a rushed response</em></p><p>If the email seems legit, the next step is to open it and read it, staying on guard for anything suspicious.</p><h4>In the Message Body</h4><p><em>🚩 — Fear of Missing Out (FOMO) or a similar emotional grab.<br>🚩 — Icons or logos that appear fuzzy, modified, or discolored.<br>🚩 — Wrong company name, address, or contact info</em></p><p>Most importantly, <strong>do not click on any links</strong>! Always trust but verify. <br>With the exception of security emails, such as those you get when registering a new account, always use the official website or app to log in directly, not an email link. Once you know the email is real, you can focus on handling any business related to its content.</p><p>In other words, at the risk of sounding cliché, better to be safe than sorry!</p><p>— killshot13</p><p>Don’t forget to 👏 this article and leave a 💭; I look forward to reading your thoughts and opinions in the comments below.</p><p>If you’re feeling generous or want to read more, please🎆(<a href="https://sth13.medium.com/">follow me</a>)🎇on Medium and check out some of my other popular articles!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7424e6b4fd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 50,000px Rule:]]></title>
            <link>https://cde13.medium.com/the-50000px-rule-minimum-sizing-for-high-resolution-web-images-760a2858dafa?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/760a2858dafa</guid>
            <category><![CDATA[high-resolution-images]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[web-images]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Wed, 24 Aug 2022 08:22:57 GMT</pubDate>
            <atom:updated>2025-11-06T09:09:16.972Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>The 50,000px Rule: or, Minimum Sizing for High-Resolution Web Images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ES3Trvi3IhbN_QukjFICJA.jpeg" /><figcaption>Image comparison is shown first at 300dpi and then at only 72dpi.</figcaption></figure><h4>Introduction</h4><p>Like most other days in any given month, I learned something new today. However, this tidbit of knowledge was particularly intriguing and, in my experience, not something well-known among web developers and SEO experts.</p><p>So I thought to myself, on the off chance that I haven’t been living under a rock this time, why not pen a short piece and spread the word?</p><p>Hopefully, by now, I’ve piqued your curiosity a bit. So without further ado, let’s explore what I have christened the 50,000px Rule.</p><h3>High-Level Overview</h3><p>I recently learned this information while completing a <a href="https://codelabs.developers.google.com/">Google Codelab</a> on JSON-LD structured data. Although somewhat off-topic from my objective, some of the related verbiage caught my attention. Let’s have a look!</p><blockquote>“For best results, provide multiple high-resolution images (minimum of 50K pixels when multiplying width and height) with the following aspect ratios: 16x9, 4x3, and 1x1.”<em> —</em><a href="https://developers.google.com/search/docs/advanced/structured-data/recipe"><em> Google Search Central</em></a></blockquote><p>What Google is trying to say here is this. If this expression doesn’t return true after plugging in the dimensions of your photos, then your site isn’t serving high-resolution images correctly.</p><pre>&lt;div&gt;<br>&lt;link rel=”stylesheet” href=”<a href="https://cdn.jsdelivr.net/npm/katex@0.13.13/dist/katex.min.css">https://cdn.jsdelivr.net/npm/katex@0.13.13/dist/katex.min.css</a>&quot;&gt;<br> &lt;span&gt;imgW * imgL &gt;= sqrt(50,000)&lt;/span&gt;<br>&lt;/div&gt;</pre><p>Let’s simplify the math just a tad. We know that (2 x 2)= 4, so let’s assign these values to a simple square. Using the formula for a given square area, we can determine that a 2 in. x 2 in. square has a surface area of…surprise! Four square inches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZMXKTq72K56YkdN-T2nGw.jpeg" /><figcaption>“Oh no, not math!” exclaimed the startled cat.</figcaption></figure><p>Now we must remember that this calculation does not change based on the unit of measure. If we instead had a 2-foot square or a 2-cm square, the unit of measurement in use wouldn’t alter the numerical values.</p><p>So then, is a pixel also a unit of measure? Of course! Pixels, abbreviated as “px,” are tiny units of measure; one pixel is about 1⁄96 inch (0.26 mm).</p><p>While small, these specks do play an essential role in web design. Pixels are used to ensure that a given element will render correctly, regardless of the screen resolution used for viewing.</p><h3>Practical Application</h3><p>Returning to the 50,000px Rule, the concept seems much simpler now. To meet the minimum requirements for a high-resolution image, a photograph must have a square area of at least 50K pixels.</p><blockquote><strong>“For an image to be considered high-resolution when served on the Web, it must satisfy the 50,000px Rule.”</strong></blockquote><p>Let’s calculate what this means using three aspect ratios widely recommended as variants of any image we might serve on a webpage.</p><h4>1:1 — the basic square or thumbnail image</h4><p>We should be familiar by now with this type of calculation. After taking the square root of 50,000, we discover the minimum size for a high-resolution photo with a 1:1 ratio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*hCYmruQQQupryHhi5lFr_w.png" /><figcaption>1:1 aspect ratio</figcaption></figure><h4>4:3 — the nostalgic “<a href="https://nofilmschool.com/2018/10/creative-weight-43-aspect-ratio">Academy ratio</a>” used in older films</h4><p>Once the shape changes from a square to a rectangle, the calculation process becomes less granular and involves ratios and fractions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/260/1*dRuZ4LCDyPQgOpBPzaHLEw.png" /><figcaption>4:3 aspect ratio</figcaption></figure><h4>16:9 — the current “widescreen” cinematic standard</h4><p>As you might assume, the larger the base ratio, the larger the gap between 50,000 and the actual size of our image. With a 16:9 aspect ratio, we cannot go lower than 51,984 square pixels without using decimal numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*TSCj_-aiGwMhHDQcvYGfMA.png" /><figcaption>16:9 aspect ratio</figcaption></figure><h4>Conclusion</h4><p>So, there you have it, folks —the 50,000px Rule demystified. I do not anticipate that any developer, including myself, will need to reference this information very often.</p><p>Still, it was fun to research and set a concrete baseline for high-resolution imagery. I hope you enjoyed reading this article and perhaps learned something new today!</p><p>Here’s to hoping you found these tidbits interesting. Either way, you spent valuable time out of your day to follow along, something I genuinely appreciate. Thank you!</p><p>Don’t forget to 👏 this article and leave a 💭; I look forward to reading your thoughts and opinions in the comments below. If you’re feeling extra generous, please click the link to 🎆<a href="https://sth13.medium.com/">follow me</a> on Medium!🎇</p><p>— killshot13</p><p>Still feel like reading? Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out some of my other popular articles!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=760a2858dafa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Medium Lifehack: [CRTL-ALT-6] Code Blocks]]></title>
            <link>https://cde13.medium.com/life-hack-keyboard-shortcut-for-code-blocks-a4669aa5a1ae?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4669aa5a1ae</guid>
            <category><![CDATA[technology-writing]]></category>
            <category><![CDATA[lifehacks]]></category>
            <category><![CDATA[editing-tips]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[code-block]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Tue, 02 Nov 2021 04:43:48 GMT</pubDate>
            <atom:updated>2025-11-06T09:12:37.852Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dn_L_w5Tkh06J46QPZM4Vg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@dancounsell?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dan Counsell</a> on <a href="https://unsplash.com/s/photos/keyboard-shortcut?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>The keyboard shortcut you never knew you needed!</h4><p>Okay, this will be a very brief article, as most of you braniacs likely already know about this trick. And besides, there is no reason to belabor the point over such a simple tidbit of knowledge.</p><blockquote><strong>If you are a Medium author who sometimes shares code snippets because you write about technology and coding, then check out this lifehack.</strong></blockquote><blockquote><strong>[ CTRL &gt; ALT &gt; 6 ] .</strong></blockquote><p>This handy keybinding is enabled by default in the Medium editor and allows you to create code blocks instantly. Check it out! All you have to do first is highlight the relevant text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sq8cN0tdrpmPmiPPymgzTw.gif" /><figcaption>Here is <a href="https://raw.githubusercontent.com/killshot13/verbose-octo-memory/main/Medium-Lifehack-CTRL-ALT-6.gif">an alternate link</a> because GIFs sometimes break on the Medium app.</figcaption></figure><p>See? The keyboard shortcut works like a charm. For reference, here is the actual code block shown in the above GIF!</p><pre>sudo apt-get update -y</pre><pre>router.get(‘/’, (req, res, next) =&gt; {<br>    res.status(200).json({ msg: ‘Working’ })<br>})</pre><p>As you can see, custom indents are also permitted here to support preformatted code snippets, unlike in the default editor, which allows only a single space.</p><h4>PLEASE NOTE:</h4><p>Since I don’t have a MacBook, I cannot confirm whether [Command &gt; Option &gt; 6] is a functional equivalent for macOS. I would give it a shot, though, and if that is correct, please let me know so I can update the article.</p><p>And that’s all for today, folks. Thank you for reading, and I hope this helped make life a little easier for some of you. Also, be sure to 📣 any Medium life hacks you have discovered in the comments below so that we can work smarter rather than harder!</p><p>— killshot13</p><p>If you found this article helpful or interesting, please 👏 and share it! <br>Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out my most popular articles below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4669aa5a1ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pure CSS Blockquotes]]></title>
            <link>https://cde13.medium.com/pure-css-angled-blockquotes-9da6da0c788a?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9da6da0c788a</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[blockquote]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Tue, 02 Nov 2021 02:19:16 GMT</pubDate>
            <atom:updated>2022-08-24T05:30:46.127Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGNjuNo-bD4X37r4gkyHTw.png" /><figcaption>As Seen on CodePen</figcaption></figure><h4>“It’s all about the angles!”</h4><h3>Overview:</h3><p>Developed using only CSS and HTML, these blockquotes offer an excellent way to show off your site&#39;s accent color(s) without much extra work.</p><p>By using the natural breakpoints in the border and changing the width of the &quot;negative space,&quot; I was able to create two nice, angled versions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fkillshot13%2Fembed%2Fpreview%2FMWJeOwE%3Fdefault-tabs%3Dcss%252Cresult%26height%3D600%26host%3Dhttps%253A%252F%252Fcodepen.io%26slug-hash%3DMWJeOwE&amp;display_name=CodePen&amp;url=https%3A%2F%2Fcodepen.io%2Fkillshot13%2Fpen%2FMWJeOwE&amp;image=https%3A%2F%2Fassets.codepen.io%2F4515601%2Finternal%2Fscreenshots%2Fpens%2FMWJeOwE.default.png%3Ffit%3Dcover%26amp%3Bformat%3Dauto%26amp%3Bha%3Dfalse%26amp%3Bheight%3D360%26amp%3Bquality%3D75%26amp%3Bv%3D2%26amp%3Bversion%3D1620420571%26amp%3Bwidth%3D640&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/de9e7c329ceae1fdaeaa8fb78b72831c/href">https://medium.com/media/de9e7c329ceae1fdaeaa8fb78b72831c/href</a></iframe><h3>But How?</h3><p>This is made possible by giving border-bottom and border-top the same color as background-color, By invisibly overlapping these two, we can quite handily achieve this creating a simulated angle that would otherwise be hard to accomplish on such a narrow width.</p><p>I&#39;m sure I cannot be the only one to have thought of this idea, but I have not yet come across it elsewhere, so I am pretty proud to at least be able to take credit for this version of the concept.</p><h3>Usage</h3><p>Of course, anyone is free to use the design or find a way to improve upon it. Just put a link back in the comments, please! The <a href="https://codepen.io/killshot13/pen/MWJeOwE">original code</a> is available on <a href="https://codepen.io/">CodePen</a>, and I have open-sourced it under the MIT License so anyone can modify and reuse it as they please. Happy Blockquoting!</p><p>Thank you for reading my article; I genuinely hope you enjoyed it. Please don&#39;t forget to 👏 and share this article or post a 📣 down below. Until next time!</p><p>— killshot13</p><p>If you found this article useful or interesting, please 👏 and share it! <br>Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out my most popular articles below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9da6da0c788a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Pandoc?]]></title>
            <link>https://cde13.medium.com/what-is-pandoc-302dc35c3ba0?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/302dc35c3ba0</guid>
            <category><![CDATA[markdown]]></category>
            <category><![CDATA[file-conversion]]></category>
            <category><![CDATA[pandoc]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Sat, 15 May 2021 17:49:07 GMT</pubDate>
            <atom:updated>2022-08-24T05:34:37.291Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*HoR-BVTRaSJSBOS1RoLZcQ.png" /><figcaption>Image Credit: <a href="https://groups.google.com/g/pandoc-discuss/c/1bKIuyBnWaQ/discussion"><strong>RFC: Designing Logo of Pandoc</strong></a></figcaption></figure><p>An Introduction to Document Conversion from the Command Line</p><h4>Introduction</h4><p>Most developers have probably wondered or even asked the question at some point, “What exactly is <a href="http://pandoc.org/installing.html">Pandoc</a>?&quot; or “What do people use Pandoc for?”</p><p>I certainly did! So, I have written a short article to help answer that question. Much of the information in this article is sourced from <a href="https://gist.github.com/killshot13/5b379355d275e79a5cb1f03c841c7d53">a gist I had put together</a> over several months.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/da8bc138e140a41aa78ec00e9b8d3e41/href">https://medium.com/media/da8bc138e140a41aa78ec00e9b8d3e41/href</a></iframe><p>Defined as a universal <a href="https://en.wikipedia.org/w/index.php?title=Pandoc&amp;oldid=1018572588">document converter</a>, Pandoc is an open-source software program for file conversion. Pandoc is not a markup language, nor is it a CLI, although it is used from one. 🙃</p><p>If you need to convert files from any conceivable format to another, Pandoc is your best friend. It has become popular across multiple industry and technology sectors.</p><p>The value of Pandoc shines brightest when used to transform file types like Markdown, Microsoft Word (.docx), and XML into more user-friendly documents and markup languages, including PDF and HTML.</p><h3>Installing Pandoc</h3><p>I will assume at this point, if you are still reading, you likely want to try Pandoc out for yourself.</p><p>Listed below are the steps I took to install and configure Pandoc on Windows (10 Pro Edition) and Linux (Ubuntu 20.04 Focal) for Markdown to PDF document conversion.</p><p>Please note all disclaimers remain flapping in the breeze. Pandoc is open-source software that <a href="https://pandoc.org/MANUAL.html#authors">carries no warranty of any kind</a>, and likewise, I make no guarantee that you will achieve a favorable result simply by following the steps below. 🙃</p><blockquote>Your Mileage Might Vary</blockquote><h4>→ Pandoc on Windows</h4><p>I have been using the <a href="https://community.chocolatey.org/">Chocolately</a> package manager for Windows for several years now. So for me, the simplest way to get Pandoc up and running was first to install it with this command.</p><pre>choco install pandoc</pre><p>Then I grabbed the Windows installer for MikTex (one of many Pandoc engines) from the <a href="https://miktex.org/download">official download page</a> and ran the .exe file to install.</p><figure><img alt="Before-and-after view when running the markdown-to-pdf command in Pandoc" src="https://cdn-images-1.medium.com/max/1024/1*MnlbGyL_LRiMtLctIHPO9w.jpeg" /><figcaption>Before-and-after view when running the markdown-to-pdf command in Pandoc</figcaption></figure><p>No further configuration was necessary, at least not from a functional point of view. However, Pandoc will let you customize certain behaviors at quite a granular level.</p><p>At the end of this article, there is a configuration section that offers a good starting place for those wishing to take a deeper dive.</p><h4>→ Pandoc on Linux</h4><p>Getting Pandoc setup with PDF capabilities on Linux proved a bit more challenging.</p><p>After navigating a good deal of noise encountered while researching different packages, I found <a href="https://askubuntu.com/a/1219144/1153800">the consensus</a> seemed to favor a Pandoc/TexLive setup.</p><p>Since I am running Ubuntu Linux on WSL2, I opted to build from scratch to avoid conflicts with my local Windows environment.</p><figure><img alt="Before-and-after view when running the markdown-to-HTML command in Pandoc" src="https://cdn-images-1.medium.com/max/1024/1*9_NuR-SjcsgQAc3T7sljEQ.jpeg" /><figcaption>Before-and-after view when running the markdown-to-HTML command in Pandoc</figcaption></figure><p>First, I pulled the latest tarball from the <a href="https://github.com/jgm/pandoc/releases/">release page</a>.</p><blockquote>There are multiple assets available with each release, so check your OS architecture first rather than blindly copying the snippets. This way you can ensure you are requesting the correct package for your machine.</blockquote><pre>wget <a href="https://github.com/jgm/pandoc/releases/download/2.13/pandoc-2.13-linux-amd64.tar.gz">https://github.com/jgm/pandoc/releases/download/2.13/pandoc-2.13-linux-amd64.tar.gz</a></pre><p>Then, without switching directories, I used a two-step installation process.</p><pre>sudo tar xvzf $TGZ --strip-components 1 -C ‘/usr/local’</pre><p>Note that $TGZ and the destination folder in the snippet above are generic, and substitutions must be made to reflect your home directory.</p><pre>sudo apt-get install texlive texlive-latex-extra</pre><p>And with that, Pandoc was installed on Linux with the ability to convert markdown files to PDF documents!</p><h3>Configuring Pandoc</h3><p>These configuration options are just examples and may not apply in every situation.</p><blockquote>One should always consult the <a href="https://pandoc.org/MANUAL.html">official Pandoc documentation</a> for complete details and the latest changes.</blockquote><pre>--pdf-engine=PROGRAM</pre><ul><li>Specifies which engine Pandoc should use when producing PDF output.</li><li>Valid values are pdflatex, lualatex, xelatex, latexmk, tectonic, wkhtmltopdf, weasyprint, prince, context, and pdfroff.</li><li>If the engine is not in your PATH, you can specify the full path of the engine here.</li><li>If this option is not specified, pandoc uses the following defaults depending on the output format specified.</li></ul><h4>Examples:</h4><pre>-t latex or none</pre><ul><li>defaults to pdflatex (other options: xelatex, lualatex, tectonic, latexmk)</li></ul><pre>-t context</pre><ul><li>defaults to context</li></ul><pre>-t html</pre><ul><li>defaults to wkhtmltopdf (other options: prince and weasyprint; visit <a href="https://print-css.rocks/">Print-CSS</a> for a good introduction to PDF generation from HTML/CSS.)</li></ul><pre>-t ms:</pre><ul><li>defaults to pdfroff</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6T2Ov7Fn_ovUfeVeIp4gQ.jpeg" /><figcaption>Pandoc can even apply custom styling when rendering HTML from Markdown</figcaption></figure><pre>--pdf-engine-opt=STRING</pre><ul><li>Use the given string as a command-line argument to the PDF engine.</li><li>For example, to use a persistent directory foo for <a href="https://ctan.org/pkg/latexmk/">Latexmk</a>’s additional files, use:</li></ul><pre>--pdf-engine-opt=-outdir=foo</pre><ul><li>Note that no check for duplicate options is done.</li></ul><blockquote>Credit for Examples: <a href="https://pandoc.org/MANUAL.html">Pandoc User’s Guide</a></blockquote><h4>Conclusion</h4><p>On a related note, if you find yourself working with markdown, HTML, PDF, or XML files quite often, you should check out a little project of mine called mdEditor for VS Code.</p><p>The frameworks installed by mdEditor automate the configurations we just covered in such detail. Now you can generate file conversion with a simple keybinding or click in the command palette!</p><p><a href="https://github.com/killshot13/mdEditor">killshot13/mdEditor</a></p><p>I hope you have found this tutorial useful, and thank you for taking the time to follow along!</p><p>Don’t forget to 👏 this article and leave a 💭. If you’re feeling extra generous, please click the link to 🎆<a href="https://sth13.medium.com/">follow me</a> on Medium!🎇</p><p>— killshot13</p><p>Still feel like reading? Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out some of my other popular articles!</p><h4>A Note on Pandoc</h4><blockquote>Copyright 2006–2021 <a href="/service/mailto:jgm@berkeley.edu">John MacFarlane</a>. Released under the <a href="https://www.gnu.org/copyleft/gpl.html">GPL</a>, version 2 or greater. This software carries no warranty of any kind. (See COPYRIGHT for full copyright and warranty notices.) For a full list of contributors, see the file AUTHORS.md in the <a href="https://github.com/jgm/pandoc">Pandoc source code</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=302dc35c3ba0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Build an SMTP Mail Server with Express, Node, and Gmail]]></title>
            <link>https://medium.com/code-develop-engineer/build-an-smtp-mail-server-with-express-node-and-gmail-7e58ee84de52?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e58ee84de52</guid>
            <category><![CDATA[smtp-server]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[javascript-development]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 00:00:00 GMT</pubDate>
            <atom:updated>2022-08-24T05:36:20.701Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*_-ElM-rKswTrYdnp.jpg" /></figure><h3>Overview</h3><p>Recently I had the opportunity to develop and integrate an SMTP Email Server into a more extensive full-stack application. Today we will reference the code from my solution for this tutorial.</p><p>We’ll primarily be using Express and Node to create this server. We’ll also integrate Nodemailer to construct a mailable object and Gmail SMTP Server to deliver our emails free of charge.</p><p>The full codebase can be viewed here:</p><p><a href="https://github.com/killshot13/express-smtp-mailer">killshot13/express-smtp-mailer</a></p><h3>Features</h3><p>Before we start coding, we should quantify the expected functionality of our Express mail server. We can always refer back to this list later if confusion develops.</p><ol><li><em>Establish API routes</em> to a contact form on the frontend.</li><li><em>Receive user data</em> from these routes upon form submission.</li><li><em>Format a mailable JSON object</em> with the data received.</li><li><em>Construct a transport function</em> with Nodemailer in preparation for delivery.</li><li><em>Obtain authorization</em> from Gmail using credentials stored in the server.</li><li><em>Call the transport function</em>, prompting Nodemailer to handoff the email object to the Gmail SMTP Server for delivery.</li><li><em>Request confirmation</em> of successful delivery and return an error message if not received.</li></ol><p>Upon completion, we will have the perfect backend for processing contact forms. Alternatively, our server will also provide a solid base to build a full-stack MERN app with plenty of functionality.</p><p>The production version of the server we are building today powers the backend of <a href="https://ormica.com/">Ormica</a>, a real estate investment firm in S. Florida.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p3Mug-bmKW2M5Fjl5ZpPPA.jpeg" /></figure><h3>Prerequisites</h3><ul><li>A basic understanding of fundamental programming concepts and familiarity with at least one server-side programming language such as [ Node, Python, Ruby, PHP].</li><li>A code editor such as <a href="https://code.visualstudio.com/">Visual Studio</a></li><li><a href="https://nodejs.org/en/download">Node.js</a> and <a href="https://www.npmjs.com/get-npm">npm</a> locally installed. (Current LTS version preferred)</li></ul><blockquote><em>Some developers, including myself, prefer to use </em><a href="https://github.com/nvm-sh/nvm"><em>nvm</em></a><em> or </em><a href="https://github.com/coreybutler/nvm-windows"><em>nvm-windows</em></a><em> to simplify Node version management, which is perfectly fine.</em></blockquote><blockquote><em>For further reference you can check out also </em><a href="https://daily.dev/posts/how-to-use-multiple-node-versions-with-nvm-on-macos-node-version-manager"><em>How To Use Multiple Node Versions With NVM On MacOS — Node Version Manager</em></a></blockquote><h3>Development</h3><h4>Part 1. Dependencies</h4><p><em>The moment has arrived! Time to write some code.</em></p><p>Begin with these terminal commands to make an empty directory wherever you wish to store your server’s local version and create the first file using npm.</p><pre>mkdir smtp-email-server <br>cd smtp-email-server <br>npm init</pre><p>Follow the terminal prompts from npm to create a package.json file. In most cases, the default values will suffice, but be sure to change the entry point to server.js instead of the proposed index.js.</p><p>Now we need to add the required dependencies (npm packages) to our project. Run the following command and notice that npm automatically creates a new directory called node_modules. This is normal, so don&#39;t change or configure anything in this folder.</p><pre>npm install express nodemailer morgan dotenv</pre><p>Let’s glance at a brief overview of each package.</p><ul><li><strong>Express</strong> is a minimal and flexible Node.js web application framework that provides a robust set of features.</li><li><strong>Nodemailer</strong> is a module designed to allow Node.js applications to send emails securely and efficiently.</li><li><strong>Morgan</strong> is named after Dexter (a show you should not watch until completion) and provides HTTP request logger middleware for Node.js.</li><li><strong>dotenv</strong> is a zero-dependency module that loads environment variables from a .env file into process.env.</li></ul><h4>Part 2. Routes</h4><p>Let’s begin by creating a routes folder containing routes.js.</p><pre>mkdir routes &amp;&amp; cd routes &amp;&amp; touch routes.js</pre><p>Open routes.js in your code editor and establish a baseline by requiring the dependencies at the top of the file.</p><pre>require(&quot;dotenv&quot;).config();<br>// routes.js<br>const router = require(&quot;express&quot;).Router();<br>const path = require(&quot;path&quot;);<br>const nodemailer = require(&quot;nodemailer&quot;);</pre><p>As you can see, Express has its own built-in router. I have opted to use this option instead of a separate npm package. This helps keep our application lightweight and efficient.</p><p>Our next order of work will involve setting up authentication using our Gmail account credentials. Don’t forget to add the .env file in the root directory rather than our current location.</p><pre>const transport = {<br>    //this is the authentication for sending email.<br>    host: &quot;smtp.gmail.com&quot;,<br>    port: 465,<br>    secure: true, // use TLS<br>    /* create a .env file and define your credentials. */<br>    auth: {<br>        user: process.env.SMTP_TO_EMAIL,<br>        pass: process.env.SMTP_TO_PASSWORD,<br>    },<br>};</pre><p>Remember the transport function we mentioned earlier? In this step, we will construct that same function. Let’s have a look!</p><pre>// call the transport function<br>const transporter = nodemailer.createTransport(transport);<br>transporter.verify((error, success) =&gt; {<br>    if (error) {<br>        //if error happened code ends here<br>        console.error(error);<br>    } else {<br>        //this means success<br>        console.log(&quot;Ready to send mail!&quot;);<br>    }<br>})</pre><p>Now let’s build the API routes. We will simultaneously define the schema for our JSON object (email).</p><p>In simple terms, we are telling Nodemailer about the form data it will be receiving from the front-end and how it should translate said data into a structured email.</p><p>Finally, we call the transporter.sendMail function, Nodemailer works its magic, and the email goes on its merry way to the recipient&#39;s inbox.</p><pre>router.get(&#39;/&#39;, (req, res, next) =&gt; {<br>    res.status(200).json({ msg: &#39;Working&#39; })<br>})<br>router.post(&#39;/&#39;, (req, res, next) =&gt; {<br>    //make mailable object<br>    const mail = {<br>    from: process.env.SMTP_FROM_EMAIL,<br>    to: process.env.SMTP_TO_EMAIL,<br>    subject: &#39;New Contact Form Submission&#39;,<br>    text: `from: ${req.body.name} contact details email: ${req.body.email} phone: ${req.body.tel} message: ${req.body.message}`,<br>    }<br>    transporter.sendMail(mail, (err, data) =&gt; {<br>    if (err) {<br>        res.json({<br>            status: &#39;fail&#39;,<br>        })<br>        } else {<br>        res.json({<br>            status: &#39;success&#39;,<br>        })<br>    }<br>    })<br>})</pre><p>The last block of code in this file instructs Express to use the routes we have established; finally, we export the entire router to the Node server.</p><pre>// Answer API requests.<br>router.use(&#39;/api&#39;, function (req, res) {<br>    res.set(&#39;Content-Type&#39;, &#39;application/json&#39;)<br>    res.send(&#39;{&quot;message&quot;:&quot;Hello from the custom server!&quot;}&#39;)<br>})<br>/* All remaining requests return the React app, so it can <br>handle routing. */<br>router.use(&#39;*&#39;, function (request, response) { <br>    response.sendFile(path.resolve(__dirname, &#39;/react- <br>    ui/build&#39;, &#39;index.html&#39;))<br>})<br>module.exports = router</pre><blockquote><em>NOTE: </em>If you are unfamiliar with <em>process.env</em> or merely need a refresher, this Codeburst article provides a splendid reference point.</blockquote><p><a href="https://codeburst.io/process-env-what-it-is-and-why-when-how-to-use-it-effectively-505d0b2831e7">process.env: What it is and why/when/how to use it effectively</a></p><h4>Part 3. Server</h4><p>Let’s create a server.js file in the root directory and open it with the editor.</p><p>Here we are just ensuring everything runs smoothly. I could write an entire article about each of the parameters defined here, but the template is pretty standard.</p><p>Let’s start by defining some initial requirements.</p><pre>const express = require(&#39;express&#39;)<br>const cluster = require(&#39;cluster&#39;)<br>const numCPUs = require(&#39;os&#39;).cpus().length</pre><p>Now we should check the environment to see if we are running in production. If so, we use a <a href="https://nodejs.org/api/cluster.html">cluster of Node processes</a> to distribute the stress of running the application as evenly as possible across the server cores.</p><pre>const isDev = process.env.NODE_ENV !== &#39;production&#39;<br>/* Multi-process to utilize all CPU cores. */<br>if (!isDev &amp;&amp; cluster.isMaster) {<br>    console.error(`Node cluster master ${process.pid} is running`)<br>    // Fork workers.<br>    for (let i = 0; i &lt; numCPUs; i++) {<br>    cluster.fork()<br>    }<br>cluster.on(&#39;exit&#39;, (worker, code, signal) =&gt; {<br>    console.error(`Node cluster worker ${worker.process.pid} exited: code ${code}, signal ${signal}`)<br>    })<br>}</pre><p>We will then connect to the frontend, priority serve our static HTML files, define some middleware for AJAX parsing, and finally call the routes we are importing from the routes.js file, all in that order.</p><p>We wrap it up with some error logging for the development environment, and voila! Our Express mail server is humming along.</p><pre>else {<br>     const app = express()<br>     const morgan = require(&#39;morgan&#39;)<br>     const path = require(&#39;path&#39;)<br>     const PORT = process.env.PORT || 5000<br>     /* Priority serve any static files. */<br>     /* Replace the example to connect to your frontend. */<br>     app.use(express.static(path.join(__dirname, <br>     &#39;/example/frontend.js&#39;)))<br>     // dev middleware<br>     app.use(morgan(&#39;dev&#39;))<br>     /* configure body parser for AJAX requests */<br>     app.use(express.urlencoded({ extended: false }))<br>     app.use(express.json())<br>     const routes = require(&#39;./routes/routes&#39;)<br>     /* after all middleware functions */<br>     app.use(&#39;/&#39;, routes)<br>     app.listen(PORT, function () { <br>     console.error(`Node ${isDev ? &#39;dev server&#39; : &#39;cluster worker&#39; <br>     + process.pid}:<br>     listening on port ${PORT}`)<br>})</pre><h3>SMTP Email Server is complete! Congratulations!</h3><blockquote><em>NOTE: </em>If you encounter difficulty with the authentication process, read this Google Support documentation! It will save you hours of debugging and Excedrin.</blockquote><blockquote><a href="https://support.google.com/accounts/answer/6010255?hl=en">Less secure apps &amp; your Google Account — Google Account Help</a></blockquote><h3>Conclusion</h3><p>We’ve successfully created an SMTP Email Server using Express and Node. We also learned how to integrate Nodemailer and Gmail to streamline the mailing process.</p><p><a href="https://github.com/killshot13/express-smtp-mailer">killshot13/express-smtp-mailer: A production-ready Node backend with an Express SMTP mail server configurable for use with contact forms, subscriptions, etc. (github.com)</a></p><p>Feel free to clone the source code and explore your own methods of implementation. I hope you have found this tutorial useful, and thank you for taking the time to follow along!</p><p>If you found this article useful, don’t forget to 👏 and share it! If you’re feeling extra generous, please click below to 🎆subscribe🎇!</p><p>— killshot13</p><p>Still feel like reading? Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out some of my other popular articles!</p><p><em>Originally published at </em><a href="https://daily.dev/blog/how-to-build-an-smtp-mail-server-with-express-node-and-gmail"><em>https://daily.dev</em></a><em> on February 4, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e58ee84de52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-develop-engineer/build-an-smtp-mail-server-with-express-node-and-gmail-7e58ee84de52">How To Build an SMTP Mail Server with Express, Node, and Gmail</a> was originally published in <a href="https://medium.com/code-develop-engineer">Code. Develop. Engineer.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Discussions”]]></title>
            <link>https://cde13.medium.com/discussions-d216ce8bba6e?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d216ce8bba6e</guid>
            <category><![CDATA[developer-news]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[public-beta]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Sun, 17 Jan 2021 02:16:28 GMT</pubDate>
            <atom:updated>2022-08-24T05:39:06.135Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>A Thorough Review of GitHub’s Latest Brainchild</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tdq5yG6Ut4ir0-sk4xBGWg.jpeg" /><figcaption>View of a “GitHub Discussion”</figcaption></figure><blockquote><strong>“Discussions is a collaborative communication forum for the community around an open source project.”</strong> — <a href="https://docs.github.com/en/discussions"><em>GitHub Docs</em></a></blockquote><h3>Overview</h3><p>After nearly a year of private beta testing, GitHub confirmed last month in a blog post that its new <a href="https://docs.github.com/en/discussions">Discussions</a> feature is now available as a public beta.</p><p>First revealed during the live stream of GitHub’s <a href="https://githubsatellite.com/">Satellite Virtual 2020</a>, this latest addition to the GitHub platform seeks to provide a way for software communities to collaborate outside the codebase.</p><p>In theory, the new feature will improve collective participation for open-source projects while smoothing communication lines between project managers, developers, beta testers, and end-users.</p><p>Some prominent repositories, such as <a href="https://github.com/nodejs/node/discussions">Node.js</a>, <a href="https://github.com/laravel/framework/discussions">Laravel</a>, <a href="https://github.com/vercel/next.js/discussions">Next.js</a>, and <a href="https://github.com/prisma/prisma/discussions">Prisma</a>, participated in the first round of beta testing and have already successfully integrated Discussions. Based on current trends, <strong>it appears that Discussions is poised to reshape the existing structure of most GitHub repositories.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pywljbeXoHbQz_oJ36SFlg.jpeg" /><figcaption><a href="https://github.com/vercel/next.js/discussions">A view of “Discussions” from the Next.js repository</a></figcaption></figure><h3>Features</h3><p>By default, <strong>four categories</strong> are created to help Discussions stay organized.</p><ol><li>💬 General</li><li>💡 Idea</li><li>🙏 Q&amp;A</li><li>🙌 Show and tell</li></ol><p>Aside from these templated options, repository owners can author unlimited custom threads. <strong>Users are encouraged to mark quality answers as helpful</strong>, similar to the familiar layout of Stack Overflow.</p><p>Discussions also attempts to establish content moderation by <strong>allowing top contributors to achieve higher privileges. </strong>This option should help relieve some stress for the developer(s), who would otherwise be forced to keep a constant eye on the conversations.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDbTWBP3_RbM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDbTWBP3_RbM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDbTWBP3_RbM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5eab389c12214e85bc9ea1a6af35a907/href">https://medium.com/media/5eab389c12214e85bc9ea1a6af35a907/href</a></iframe><h3>Configuration</h3><p>Anyone can configure Discussions quite easily; it took me about<strong> 5–10 minutes per repository</strong> on average.</p><p>The layout is almost identical to GitHub issues, allowing for creating any number of topics linked to a single repository, each with a unique title and URL. While this is conducive in most scenarios, the setup could intimidate some developers who maintain an extensive library of source code.</p><p>Fortunately, most of the configuration is already provided by a boilerplate template. I found the default options to be well-balanced, sparing precious design time while still allowing customization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*57nKA0r8kbFiWA0O-m8qtA.jpeg" /><figcaption><a href="https://docs.github.com/en/discussions/quickstart">Getting Started with Discussions</a></figcaption></figure><p>As shown on the left, the option to enable Discussions is now available for every repository. To access, open the settings tab and scroll to the bottom of the features section.</p><p>You are now presented with a template containing several options to personalize if you so desire. Styling with Markdown is supported, so once you are satisfied, preview and publish just like a README.</p><p>A new menu tab should appear in the navbar of the repository. Here, members of the software community who utilize your code can now gather to converse and collaborate.</p><h3>Outlook</h3><p>Some developers contend that Discussions shares too much similarity with existing features to be worth the hassle. Others fear that management will pile more expectations onto an already overwhelming workload.</p><p>As it stands, Discussions admittedly leaves room for improvement and likely will not be suitable for every situation. That being said, the latest metrics released by GitHub in a new report are nothing short of impressive.*</p><p>Since January 2020 —</p><ul><li><strong>3000 discussions</strong> have been created.</li><li><strong>50% of active Discussions users</strong> contributed or pushed code.</li><li><strong>34% more pull requests</strong> were merged.</li><li><strong>18% less time</strong> was required to accomplish a merge.</li></ul><p>All figures were derived from beta testing conducted after the addition of Discussions to the Next.js repository, which produced a marked overall improvement in <strong>user participation</strong> and <strong>developer productivity.</strong></p><p>*If you wish to read the entire report, visit <a href="https://octoverse.github.com/#community"><strong>octoverse.github.com</strong></a>, where you can also download a PDF copy for later reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wMfOcqno14V1f1R_dZ8yww.jpeg" /><figcaption>Customization options for pinned Discussions</figcaption></figure><h3>Conclusion</h3><p>Every developer knows that data from a test environment cannot be used conclusively to predict future performance.</p><p>However, if the benchmarks established last year hold steady, we can safely assume that Discussions&#39; popularity and usage will continue to increase across GitHub. So here is my personal opinion on the matter.</p><p><strong>Provided as users, we treat Discussions like a tool and not a social media platform, and as project managers, we integrate the feature gradually and tactfully; I believe there are many benefits to be realized.</strong></p><p>I would love to gather perspectives from all of you on the matter, so please leave your thoughts in the comments.</p><p>— killshot13</p><p>Still feel like reading? Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out some of my other popular articles!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d216ce8bba6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[mj-pa]]></title>
            <link>https://cde13.medium.com/mj-pa-4ade95f91fd7?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ade95f91fd7</guid>
            <category><![CDATA[prettier]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[formatting-code]]></category>
            <category><![CDATA[configuration]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Sat, 31 Oct 2020 07:35:42 GMT</pubDate>
            <atom:updated>2021-11-07T15:52:15.285Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0slHJ8UuGGcOn-JmKHxew.jpeg" /><figcaption>“Prettier, meet JavaScript, and JavaScript, meet Prettier.”</figcaption></figure><h3>mj-pa:</h3><h4>A custom Prettier configuration designed for ReactJS, JSON, &amp; JSX.</h4><h4>Introduction</h4><p>I’ll start this article off with a rather embarrassing confession; until last month, I was unaware that “regular developers” could publish packages to npm. I don’t know why I believed this, and I just assumed there was some stringent checklist or rigorous testing that each bit of code underwent to become an npm package.</p><figure><img alt="Successful installation of the mj-pa package from the command line using npm." src="https://cdn-images-1.medium.com/max/1024/1*D92z29vRMjp-Oe9-o81C3A.jpeg" /><figcaption>First time installing mj-pa into an actual codebase! 😅</figcaption></figure><h4>Seeking Confidence</h4><p>Credit goes to the <a href="https://prettier.io/docs/en/index.html">Prettier docs</a> for broadening my perspective. Herein is made a brief reference to the option to publish one’s own configuration file to npm, allowing for reuse across multiple projects and sharing with others. I bookmarked the link for later and continued searching for the answer I needed at the moment.</p><blockquote>The mj-pa config is naturally opinionated since it was modeled after and directly extends the Prettier formatting tool, an almost equally dogmatic source.</blockquote><p>The concept still intimidated me a bit. As a junior developer, was I even worthy of making a valuable contribution to the excellent <a href="https://registry.npmjs.org/">npm registry</a>? But see that was just my lack of self-confidence talking. As it turns out, the answer to these types of questions is always, “Yes!”, and this is certainly also the case for any similar ambitions you might presently have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*buOKFe13iuZMFSWWvSsSIA.jpeg" /><figcaption>mj-pa v1.0.0 is published to npm</figcaption></figure><h4>A Package is Born</h4><p>As you can see from the photos, I eventually gathered the courage to define my very own <a href="https://prettier.io/">Prettier</a> configuration file and publish it to the npm registry.</p><p>Which, I might add, if you have never attempted this before, can be pretty challenging! I spent hours poring over the npm documentation and checking <a href="https://stackoverflow.com/">Stack Overflow</a>, searching for elusive but straightforward tips and tricks. Lest I digress too much, I shall write in more detail at a later time about the technical side of publishing my first npm package.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ABVwmogVIQz6kPkhgVa49A.png" /><figcaption>React component after being formatted with mj-pa</figcaption></figure><h4>Use Cases</h4><p>While the variables may have shifted over time, the codebases in which I have been using mj-pa have remained relatively similar, due in part to the limited scope of Prettier itself. The formatter works almost exclusively within the JavaScript ecosystem, so, naturally, the best results will be realized when mj-pa is used in a React- or Vue- style JavaScript environment.</p><p>Now I realize each developer will have a different opinion, and I am by no means claiming to have written the best config file or discovered the perfect formatting parameters. However, if you decide to give mj-pa a shot, at least now you have the project’s backstory.</p><p>And should you decide to make your edits or write an entirely different version, hopefully, you now have the confidence to experiment just as I have done until you decide what works best for you.</p><h3>Michael R. on Twitter: &quot;#opinionated #prettier #reactdeveloper pic.twitter.com/HIcjkGpRhf / Twitter&quot;</h3><p>opinionated #prettier #reactdeveloper pic.twitter.com/HIcjkGpRhf</p><h4>Making it Better</h4><p>Since its release, I have made several updates to mj-pa, and I also published it to the <a href="https://github.com/killshot13/mj-pa/packages/549875">GitHub package registry</a> and the <a href="https://www.npmjs.com/package/mj-pa">npm registry</a>. The most noteworthy was the recent release of v2.0.0, which introduced several critical adjustments to the previous config.</p><p>You may rightfully wonder, “If your config was so great, then why would you need to change it?” The long and short answer is that I didn’t know as much then as I do now, so some of my initial configuration choices were based on inaccurate assumptions or incomplete data.</p><p>Let’s face it; opinions are universally fluid. Most developers will change their viewpoints over time, especially if they remain open-minded and willing to consider perspectives besides their own.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FlUpP5P8rQVE5wC&amp;display_name=SlideShare&amp;url=https%3A%2F%2Fwww.slideshare.net%2FMichaelRehnert%2Fmjpa-v200&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fmj-pa-211107154243-thumbnail-4.jpg%3Fcb%3D1636300080&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/3adf87282378b7814699e47aa8bfe6b3/href">https://medium.com/media/3adf87282378b7814699e47aa8bfe6b3/href</a></iframe><h4>Conclusion</h4><p>Even while we are junior developers, we should never be afraid of trying something new. While there exists a level of understanding that should be achieved before rushing headlong into the unknown, at some point, we have to take the plunge.</p><p>I hope this inspires you also to attempt something that has been making you nervous until now! Feel free to add suggestions or ask questions in the comments below, and I will get back to you. Thank you for reading, and don’t forget to try <a href="https://www.npmjs.com/package/mj-pa">mj-pa</a>!</p><p>— killshot13</p><p>If you found this article useful, please 👏 to share it!</p><p>Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out my most popular articles below!</p><ul><li><a href="https://sth13.medium.com/pure-css-angled-blockquotes-9da6da0c788a">Pure CSS Blockquotes</a></li><li><a href="https://sth13.medium.com/docker-install-setup-for-windows-10-10e7bd097dd">Docker Desktop Install/Setup for Windows 10</a></li><li><a href="https://medium.com/@sth13/npm-publish-a8a879938eaf">npm-publish</a></li></ul><p><em>Originally published </em><a href="https://www.linkedin.com/pulse/mj-pa-michael-rehnert"><em>on LinkedIn</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ade95f91fd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[npm-publish]]></title>
            <link>https://cde13.medium.com/npm-publish-a8a879938eaf?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8a879938eaf</guid>
            <category><![CDATA[node-package-manager]]></category>
            <category><![CDATA[npm-publish]]></category>
            <category><![CDATA[npm-registry]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[npm-package]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Sat, 24 Oct 2020 09:16:25 GMT</pubDate>
            <atom:updated>2022-08-24T05:25:08.570Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qj1OTPHk-djj2C1Nnkn4VQ.png" /><figcaption>The iconic logo of the <a href="https://www.npmjs.com/">npm registry</a></figcaption></figure><h4>a guide to releasing your first npm package</h4><h4>Introduction</h4><p>npm (node package manager) is the world’s largest software registry. According to the <a href="https://docs.npmjs.com/about-npm/">documentation</a>, npm consists of three distinct components:</p><ul><li>the registry</li><li>the website</li><li>the CLI</li></ul><p>The registry is an immense database containing all the node packages &amp; modules ever published, complete with version info and metadata.</p><p>On the website, you can search for and view packages, create an npm profile, and manage user settings.</p><p>The CLI provides the primary means of interacting with npm, including the publishing of packages &amp; modules, which we will now cover in-depth.</p><h3>Prerequisites:</h3><ol><li>an <a href="https://www.npmjs.com/">npm</a> account</li><li>a <a href="https://github.com/">GitHub</a> account</li><li>the <a href="https://nodejs.org/">current version</a> of Node.js</li><li>the <a href="https://github.com/npm/cli/releases/latest">current stable version</a> of npm</li></ol><pre>npm install npm@latest -g</pre><h3>Package vs Module</h3><p>It is important to understand the two types of objects you can publish to the registry.</p><h4>How is a package defined?</h4><ul><li>a) A folder containing a program described by a package.json file.</li><li>b) A gzipped tarball containing (a).</li><li>c) A URL that resolves to (b).</li><li>d) A &lt;name&gt;@&lt;version&gt; that is published on the registry with (c).</li><li>e) A &lt;name&gt;@&lt;tag&gt; that points to (d).</li><li>f) A &lt;name&gt; that has a latest tag satisfying (e).</li><li>g) A git URL that, when cloned, results in (a).</li></ul><h4>How is a module defined?</h4><p>Any file or directory within node_modules that can be loaded by the Node.js require() function. To comply, at least one of these formats must be used.</p><ul><li>A folder with a package.json file containing a &quot;main&quot; field.</li><li>A folder with an index.js file in it.</li><li>A JavaScript file.</li></ul><p>A module can also be a package, but not all modules are packages by default.</p><h3>Private vs Public</h3><p>This parameter determines the visibility of your new npm package. For this article, it is assumed that you will elect to create a public package, but you may always reference the <a href="https://docs.npmjs.com/creating-and-publishing-private-packages#publishing-private-packages">documentation</a> for more details.</p><h4>Scoped vs Unscoped</h4><p>Here you will define whether you want to release your code completely to the public domain (unscoped) or publish the code within a retained namespace (scoped).</p><ul><li><a href="https://docs.npmjs.com/creating-and-publishing-unscoped-public-packages">Unscoped packages</a> are always public.</li><li><a href="https://docs.npmjs.com/about-private-packages">Private packages</a> are always scoped.</li><li><a href="https://docs.npmjs.com/creating-and-publishing-scoped-public-packages">Scoped packages</a> are private by default; you must pass a command-line flag when publishing to make them public.</li></ul><p>The command line interprets your decision by how your package is named. I’ll create examples based on my own npm account username.</p><pre>PUBLIC/UNSCOPED: npm publish my-package</pre><pre>PUBLIC/SCOPED: npm publish @killshot13_npm/my-package --access public</pre><pre>PRIVATE/SCOPED: npm publish @killshot13_npm/my-package</pre><p>To avoid confusing the reader, I shall refrain from much discussion about teams, organizations, and enterprise accounts. Since this article is about publishing our first npm package, I doubt these factors will be of much concern at present. Just be aware of the concepts for future knowledge.</p><h3>Create | Review | Test | Publish</h3><p>At last, the moment you have been waiting for! These four simple steps are what you will be using to publish your package or module to the registry.</p><p>WARNING: If you deviate from this path or omit one of these steps, chances are you will encounter errors and spend a considerable amount of time debugging your files.</p><h4>Create</h4><pre>mkdir my-package<br>cd my-package</pre><p>Now that you have a root directory, initiate git and npm</p><pre>git init<br>git remote add origin git://YOUR URL HERE</pre><pre>npm init</pre><pre>// Follow the prompts to create a package.json file. <br>// Consider the conventions listed above when naming your package.</pre><p>Now open the directory in your favorite code editor and add a README.md file and the rest of your package code files.</p><h4>Review</h4><p>In this step, use whatever means are at your disposal to double-check your code for environmental variables, including passwords, API keys, and other sensitive data.</p><p>If necessary, create the appropriate files and replace your existing code with default variables as needed to protect your secrets.</p><pre>.gitignore | .npmignore | .env | PROCESS.ENV</pre><h4>Test</h4><p>Almost there! Just one more quick (hopefully) thing to wrap up before you publish. To keep bugs out of the registry, especially when publishing publically, you should first test your package in your own environment.</p><p>Since you are already using the npm CLI, you can just run this command.</p><pre>npm install my-package<br>// Use the full path to your project directory.</pre><p>If everything functions as designed, congratulations, you are ready to publish your first package!</p><h4>Publish</h4><p>This is the simplest and most satisfying step. Navigate back to the root directory of your npm package.</p><pre>cd /path/to/package</pre><p>Are you ready?</p><pre>npm publish my-package</pre><p>If npm prints something that looks like this, you are golden!</p><figure><img alt="The code output from a successful npm publish" src="https://cdn-images-1.medium.com/max/562/1*a4D33da_XKMAWcKiqtVaNA.png" /><figcaption>Photo courtesy <a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fdev.to%2Fuf4no%2Fnpm-behind-the-scenes-and-publish-guide-4gi8&amp;psig=AOvVaw2YASbV57xtKtceX3dfQIse&amp;ust=1603615047851000&amp;source=images&amp;cd=vfe&amp;ved=0CAMQjB1qFwoTCJi1qeHpzOwCFQAAAAAdAAAAABAD">Dev Community</a></figcaption></figure><h3>Tips &amp; Tricks</h3><ul><li>Once you npm publish, you <strong>CANNOT </strong>change your package name! Take a moment to solidify your choice of words. Try to keep package names short and descriptive. For an example of what not to do, imagine installing this npm package.</li></ul><blockquote>I pity the fool!</blockquote><pre>npm install --save @teambit/staged-components.component-status-resolver</pre><ul><li>Sometimes, even with an unscoped public package, npm refuses to publish unless you include a flag. Add --access public to your command and try again.</li></ul><pre>npm publish my-package --access public</pre><ul><li>If you enabled 2FA when creating your npm account, you will have to provide the one-time token in your publish command.</li></ul><pre>npm publish my-package --otp=811486</pre><h3>Conclusion</h3><p>I hope you enjoyed this article. Feel free to add suggestions or ask questions in the comments below, and I will get back to you. Thank you for reading, and happy coding!</p><p>— killshot13</p><p>If you found this article useful or interesting, please 👏 and share it! <br>Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out my most popular articles below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8a879938eaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker Desktop Install/Setup for Windows 10]]></title>
            <link>https://cde13.medium.com/docker-install-setup-for-windows-10-10e7bd097dd?source=rss-bd08e23926d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/10e7bd097dd</guid>
            <category><![CDATA[windows-10]]></category>
            <category><![CDATA[docker-installation]]></category>
            <category><![CDATA[docker-desktop]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[integration-platform]]></category>
            <dc:creator><![CDATA[M. Rehnert]]></dc:creator>
            <pubDate>Tue, 04 Aug 2020 01:45:39 GMT</pubDate>
            <atom:updated>2022-08-24T05:26:49.268Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a679x4Ar-Z480jJXJ7Mpdg.jpeg" /><figcaption>Docker Desktop</figcaption></figure><h3>Introduction</h3><p>Docker is an open-source, platform-as-a-service (PaaS) product grouping that provides software delivery using virtualization at the system level. Using a container method similar to how folders can hold various types of files, Docker ships bundled software across the wires in a marvelously convenient fashion.</p><p>After creating a Docker account and downloading the required software, you will have access to the world’s largest library of container images. Docker is amazingly versatile and compatible with nearly every modern platform, including Kubernetes, AWS, Node.js, MongoDB, and MySQL.</p><p>Like many other popular platforms today such as MongoDB and GitHub, Docker provides a downloadable interface known as Docker Desktop. This versatile GUI provides a dashboard similar to the picture below and comes complete with Kubernetes support and an integrated command line. All these features are powered by the Docker Engine, a single kernel which hosts the containers for your entire network and sets a clear advantage over traditional virtual machines.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZqC8E4f9zNQF6Cfp8nmW2Q.png" /><figcaption>Docker Desktop</figcaption></figure><h3>Installation</h3><p>I hope you are excited as I was to get these awesome features onto your Windows machine! It takes about fifteen minutes to get Docker Desktop up and running, provided your machine already meets the prerequisites listed below.</p><h4>System Requirements</h4><p>Windows 10 Pro, Enterprise, or Education (Build 16299 or later)<br>— 64-bit processor<br>— 4 GB RAM<br> — <a href="https://docs.docker.com/docker-for-windows/troubleshoot/#virtualization-must-be-enabled">BIOS virtualization</a> enabled<br>— <a href="https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v">Hyper-V</a> enabled</p><p>Windows 10 Home (Version 2004 and up) <br>— 64-bit processor<br>— 4 GB RAM<br>— <a href="https://docs.docker.com/docker-for-windows/troubleshoot/#virtualization-must-be-enabled">BIOS virtualization</a> enabled<br> — <a href="https://docs.microsoft.com/en-us/windows/wsl/install-win10">WSL 2 feature</a> enabled</p><h4>Acquire the Installer</h4><p>Your journey begins on the <a href="https://www.docker.com/get-started">Docker website</a>. Here you can <a href="https://hub.docker.com/signup">signup for Docker Hub</a> or <a href="https://www.docker.com/play-with-docker">play around with Docker</a> in the sandbox if you wish. You should also see a simple “Download for Windows” option. Click here to get started!</p><p>You may have to run the .exe file to start the installer, which will request the necessary permissions and guide you through the rest of the installation process. After closing the installer, you will be ready to start using Docker Desktop.</p><h4>Setup the Dashboard</h4><p>Docker Desktop usually does not start on its own; you will need to access the program through the Start menu. Once initialized, you should see a small whale icon in the notifications section of your taskbar. Wait until the icon animation stops and you receive a confirmation message that Docker is running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HclGulQJXkVT_EU8qh19kw.jpeg" /><figcaption>Docker Desktop Tutorial</figcaption></figure><p>You may now right-click the icon and select Dashboard, which will open the interface and present you with a tutorial. Your screen should be similar to the photo above. The tutorial will run you through the four basic steps of using Docker and is a good way to get familiar with using the dashboard.</p><ul><li>Clone</li><li>Build</li><li>Run</li><li>Share</li></ul><p>You will be provided code snippets that clone a repository from GitHub, build the image in a container, and run the application in your web browser.* Once this is done, you get to share your first Docker Desktop application with the world!</p><p>*Note: You may run into an error at the beginning of the run sequence. Don’t panic, there is a troubleshooting section at the bottom of this page to help clear things up.</p><h4>Docker Desktop install/setup for Windows 10 is now complete. Congratulations!</h4><h3>Pro Tips</h3><p>Here are some optional steps and troubleshooting tricks to help solidify your successful start with Docker development.</p><h4>Additional Setup</h4><ol><li>Turn on Experimental Features in the settings panel to run a Windows PowerShell terminal right in your dashboard.</li><li>Create a Docker account so you can access the Docker Hub online and sync your dashboard with the cloud.</li><li>Connect your GitHub or BitBucket account to Docker Hub so you can manage your repositories online and with Docker Desktop.</li><li>Enable Kubernetes in the settings panel to start a single-node cluster each time you start Docker Desktop.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svCd4hzmipYXvY5uMKMaDA.jpeg" /><figcaption>Docker Desktop — Port 80:80 Error</figcaption></figure><h4>Troubleshooting</h4><p>If you are reading this, you have likely encountered the following error —</p><pre><strong>docker: Error response from daemon: Ports are not available: listen tcp 0.0.0.0:80: bind: An attempt was made to access a socket in a way forbidden by its access permissions.</strong></pre><p>This error is caused because another program or service is already running on your localhost:80; else it could be a port enabling issue. Your firewall might even be the culprit. If you would rather avoid the tedious process of elimination hunting down a ghost, run the following code in the terminal.</p><pre><strong>docker run -d -p 81:80 --name docker-tutorial docker101tutorial</strong></pre><p>By avoiding port 80 altogether and using port 81 instead, the server should start successfully. To be certain, open <a href="http://localhost:81/">this link</a> and you should see the following cheery message —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*vUhKiSTU8LwACHmjXyJLVQ.jpeg" /><figcaption>nginx welcome message</figcaption></figure><p>You can now complete the last step of the tutorial by following the prompts in your Docker Desktop application.</p><h3>Conclusion</h3><p>I hope you enjoyed this article. Feel free to add suggestions or ask questions in the comments below, and I will get back to you. Thank you for reading, and happy coding!</p><p>— killshot13</p><p>If you found this article useful or interesting, please 👏 and share it! <br>Follow me (<a href="https://sth13.medium.com/">M Rehnert</a>) on Medium and check out my most popular articles below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10e7bd097dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>