|
1 | 1 | # ten-seconds-cv
|
2 |
| -> A LaTeX resume/cv template for DevOps Engineer to make quick update and |
3 |
| -> pdf creation |
4 | 2 |
|
5 |
| -This template I use for my own resume/CV. |
| 3 | +Hi! |
| 4 | +My name is Esteban Martinena, a Software Engineer from Spain. |
| 5 | +This is my resume, built with LaTeX, Pandoc, Docker... |
6 | 6 |
|
7 |
| -```shell |
8 |
| -docker build -t latex-cv . |
9 |
| -docker run -v $(pwd):/latex_content latex-cv /bin/bash -c "make pdf" |
10 |
| -#docker run -v $(pwd):/latex_content --name latex-container latex-cv /bin/sh -c "make pdf" |
11 |
| -#docker cp latex-container:/latex_content/cv-piotr-kowalski.pdf output.pdf |
12 |
| -#docker remove /latex-container |
13 |
| -``` |
| 7 | +## Why? |
| 8 | +As many other developers, I really hate to write or update my resume. |
| 9 | +I've tried many different approaches, but I've never been satisfied with the result. |
| 10 | +Including new information, changing the format, or even modifying the order of the sections was always a pain. |
14 | 11 |
|
| 12 | +At some point, I decided to write my resume in LaTeX, |
| 13 | +but the more important thing was to automate the process of building the PDF file |
| 14 | +and extracting the information from a single source of truth. |
15 | 15 |
|
| 16 | +Also, I wanted to have a repository with my resume, so I could track the changes and share it with others, and |
| 17 | +at the same time show some of my skills as DevOps and Software Engineer here. |
16 | 18 |
|
17 |
| -## Install pre-requisites (Windows) |
| 19 | +So, not only the PDF generated in this repository is my resume, but also the repository itself. |
18 | 20 |
|
19 |
| -1. Install [MiKTeX](https://miktex.org/howto/install-miktex), a TeX |
20 |
| - distribution for Windows that includes a large number of major packages. |
| 21 | +As you can see in the commit history, it's a work in progress that started recently. |
| 22 | +So don't be too harsh with me :) It's NOT yet on version 1.0. |
21 | 23 |
|
22 |
| -2. Install an editor to edit and compile LaTeX documents: |
23 |
| - - [TexWorks](http://www.tug.org/texworks/) (comes with MiKTeX) |
24 |
| - - [TeXstudio](http://www.texstudio.org/) |
25 |
| - - [Texmaker](http://www.xm1math.net/texmaker/) |
| 24 | +## How? |
| 25 | +Apart from using some nice LaTeX templates, |
| 26 | +I've used [Pandoc](https://pandoc.org/) to convert the Markdown file to LaTeX. |
| 27 | +This way I can write my resume in the data.md file, and then generate the LaTeX file and the PDF when I change it. |
26 | 28 |
|
27 |
| -Once both the distribution and editor are installed, clone this repository |
28 |
| -using `git clone` and open the template.tex file in your editor. |
| 29 | +I've also used [Docker](https://www.docker.com/) to build the PDF file, |
| 30 | +so I (or anyone else) can build it without installing anything else. |
29 | 31 |
|
30 |
| -**Important**: Make sure to compile with XeLaTeX, not PDFLaTeX. |
31 |
| -You're good to go! |
| 32 | +At some point, I also decided I wanted a more visual to show my skills. |
| 33 | +Having the GitHub heatmap in mind, I decided to create a heatmap of my skills. |
| 34 | +I have created a simple Python script that generates eps file with the heatmap, and then I include it in the LaTeX file. |
32 | 35 |
|
33 |
| -## Install pre-requisites (Debian/Ubuntu) |
34 |
| -* texlive: `sudo apt-get install texlive` |
35 |
| -* texlive-xetex: `sudo apt-get install texlive-xetex` |
36 |
| -* texlive-lualatex: `sudo apt-get install texlive-luatex` |
37 |
| -* texlive-math-extra: `sudo apt-get install texlive-math-extra` |
38 |
| -* texlive-fonts-extra: `sudo apt-get install texlive-fonts-extra` |
39 |
| -* texlive-pstricks: `sudo apt-get install texlive-pstricks` |
40 |
| -* texmaker: `sudo apt-get install texmaker` |
| 36 | +## GitHub actions |
| 37 | +I have created some GitHub actions to automate the process of building the PDF file. |
41 | 38 |
|
42 |
| -## Build (Windows) |
| 39 | +### Docker image build |
| 40 | +To avoid building the docker image every time, I've created a GitHub action that builds the image and pushes it to GHCR. |
| 41 | +It's only triggered when the Dockerfile or requirements.txt changes. |
43 | 42 |
|
44 |
| -Open `.tex` file with `TexMaker` or `TexWorks` and compile using XeLaTeX |
| 43 | +### PDF build |
| 44 | +This is the main action. |
| 45 | +It is run on every push, and it uses the docker image built in the previous step to build the PDF file. |
| 46 | +After building the PDF file, it's uploaded as an artifact, so it can be downloaded from the Actions tab. |
45 | 47 |
|
46 |
| -## Build (Debian/Ubuntu) |
| 48 | +On release, the PDF file is also uploaded as a release asset. |
47 | 49 |
|
48 |
| - make all |
| 50 | +## How to build the PDF file locally? |
49 | 51 |
|
50 |
| -## FontAwesom support |
| 52 | +Clone this repository and run the following command in the root directory of the repository: |
| 53 | +```shell |
| 54 | +docker build -t latex-cv . |
| 55 | +docker run -v $(pwd):/latex_content --name latex-container latex-cv /bin/sh -c "make pdf" |
| 56 | +docker cp latex-container:/latex_content/cv-piotr-kowalski.pdf output.pdf |
| 57 | +docker remove /latex-container |
51 | 58 |
|
52 |
| -To enable fontawesome support, include the fontawesome package in the `.tex` file |
| 59 | +# If you don't need to copy the PDF file from the container, you can use this command instead |
| 60 | +docker run -v $(pwd):/latex_content latex-cv /bin/bash -c "make pdf" |
| 61 | +``` |
53 | 62 |
|
54 |
| - \usepackage{fontawesome} |
55 | 63 |
|
56 |
| -and compile the document using LuaLaTex |
57 | 64 |
|
58 | 65 | ## References
|
59 | 66 |
|
60 |
| -The elements comes from several templates, including: |
61 |
| - |
62 |
| -1. [Font Awesome Icons](https://faicons.com/) |
| 67 | +The initial idea for this repo came from the following repositories: |
| 68 | +1. [Ten Seconds CV](https://github.com/bitroniq/ten-seconds-cv) |
63 | 69 | 2. [Carmine Spagnuolo's Twenty Seconds Curriculum Vitae](https://github.com/spagnuolocarmine/TwentySecondsCurriculumVitae-LaTex)
|
64 |
| -3. [Carmine Benedetto's Smart Fancy LaTeX CV](https://github.com/neoben/smart-fancy-latex-cv) |
65 |
| -4. [Adrien Friggeri's Fancy CV](https://www.sharelatex.com/templates/52fb8c1f33621a613683ecad) |
66 |
| -5. [Harsh Gadgil opensorcer/Data-Engineer-Resume-LaTeX](https://github.com/opensorceror/Data-Engineer-Resume-LaTeX) |
67 |
| - |
68 |
| - |
69 |
| -## License |
70 |
| - |
71 |
| -> MIT License |
72 |
| -
|
73 |
| -> Copyright (c) 2019 Esteban Martinena |
74 |
| -
|
75 |
| -> Permission is hereby granted, free of charge, to any person obtaining a copy |
76 |
| -> of this software and associated documentation files (the "Software"), to deal |
77 |
| -> in the Software without restriction, including without limitation the rights |
78 |
| -> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell |
79 |
| -> copies of the Software, and to permit persons to whom the Software is |
80 |
| -> furnished to do so, subject to the following conditions: |
81 |
| -
|
82 |
| -> The above copyright notice and this permission notice shall be included in all |
83 |
| -> copies or substantial portions of the Software. |
84 |
| -
|
85 |
| -> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
86 |
| -> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
87 |
| -> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
88 |
| -> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
89 |
| -> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
90 |
| -> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
91 |
| -> SOFTWARE. |
| 70 | +3. [Harsh Gadgil opensorcer/Data-Engineer-Resume-LaTeX](https://github.com/opensorceror/Data-Engineer-Resume-LaTeX) |
0 commit comments