The reason we had to look into this is because we wanted to setup our own SMTP email server in a docker and having tried a couple of options we ended up with mailcow. Funny name but the only choice with no SPF and DKIM issues. However it creates a lot of docker containers to get up and running. Not a bad thing until you have to reset all cache and figure out how to restart all docker containers. Now that was our use case, your use case might be completely different but what to do next is the same. First see which containers are running.A simple command to do that is.<pre class="ql-syntax" spellcheck="false">docker ps 
</pre>Do you only have docker container running? If so, to restart that individual container you can run<pre class="ql-syntax" spellcheck="false">docker restart &lt;container_id&gt; 
</pre>If you have multiple docker containers running which is why you probably ended up here try runningOption 1:<pre class="ql-syntax" spellcheck="false">docker ps -q | xargs docker restart 
</pre>If that doesn't work for any reason, also tryOption 2:<pre class="ql-syntax" spellcheck="false">docker restart $(docker ps -q) 
</pre>Love working with docker. Checkout <a href="https://denix.app/us/us/docker" rel="noopener noreferrer" target="_blank">docker jobs</a> Did that work for you?

How to restart all running docker containers?

Have you ever received a warning message that says "Warning: A title element received an array with more than 1 element as children" when working with titles in Next.js or another React framework.In this article, we will explore what I learned from <a href="https://github.com/icyJoseph" rel="noopener noreferrer" target="_blank">icyJoseph</a>What causes the warning? This warning is caused when an element in your React code is rendered with an array containing more than one element as children. For example, consider the following code:<pre class="ql-syntax" spellcheck="false">const Home: NextPage = () =&gt; {
 const world = "World";
 return (
 &lt;div&gt;
 &lt;span&gt;Hello {world} foo&lt;/span&gt;
 &lt;/div&gt;
 );
};
</pre>React actually renders:<pre class="ql-syntax" spellcheck="false">&lt;div&gt;&lt;span&gt;Hello &lt;!-- --&gt;World&lt;!-- --&gt; foo&lt;/span&gt;&lt;/div&gt;
</pre>He clarifies that :<blockquote>That's a div with a span child, with 0 children elements, but 5 nodes as children. There's a subtle difference between elements and nodes. Here's a handy video. The 5 nodes are, text, comment, text, comment, text. The same is happening to your title element.</blockquote>Such a simple yet insightful explanation.How to fix the warningThe fix for this warning is to ensure that your element has only one child, which should be a single string. You can accomplish this by concatenating your string with any variables outside of the JSX element. Here's an example of how to fix the previous code:<pre class="ql-syntax" spellcheck="false">const Home: NextPage = () =&gt; {
 const world = "World";
 const message = `Hello ${world} foo`;
 return (
 &lt;div&gt;
 &lt;span&gt;{message}&lt;/span&gt;
 &lt;/div&gt;
 );
};
</pre>Which outputs:<pre class="ql-syntax" spellcheck="false">&lt;div&gt;&lt;span&gt;Hello World foo&lt;/span&gt;&lt;/div&gt;
</pre>Now the&nbsp;<code style="background-color: var(--color-neutral-muted);">span</code>&nbsp;has only one,&nbsp;<code style="background-color: var(--color-neutral-muted);">text</code>, child node.Thank you to <a href="https://github.com/icyJoseph" rel="noopener noreferrer" target="_blank" style="color: rgb(76, 139, 245);">icyJoseph</a> for providing a brilliant answer to this question about the warning message.<pre class="ql-syntax" spellcheck="false"> Warning: A title element received an array with more than 1 element as children. In browsers title Elements can only have Text Nodes as children. If the children being rendered output more than a single text node in aggregate the browser will display markup and comments as text in the title and hydration will likely fail and fall back to client rendering at title at head at Head (webpack-internal:///./node_modules/next/dist/pages/_document.js:282:1) at html at Html (webpack-internal:///./node_modules/next/dist/pages/_document.js:685:104) at Document 
</pre>His explanation of the difference between elements and nodes and how to fix the warning was clear and concise.

[Solved] Next.js - Warning: A title element received an array with more than 1 element as children.

<h2>Introduction</h2>Introduction: After years of experience in web design and production, we’ve learned one thing for sure. Frontend engineering is a complex and time-consuming field that can take up a lot of your time and resources. That said, there are some great benefits to pursuing this area of design. For starters, frontend engineers can help you create stunning websites that look great on any device. They can also help you produce high-quality videos and podcasts while keeping your content fresh and engaging. In this guide, we’ll give you the inside scoop on how to get started in frontend engineering—and how to achieve success in this growing field. <h2>What is Frontend Engineering?</h2>Frontend engineering is the process of designing, developing and maintaining the user interface for a website or application. The main purpose of frontend engineering is to make the user experience as smooth and intuitive as possible. To achieve this, engineers typically use design patterns and library functions to create efficient and well-organized interfaces. They also use frontend development frameworks such as React, AngularJS, VueJS, KnockoutJS, and Wix to create web applications or websites. What are the Different Types of Frontend Engineering ToolsThere are many different types of frontend engineering tools available, but three of the most popular are React, AngularJS and VueJS. These frameworks allow you to build interfaces quickly and easily, making them great for creating quick prototypes or small apps. React is also known for its high level of productivity and stability, while AngularJS is fast and easy to learn but can be a little more complex than other frameworks. VueJS is a new framework that has been gaining in popularity over time because it is simple to use yet offers a lot of potential features compared to other frameworks. <h2>How to Get started in Frontend Engineering.</h2>To get started in frontend engineering, you first need to learn the basics of web development. This section will teach you about the different types of websites, how to use CSS to create web pages, and how to use JavaScript to create web applications. Understand the Different Types of Web ApplicationsThere are many different types of web applications that you can build. These include e-commerce websites, social networking sites, news organizations, and more. To understand which type of application best suits your needs, it’s important to first understand the different types of websites that these applications can be used on. This section will help you understand this concept by explaining the different types of websites and their uses. Use CSS to Create Web PagesCSS is a technology that helps you design websites by controlling how they look. To create web pages with CSS, you need to first learn how to use HTML and CSS together. This section will explain how CSS works and show you how to create a basic website using CSS alone. <h2>Tips for Successful Frontend Engineering.</h2>One of the most important skills for frontend engineers is using the right tools. To be successful, you’ll need to use the right programming languages and tools for the job. To get started, check out websites like Codecademy or Lynda.com to learn how to code and create web pages. Use the Right Formatting PrinciplesWhen it comes to formatting your website, you should use common web standards. This means using a style guide that tells you how to write your pages in a specific way, as well as following certain formatting rules when writing content or displaying images. Using these standards can help improve readability and consistency on your website. Use the Right Web StandardsWeb Standards are not just for formatting; they also play a big role in designating which devices will be able to see your website properly (phone, computer, etc.). By following web standards, you can ensure that all devices will be able to understand and display your website correctly. Use the Right FontsTo make your designs look great on different devices, you’ll need to use good fonts. Look for fonts that are used commonly in Europe or North America, as these font families tend to be more popular in those regions than in other countries. Additionally, consider using modern font technologies like Adobe Sans or Trebuchet MS which will look better on modern devices than older types of fonts. <h2>Conclusion</h2>Frontend engineering is a vital skill for any web developer. By understanding the different types of frontend designs, learning how to use CSS to create web pages, and using JavaScript to create web applications, you can build powerful and successful web applications. With the right tools and standards in place, you can build beautiful and user-friendly websites that appeal to a wide audience.

From design to production: the inside scoop on frontend engineering

EverNote is so pushy about paid plans, with their limitations on devices and what note that kind of pushed people away to other options in the market - Notion being the recent cool app and OneNote being the "been there forever" app.With Notion, one of the problems is that doesn't have a sidebar view that most people are used to in EverNote, so for a similar experience as EverNote, people end up with OneNote, and guess what? There is even an importer that makes the process easy to migrate the notes from EverNote to OneNote.&nbsp;While the&nbsp;UI is very similar, the OneNote&nbsp;app is cloggy, the web version is worse, it doesn't offer sorting and hogs the browser, and if you are mac user, in a couple of days, you'd think, "I should've rather paid for EverNote".Let's say you pay for EverNote and wanna&nbsp;start Evernoting again; you'd assume OneNote has some export functionality... hmmm, no, you'd think you can find an exporter just like you found an importer.. hmm no.. You'd think, how is this possible? Someone must have asked EverNote about it, or they'd have thought about it, and wouldn't it make sense for them a build such a tool to easily bring in the OneNoters... Apparently not cuz that would make sense and be logical.So what can help? Is there anything that can help? CloudHQ to the rescue, the only firm that has taken the pain to build a sync/push between the two. Does it work? We are waiting to find out. it does take a while if you are on a free plan cuz they throttle your sync if you are on a free plan, but they have some other sync and backup utils that may be worth the upgrade but definitely give it a shot&nbsp;So, where should you start?This article would be a good starting point to get you set up<a href="https://support.cloudhq.net/how-to-backup-onenote-and-evernote/" rel="noopener noreferrer" target="_blank">Cloud HQ Free Migrator</a>Let us know how it goes!

how to migrate notes from onenote to evernote?

Amazon in a small drop-down lets you decide, how you want to sort your items.
By default it's set to sort by "Featured". You can also change this option to pick one of the following
<ol>
<li>Featured</li>
<li>Price: Low to High</li>
<li>Price: High to Low</li>
<li>Avg. Customer Review</li>
</ol>
But the most annoying part is that Amazon will inject at least 16 items on top/bottom or sometimes in the middle that are "sponsored" items and that pretty much defied the purpose of sorting because "sponsored" items are sorted in an order depending on how much that brand wants to PPC.
So getting back to "How to hide sponsored items on Amazon?"
This trick is for chrome users who know how to open the web inspector in chrome, if you are not a chrome user or have never heard of web inspector this may not help
For those who know how to open web inspector in Chrome, this is a very simple and a neat trick
<h2 id="console" tabindex="0" data-text="Open the Console panel to view logged messages or run JavaScript">1. Open the Console panel in web inspector</h2>
Press&nbsp;<kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>J</kbd>&nbsp;(Mac) or&nbsp;<kbd>Control</kbd>+<kbd>Shift</kbd>+<kbd>J</kbd>&nbsp;(Windows, Linux, Chrome OS) to jump straight into the&nbsp;Console&nbsp;panel.
<h2 id="console" tabindex="0" data-text="Open the Console panel to view logged messages or run JavaScript">2. Paste the following script and hit enter</h2>
<pre class="language-javascript"><code>var i,y=document.getElementsByClassName("AdHolder");for(i=0;i&lt;y.length;i++)y[i].style.display="none";</code></pre>

How to hide sponsored items on Amazon?

There are two ways to get over this annoying /usr/bin error
1. Install the same gem using RVM (Ruby Version Manager), but first, you'll need RVM. Here's how to install RVM on OSX
<pre>\curl -sSL https://get.rvm.io | bash -s stable</pre>
PS: If that didn't work, <a href="https://zwbetz.com/install-ruby-version-manager-on-mac/" target="_blank" rel="noopener">here is some extra help</a>
&nbsp;
2. "-n flag"
Install the same gem using the mysterious "-n flag"
<pre class="language-powershell"><code>sudo gem install cocoapods -n /usr/local/bin</code></pre>
&nbsp;
3. "Create a ~/.gemrc file"
<pre class="language-powershell"><code>code ~/.gemrc</code></pre>
or
With the following content:
<pre class="language-powershell"><code>:gemdir:
 - ~/.gem/ruby
install: -n /usr/local/bin</code></pre>
Now you can install using gem install without the -n flag.
e.g.
<pre class="language-powershell"><code>sudo gem install git_swap</code></pre>

How do I fix the 'You don't have write permissions into the /usr/bin directory' error when installing a gem?

<img src="https://s3.us-west-2.amazonaws.com/fla.blog.images/2a9df990-63b4-11e9-8a7e-b38ac9beaecf/1598377628615-meteor.gif"> Packed with 22 updates, Meteor 1.11 includes major improvements in key areas.&nbsp;For full release notes&nbsp;<a href="https://blog.meteor.com/" rel="noopener noreferrer" target="_blank" style="color: rgb(0, 124, 137); background-color: rgb(255, 255, 255);">visit the blog</a>, as well as&nbsp;Meteor<a href="https://docs.meteor.com/" rel="noopener noreferrer" target="_blank" style="color: rgb(0, 124, 137); background-color: rgb(255, 255, 255);"> docs</a>.&nbsp; <h3>Lets dive into some highlights:&nbsp;</h3><h3>Performance Improvements:</h3>Meteor had multiple PRs improving the performance of their build in different areas, including:<ul><li>node_module watchers;</li><li>realpath usage;</li><li>enabled build in place on Windows;</li><li>reduced watchers and stats what saves CPU.</li></ul><h3>Cache your builds:</h3>They've introduced a new option in their deploy command:&nbsp;--cache-build . Using it in your deploy command Meteor will re-use your bundle if your git repository is in the same commit as the last time you deployed.&nbsp; TL;DR: use&nbsp;--cache-build&nbsp;when deploying to&nbsp;<a href="https://www.meteor.com/hosting" rel="noopener noreferrer" target="_blank" style="color: rgb(0, 124, 137); background-color: rgb(255, 255, 255);">Galaxy</a>.&nbsp;<h3>Apollo Skeleton + Vue Skeleton:</h3>Want to start a new project with Meteor using Apollo in the data layer? Just run:&nbsp;meteor create myproject --apollo and you're good to go!&nbsp; They also now have a simple one line command to create a new project using Meteor and Vue:&nbsp;meteor create myproject --vue&nbsp;

Meteor 1.11 is here!

Where to find jobs urgently hiring near me?

If you are a <a href="/i/Los-Angeles-CA/Frontend-Engineer" rel="noopener noreferrer" target="_blank">Frontend Engineer in Los Angeles, CA</a> you've most likely received calls from aggressive recruiters in the Bay Area, It is very tempting to move to the <a href="/i/San-Francisco-CA/Frontend-Engineer" rel="noopener noreferrer" target="_blank" style="background-color: rgb(255, 255, 255);">bay area</a> considering <a href="/i/San-Francisco-CA/Frontend-Engineer" rel="noopener noreferrer" target="_blank" style="background-color: rgb(255, 255, 255);">bay area</a> pays more, about $20,000 more for full time <a href="/i/San-Francisco-CA/Senior-Engineer" rel="noopener noreferrer" target="_blank">jobs for senior engineers</a> and sometimes about $20/hour more for contractor. It's sad to see lower salaries in <a href="/i/Los-Angeles-CA/Frontend-Engineer" rel="noopener noreferrer" target="_blank">Los Angeles, CA </a> but there is just more happening in the Bay Area and its happening at a much faster pace. Employers in LA have the time to haggle and low ball you as an engineer but very few firms have the time in <a href="/i/San-Francisco-CA/Frontend-Engineer" rel="noopener noreferrer" target="_blank">bay area</a> to focus on the wrong things. However if you love LA and/or have other ties that are stopping you from moving the the Bay Area for more money as a Frontend Engineer then here are 10 firms hiring <a href="/i/Los-Angeles-CA/Frontend-Engineer" rel="noopener noreferrer" target="_blank" style="background-color: rgb(255, 255, 255);">Frontend Engineers in Los Angeles, CA</a>

10 companies hiring now for Frontend Engineers in Los Angeles, CA

It has been brought to our notice that some undocumented immigrants with an ITIN have received their unemployment insurance payments but few citizens and residents still haven't received a dollar for probably a small mistake on their application.Have you received it yet?

Unemployment Insurance : Have you received it yet

<div class="mockup-code">
 <pre data-prefix="$"><code>Fetching packages ...</code></pre>
 <pre data-prefix="info"><code class="text-warning">There appears to be trouble with your network connection. Retrying...</code></pre>
 <pre data-prefix="info"><code class="text-warning">There appears to be trouble with your network connection. Retrying...</code></pre>
 <pre data-prefix="info"><code class="text-warning">There appears to be trouble with your network connection. Retrying...</code></pre>
 <pre data-prefix="info"><code class="text-warning">There appears to be trouble with your network connection. Retrying...</code></pre>
 <pre data-prefix="error"><code class="text-danger">An unexpected error occurred: "https://registry.yarnpkg.com/some-package-name:ESOCKETTIMEDOUT".</code></pre>
</div>


 An engineer could not run yarn this morning, asked another engineer if yarn was working for her, but it kept failing. we thought it's our corporate network that is down but it couldn't have been because everything else seemed to be working. so we logged on to a Windows VM on GCP. Since we are a Google Partner we have access to tons of VMs but yarn was failing there too. All our CI/CD pipelines that use yarn weren't working either. We thought of all Dockerfiles that use yarn for our clients.

The question is will it fix with time? or should we all go back to using npm install.

What seems to have worked for us was increasing the yarn timeout

<div class="mockup-code">
 <pre data-prefix="$"><code>yarn install --network-timeout 1000000</code></pre>
</div>
 
 also make sure there is no proxy


<div class="mockup-code">
<pre data-prefix="$"><code>npm config rm proxy</code></pre>
<pre data-prefix="$"><code>npm config rm https-proxy</code></pre>
</div>

 Did that work for you?