<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sergio Mendonca</title>
    <description>The latest articles on DEV Community by Sergio Mendonca (@sftom).</description>
    <link>https://dev.to/sftom</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F429606%2Fdefa9b8c-73d6-4fd9-b3e3-275e9df5af36.jpeg</url>
      <title>DEV Community: Sergio Mendonca</title>
      <link>https://dev.to/sftom</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sftom"/>
    <language>en</language>
    <item>
      <title>Automate your Awesome-CV with XeLaTeX and Gitlab CI</title>
      <dc:creator>Sergio Mendonca</dc:creator>
      <pubDate>Sun, 12 Jul 2020 22:19:50 +0000</pubDate>
      <link>https://dev.to/sftom/automate-your-awesome-cv-with-xelatex-and-gitlab-ci-5g4d</link>
      <guid>https://dev.to/sftom/automate-your-awesome-cv-with-xelatex-and-gitlab-ci-5g4d</guid>
      <description>&lt;h3&gt;
  
  
  Gitlab CI
&lt;/h3&gt;

&lt;p&gt;There are numerous tutorials and documentation to learn Gitlab CI/CD. It's enough you just google it. :p&lt;/p&gt;

&lt;p&gt;Everyone who knows LaTeX will probably complain now because I could just use Overleaf to edit my CV in the browser. That's totally correct, but I want to use Gitlab CI to present you with a simple exercise on Gitlab Continuous Integration.&lt;/p&gt;

&lt;p&gt;I forked the official Awesome-CV repository into my own Gitlab. Everything that builds your Awesome-CV automatically can be found in the &lt;code&gt;.gitlab-ci.yml&lt;/code&gt; file.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;pdf&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;image&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;thomasweise/texlive&lt;/span&gt;
  &lt;span class="na"&gt;script&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;cd examples&lt;/span&gt;
    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;xelatex cv.tex&lt;/span&gt;
  &lt;span class="na"&gt;artifacts&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;paths&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="s"&gt;examples/cv.pdf&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;h3&gt;
  
  
  Explanation
&lt;/h3&gt;

&lt;p&gt;By adding this file into the root directory of the repository a GitLab runner will execute the defined tasks.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;pdf&lt;/code&gt; defines the name of the runner job. &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;image&lt;/code&gt;: The runner starts the docker image that has texlive installed, labeled &lt;code&gt;thomasweise/texlive&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;Everything in &lt;code&gt;script&lt;/code&gt; will be executed in the docker container. Just like we use XeLaTeX on our local machine;&lt;/li&gt;
&lt;li&gt;The runner will switch to the &lt;code&gt;examples&lt;/code&gt; folder and;&lt;/li&gt;
&lt;li&gt;Execute &lt;code&gt;xelatex cv.tex&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;That will generate a PDF file - if no error occurred. &lt;/li&gt;
&lt;li&gt;To obtain the generated PDF file we have to define the file as an artifact. The &lt;code&gt;artifacts&lt;/code&gt; can be downloaded into a zipfile or browse to &lt;code&gt;examples/cv.pdf&lt;/code&gt;, if the job has finished successfully.&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The jobs for my repository can be found &lt;a href="https://gitlab.com/sftom/Awesome-CV/-/jobs"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;In the &lt;a href="https://gitlab.com/sftom/Awesome-CV/-/blob/master/README.md"&gt;README.md&lt;/a&gt; the status of the pipeline is displayed and direct links to the artifacts can be found. Have a look at the official documentation for the badges.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gh"&gt;# My Awesome-CV&lt;/span&gt;

&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;![pipeline status&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="sx"&gt;https://gitlab.com/sftom/Awesome-CV/badges/master/pipeline.svg&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;](https://gitlab.com/sftom/Awesome-CV/-/commits/master)

&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;Browse&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="sx"&gt;https://gitlab.com/sftom/Awesome-CV/builds/artifacts/master/browse?job=pdf&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; the Artifacts or &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;download&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="sx"&gt;https://gitlab.com/sftom/Awesome-CV/-/jobs/artifacts/master/raw/examples/cv.pdf?job=pdf&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; the PDF directly.

I forked from &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;Awesome-CV repository&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="sx"&gt;https://github.com/posquit0/Awesome-CV&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; into my own space on GitLab.
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;&lt;a href="https://gitlab.com/sftom/Awesome-CV/-/blob/master/README.md"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--audQPBvp--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/v1/./readme.png" alt=""&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://gitlab.com/sftom/Awesome-CV/-/blob/master/README.md"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--gwiFW5K3--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/wqxw85vdr2r74jcsmacm.png" alt=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you want to build your own Awesome-CV with Gitlab CI feel free to fork &lt;a href="https://gitlab.com/sftom/Awesome-CV/-/tree/customizing"&gt;my repository&lt;/a&gt; and start editing the files in the &lt;em&gt;customizing&lt;/em&gt; branch.&lt;/p&gt;

&lt;p&gt;Adapted by &lt;a href="https://ayeks.de/post/2018-01-25-awesome-cv-cicd/"&gt;LARS LÜHR, Blogging about coding, security and photography&lt;/a&gt;.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to create a profile on the new Github profile</title>
      <dc:creator>Sergio Mendonca</dc:creator>
      <pubDate>Sun, 12 Jul 2020 17:09:23 +0000</pubDate>
      <link>https://dev.to/sftom/como-criar-um-perfil-mais-atrativo-no-github-profile-248e</link>
      <guid>https://dev.to/sftom/como-criar-um-perfil-mais-atrativo-no-github-profile-248e</guid>
      <description>&lt;p&gt;Github launched a cool feature!&lt;/p&gt;

&lt;p&gt;The user can create a presentation page, through a README.md, within a public project of the same name as the user.&lt;/p&gt;

&lt;p&gt;And, it should look like this:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/sftom/sftom/README.md"&gt;&lt;code&gt;https://github.com/sftom/sftom/README.md&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Above, you can check my profile:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/sftom"&gt;&lt;code&gt;https://github.com/sftom&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>profile</category>
      <category>branding</category>
      <category>markdown</category>
    </item>
  </channel>
</rss>
