{"id":14063003,"url":"https://github.com/dwyl/dev-setup","last_synced_at":"2025-07-29T14:32:05.890Z","repository":{"id":38419187,"uuid":"41505511","full_name":"dwyl/dev-setup","owner":"dwyl","description":"✈️ A quick-start guide for new engineers on how to set up their Dev environment","archived":false,"fork":false,"pushed_at":"2024-10-02T13:42:13.000Z","size":64,"stargazers_count":81,"open_issues_count":38,"forks_count":21,"subscribers_count":194,"default_branch":"master","last_synced_at":"2025-03-30T10:35:02.946Z","etag":null,"topics":["development","development-environment","github"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/dwyl.png","metadata":{"files":{"readme":"readme.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2015-08-27T18:58:48.000Z","updated_at":"2025-03-20T11:14:55.000Z","dependencies_parsed_at":"2024-04-10T16:40:28.562Z","dependency_job_id":"c1a7daad-b47f-4fd7-a2b5-0288dc9a3689","html_url":"https://github.com/dwyl/dev-setup","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/dwyl/dev-setup","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dwyl%2Fdev-setup","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dwyl%2Fdev-setup/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dwyl%2Fdev-setup/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dwyl%2Fdev-setup/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/dwyl","download_url":"https://codeload.github.com/dwyl/dev-setup/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/dwyl%2Fdev-setup/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":267703051,"owners_count":24130463,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-07-29T02:00:12.549Z","response_time":2574,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["development","development-environment","github"],"created_at":"2024-08-13T07:02:58.619Z","updated_at":"2025-07-29T14:32:05.620Z","avatar_url":"https://github.com/dwyl.png","language":null,"readme":"\u003cdiv align=\"center\"\u003e\n\n# A Guide to Setting Up Your Dev Environment\n\n![tianyi-ma-WiONHd_zYI4-unsplash](https://user-images.githubusercontent.com/194400/180770906-938c8083-28fb-4c03-872f-3a636376f15f.jpg)\n\n[![contributions welcome](https://img.shields.io/badge/contributions-welcome-brightgreen.svg?style=flat-square)](https://github.com/dwyl/dev-setup/issues)\n[![HitCount](https://hits.dwyl.com/dwyl/dev-setup.svg?style=flat-square)](https://hits.dwyl.com/dwyl/dev-setup)\n\n\n\u003c/div\u003e\n\n- [A Guide to Setting Up Your Dev Environment](#a-guide-to-setting-up-your-dev-environment)\n- [Why? 🤷‍♀️](#why-️)\n- [What?](#what)\n- [Who?](#who)\n- [How?](#how)\n  - [Web Browsers](#web-browsers)\n  - [Git + GitHub](#git--github)\n    - [2 Factor Authentication (2FA)](#2-factor-authentication-2fa)\n    - [Basic Git setup](#basic-git-setup)\n    - [Learn how to use Git + GitHub](#learn-how-to-use-git--github)\n- [Mac 🍏](#mac-)\n  - [PostgresApp](#postgresapp)\n  - [PGAdmin](#pgadmin)\n  - [Rectangle](#rectangle)\n    - [Keyboard Shortcuts](#keyboard-shortcuts)\n  - [Homebrew](#homebrew)\n  - [`iTerm`](#iterm)\n    - [Themes](#themes)\n- [_Everyone_](#everyone)\n  - [Text Editor](#text-editor)\n    - [Basic text editor setup](#basic-text-editor-setup)\n  - [How to connect Github to Atom step-by-step](#how-to-connect-github-to-atom-step-by-step)\n    - [Our most used text editor keyboard shortcuts](#our-most-used-text-editor-keyboard-shortcuts)\n- [Linux 🐧](#linux-)\n  - [Text Editor](#text-editor-linux)\n    - [Vim](#vim)\n    - [Neovim](#neovim)\n    - [Visual Studio Code (aka VS Code)](#vs-code)\n  - [System Fetch](#system-fetch)\n    - [screenfetch](#screenfetch)\n    - [neofetch](#neofetch)\n\n\n# Why? 🤷‍♀️\n\nSetting up a software engineering computer \ncan take a _long_ time. ⏳ \u003cbr /\u003e\nWe need to streamline the process\nso that we can start work as quickly as possible. 🏁\u003cbr /\u003e\nThis doc outlines all the steps we take to setup \nour typical system. 💻\n\nIf you find it helpful,\nplease \n[⭐](https://github.com/dwyl/dev-setup/stargazers) \nthe repo\nto let us know.\nThanks.\n\n\n# What?\n\nThis repo contains the tools we use.\n\nIf you have a tool or setup step\nyou think we should include/use,\n[please open an issue](https://github.com/dwyl/dev-setup/issues)\nto let us know! 🙏\n\n\u003e _Note:_ The intention is **not** to include every fancy script, \ntip and trick under the sun, \nthis is about **basic setup and getting going when you're new** \nand already have a _steep_ learning curve!\n\n# Who?\n\n1. People who are **`new`** to software engineering.    \nParticularly people who have learnt online \nusing inbuilt browser-based editors and tools \n(often the case in online courses) \nand have **not set up their own environment** before.\n\n2. People @dwyl who have just got a new computer\nand need to set it up as quickly as possible\nso they can get work done. \n\n\n\u003e **Note**: @dwyl we use a specific \n[technology stack](https://github.com/dwyl/technology-stack)\nthat includes \n[PostgreSQL](https://github.com/dwyl/learn-postgresql#installation) \nand \n[Elixir](https://github.com/dwyl/learn-elixir#how)\n\u003e **Installing** most of this software \n[is optional](https://github.com/dwyl/dev-setup/issues/3),\nbut it does make you more effective so we highly recommend it.  \nThis repo includes some recommendations of things we favour and use @dwyl.\n\n# How? \n\nEnsure you have a decent internet connection \nwhen setting up your machine,\nseveral **gigabytes** will be downloaded.\n\n\u003e **Note**: if you lack a good internet connection,\n\u003e simply skip downloading the browser(s) and other larger Apps.\n\u003e But we are _assuming_ that if you are reading this,\n\u003e you have _access_ to decent bandwidth to be a Developer/Engineer.\n\u003e Please, share your experience if not!\n\u003e We are very curious to hear from bandwidth-constrained people! 🙏\n\u003e We would like to formulate a \"Low Cost / Bandwidth\" version \n\u003e of this doc for use on a Raspberry Pi or other lower cost computer.\n\u003e We could even create a pre-built SD card with everything required. 💭\n\n## Web Browsers\n\nThe reason the word \"browsers\" is _plural_ is simple:\nhaving _multiple_ web browsers \nallows you to segment your use of each one\nfor a specific purpose.\ne.g:\n\n1. **`Safari`** - the default browser on Mac. \n   Keep it \"stock\" (no plugins/themes), \n   use it for UAT testing web apps \n   to know what they will look \u0026 feel like \n   to people who own Macs \n   but don't bother to download a different browser.\n   Safari is good for personal things too as it has good privacy and speed.\n2. **`Google Chrome`**: \n   [google.com/chrome](https://www.google.com/chrome/)\n   The baseline for web development. Great Dev Tools, profiling etc.\n3. **`Firefox`**: \n   [mozilla.org/firefox](https://www.mozilla.org/en-US/firefox/new/)\n   We use Firefox for testing our Web apps because\n   it has the best support for Web Standards.\n   It's fast, free and surfaces potential bugs \n   in our code better than other browsers.\n\nIn addition to these \nthere are _many_ other browsers you can install/use,\nfor example:\n\n4. **`Brave`**: \n   [brave.com/download](https://brave.com/download/)\n   Based on Chrome but with built-in ad-blocker.\n   Use Brave to watch YouTube lectures/tutorials without Ads.\n5. **`Google Chrome Canary`**: \n   [google.com/chrome/canary/](https://www.google.com/chrome/canary/)\n   Chrome but with all latest features.\n6. **`Firefox Developer Edition`**: \n   [mozilla.org/firefox/developer/](https://www.mozilla.org/en-US/firefox/developer/)\n   Useful for debugging and testing web apps.\n   We have it installed as a backup browser\n   for when we need to test multiple clients concurrently.\n7. **`Microsoft Edge`**: \n   [microsoft.com/edge](https://www.microsoft.com/en-us/edge)\n   Based on Google Chrome but with a few Microsoft enhancements.\n\nAs noted in\n[#9](https://github.com/dwyl/dev-setup/issues/9#issuecomment-1193409980)\nwe have several web browsers installed and use them for specific purposes:\n\n\u003cimg width=\"475\" alt=\"image\" src=\"https://user-images.githubusercontent.com/194400/180669042-91cd806d-2a3b-488a-b9cd-1ca0e8d8f20d.png\"\u003e\n\nGiven that Microsoft now owns GitHub\nand can read _everything_ we do on the platform\n(_both `public` and `private`..._)\nwe use **`Edge`** for all our GitHub\ninteractions (e.g. reading notifications, responding to issues/questions, etc.)\n**`Edge`** is our \"GitHub browser\".\n\nYou are free to come up with your own system,\nbut having multiple browsers and segmenting your use\ncan mean you have fewer tabs in your \"work\" browser\nand can easily separate any personal stuff.\n\n\n## Git + GitHub\n\nWe use Git and \n[Github](https://en.wikipedia.org/wiki/GitHub) \nexclusively for our version control \nand to share our work with the world.   \nUnderstanding the \n[difference between the two](https://www.codefellows.org/blog/git-and-github-what-s-the-difference) \nis also helpful.\n\nIf you don't _already_ have a GitHub account,\nsign up for one: \n[github.com/join](https://github.com/join)\n\n### 2 Factor Authentication (2FA)\n\n[2FA](https://help.github.com/en/github/authenticating-to-github/about-two-factor-authentication)\nprotects your Github account\nand also any organisations you are a member of\nfrom malicious intent.\n\n![setup-2factor-auth](https://user-images.githubusercontent.com/4185328/79356313-b16e9f80-7f36-11ea-8645-d0ee1ea36853.png)\n\n\n**Next steps?** If you want to \n[contribute to dwyl projects](https://github.com/dwyl/contributing), \nyou can easily do so _without_\nknowing _any_ of our  \n[tech stack](https://github.com/dwyl/technology-stack).\nSimply use the \n[App](https://github.com/dwyl/app)\nand **open issues whenever you have questions**!\n\n\n### Basic Git setup   \n\nFollow the official \n[**set up Git guide**](https://help.github.com/articles/set-up-git/)\nto get it working on your computer.\n\nSetup \n[**ssh authentication**](https://help.github.com/articles/set-up-git/#connecting-over-ssh) \nas it is more secure \nand means you _won't have to type in your password \nevery time you push to GitHub.\n\n\u003e **Note**: This also means that when you _clone_ a repo, \n\u003e you'll need to use the **SSH clone URL** \n\u003e (thanks [@tsop14](https://github.com/tsop14) for the screenshot!)\n\n![change-to-ssh](https://user-images.githubusercontent.com/21698271/45860770-00daf280-bd37-11e8-92f8-34bb1ddf8152.png)\n\n### Learn how to use Git + GitHub\n\nThere are many resources online:\n[start-here#git](https://github.com/dwyl/start-here#git--github)\n\nAlthough [Git has a desktop client](https://desktop.github.com/), \nwe **recommend that you learn to use it on the command line**. \nThis is _much_ faster in the long run and will serve you well\nwhen you need to understand how things work.\n\n\n# Mac 🍏\n\nThis section is _specific_ to Mac computers.\nSkip it if you are using Linux or \n[Windows](https://www.google.com/search?q=stop+hitting+yourself\u0026tbm=isch).\n\n## PostgresApp \n\nWe find PostgresApp to be the easiest way \nto manage PostgreSQL on Mac.\nIt gives us a basic graphical user interface (GUI)\nand menu bar icon that informs us of the status of the DB.\n\nDownload: https://postgresapp.com/\n\n## PGAdmin\n\nPostgres \nhttps://www.pgadmin.org/\n\n\n## Rectangle\n\n[Rectangle](https://rectangleapp.com/) \nis window manager/tiler for Mac,\nit gives you keyboard shortcuts for moving/organising your Apps/Windows: \n[rectangleapp.com](https://rectangleapp.com/)\n\n\u003cimg width=\"1115\" alt=\"image\" src=\"https://user-images.githubusercontent.com/194400/180993778-01d42389-9d9c-497c-a469-968e220ec3c7.png\"\u003e\n\n\u003e **Note**: Rectangle will request/require \n\u003e \"accessibility\" permissions to control your windows.\n\u003e This is normal.\n\n### Keyboard Shortcuts\n\nUsing Rectangle is fastest via the keyboard shortcuts:\n\n\u003cimg width=\"884\" alt=\"image\" src=\"https://user-images.githubusercontent.com/194400/180995347-d7838081-9a84-49c6-b45c-0f251e44c719.png\"\u003e\n\nYou can add your own shortcuts if you prefer.\nWe haven't found the need to yet.\n\n\n## Homebrew\n\nIf you are setting up a Mac,\nyou will need to install homebrew \n[brew.sh](https://brew.sh),\nthe package manager that will download and manage\nseveral other open source software packages.\n\nInstall with the following command in your terminal:\n\n```sh\n/bin/bash -c \"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)\"\n```\n\n## `iTerm`\n\nThe default terminal emulator on Mac is _OK_ for basic tasks... \u003cbr /\u003e\nWe find that \n[**`iTerm`**](https://www.iterm2.com/) \nis _considerably_ better UX.\ne.g: **`iTerm`** allows screen splitting:\n\n![iterm-screen-splitting](https://cloud.githubusercontent.com/assets/4185328/9831158/56d8cb90-5943-11e5-99ec-9fb1a5907f8a.png)\n\nAs with Web Browsers, \nit doesn't _hurt_ to have more than one Terminal \non your Mac. \n\nDownload: https://iterm2.com\n\n### Themes\n\nThere are _many_ themes \nwhich you may have heard of \n(like [Oh My Zsh](https://ohmyz.sh/)) \nthat aim to add some functionality \nand shortcuts to your terminal. \n**We _don't_ recommend** \nyou use any terminal themes \nwhen you're starting out\nbecause they are a _distraction_\nfrom the content/code you are crafting.\n\nHowever, once you know what you're doing in the terminal, \nyou can consider _enhancing_ your terminal with themes.\nThere are _many_ to choose from:\n[iterm2colorschemes.com](https://iterm2colorschemes.com/)\n\n\n\u003cbr /\u003e\n\n# _Everyone_\n\nThe following applies to all people \nregardless of their operating system\n(Linux, Mac \u0026 Windows)\n\n## Text Editor\n\nIt's your choice which text editor you use, \nbut you will inevitably need (at least) one editor.\nAt the time of writing, \n`@dwyl` we use \n[Atom](https://atom.io/) \n(Open Source, Electron/NodeJS based editor).\n\nThere are a wide range of text editors \nand integrated development environment (IDEs)\navailable.\n\nWe tend to use:\n\n+ Atom: https://atom.io Open Source and has many plugins for language and framework support.\n  Download and install it even if you only use it as a \"backup\" editor.\n  VSCodium https://vscodium.com the Open Source version of VS Code. All Plugins work as expected\nbut no Tracking from Microsoft.\n+ VS Code: https://code.visualstudio.com as a backup or read-only viewer when we are working on multiple projects concurrently.\n+ Sublime Text: [sublimetext.com](https://www.sublimetext.com) - fast and free-ish \n  (you will be reminded to purchase a license ... but the license is perpetual not annual!)\n  \n  \n\n\n### Basic text editor setup\n\n**Set up** [**_soft tabs_**](https://opensourcehacker.com/2012/05/13/never-use-hard-tabs/) (indentation) \u003cbr /\u003e\nYou can usually set this up in the _Preferences_ or _Settings_ \nof your favourite text editor \nso you never have to think about it again \n(example below for [Atom](https://atom.io/)): \n\n\u003cimg width=\"507\" alt=\"atom-soft-tab-preferences-menu\" src=\"https://cloud.githubusercontent.com/assets/4185328/9154618/a6598690-3e91-11e5-939b-2c03cf3c7ffc.png\"\u003e     \n\n\n+ **Set up a guide (or line) to show on your page at the 80 character mark** so you know [when you go past 80 characters (or columns) on a single line](https://programmers.stackexchange.com/questions/604/is-the-80-character-limit-still-relevant-in-times-of-widescreen-monitors)\n  + Useful for _readability_, particularly in code snippets where you would otherwise end up with a scroll bar\n  + You should also be able to set this up in your favourite text editor's _Preferences_ (example below again on Atom editor - note, I also like to set up my editor to soft wrap at this line length so I can read other people's code more easily)    \n  \u003cimg width=\"511\" alt=\"80-character-line-guide-setup\" src=\"https://cloud.githubusercontent.com/assets/4185328/9826015/45796748-58cf-11e5-8a5d-db7350a8eb82.png\"\u003e\n\n## How to connect Github to Atom step-by-step\n\nFirst of all you need to create a Github Account and then create a new repository, name it as you wish.\u003c/br\u003e\n\nNow you have a link to your repository and instructions to how to create a new repository in the command line.\u003c/br\u003e\nNow go to Atom and press cmd+SHIFT+P and you enter Github:clone and then paste your link.\n\n![Screen Shot 2020-01-12 at 22 41 04](https://user-images.githubusercontent.com/27420533/72227070-45277d00-3590-11ea-90f9-6e78998bf30e.png)\n\nA couple a seconds later you have your repository on the left side of the screen.\u003c/br\u003e\n\n![Screen Shot 2020-01-12 at 22 42 59](https://user-images.githubusercontent.com/27420533/72227087-638d7880-3590-11ea-920e-643b8433d193.png)\n\n\nThe next thing to do is authorize Github for atom so go to github.atom.io/login.\u003c/br\u003e\nJust make the login with your information and copy the GitHub token after having your GitHub token copied go to Atom to the GitHub tab in the right lower corner and you will see a login just paste your token there and now you are connected to GitHub.\u003c/br\u003e\n\nSo now if you create a file and edit with your own text you can upload the file to GitHub by going to the git tab and Stage the changes in your file you have to give a commit message the first time you edit the file.\nThen click on Commit to master.\n\n\n![Screen Shot 2020-01-12 at 23 21 55](https://user-images.githubusercontent.com/27420533/72227281-86209100-3592-11ea-96a2-06ba543fa6a6.png)\n\n\nNow click on master and then on new branch and call it whatever you want then click on publish.\nYou will have to enter your credentials again to validate those changes.\n\n![Screen Shot 2020-01-12 at 23 24 13](https://user-images.githubusercontent.com/27420533/72227295-bc5e1080-3592-11ea-95e3-524c86a80757.png)\n\n\nIf you go on your created repository and press F5 you should see those changes.   \n\n\nInstall at least a [linter](https://stackoverflow.com/questions/8503559/what-is-linting) in your editor.\n\n### Our most used text editor keyboard shortcuts  \nEach person's most used shortcuts will vary of course, but here are some of the things we suggest **learn the keyboard shortcuts for:**\n  + Select the current word (usually `cmd + D`)\n  + Delete current line (usually `ctrl + shift + K`)\n  + Indenting a line or a whole block of code at once\n  + [Column editing](https://atom.io/docs/v1.0.11/using-atom-editing-and-deleting-text#multiple-cursors-and-selections)\n  + [Moving a line](https://atom.io/docs/v1.0.11/using-atom-editing-and-deleting-text#basic-manipulation) or block of code up and down the page\n  + Changing the [syntax highlighting](https://en.wikipedia.org/wiki/Syntax_highlighting) when required\n  + Toggle between the different views (e.g. hide/show the file tree view to gain more screen real estate)\n  \n\n\u003cbr /\u003e\n\n# Linux 🐧\nThis section is _specific_ to Linux computers.\nSkip it if you are using Mac or \n[Windows](https://www.google.com/search?q=stop+hitting+yourself\u0026tbm=isch).\n\n## Text Editor\nIt's your choice which text editor you use, but you will inevitably need (at least) one editor. At the time of writing, `@lnxwizard` we use Visual Studio Code (aka VS Code).\n\n### Vim\nVim is a free and open-source, screen-based text editor program. It is an improved clone of Bill Joy's vi. Vim's author, Bram Moolenaar, derived Vim from a port of the Stevie editor for Amiga and released a version to the public in 1991. Vim is designed for use both from a command-line interface and as a standalone application in a graphical user interface. Vim comes pre-installed on some Linux distributions.\n\nArch Linux, Manjaro:\n```shell\nsudo pacman -S vim\n```\n\nDebian, Ubuntu, Linux Mint:\n```shell\nsudo apt install vim\n```\n\nCentOS, Fedora, RHEL:\n```shell\nsudo dnf install vim\n```\n\nOpenSuse:\n```shell\nsudo zypper install vim\n```\n\n### Neovim\nNeovim is a project that seeks to aggressively refactor Vim in order to:\n  - Simplify maintenance and encourage contributions\n  - Split the work between multiple developers\n  - Enable advanced UIs without modifications to the core\n  - Maximize extensibility\n\nArch Linux, Manjaro:\n```shell\nsudo pacman -S neovim\n```\n\nDebian, Ubuntu, Linux Mint:\n```shell\nsudo apt-get install neovim\n```\n\nFedora:\n```shell\nsudo dnf install -y neovim python3-neovim\n```\n\nCentOS, RHEL:\n```shell\nyum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm\nyum install -y neovim python3-neovim\n```\n\nOpenSuse:\n```shell\nsudo zypper in neovim\n```\n\n### Visual Studio Code (aka VS Code)\nVisual Studio Code, also commonly referred to as VS Code, is a source-code editor made by Microsoft with the Electron Framework, for Windows, Linux and macOS. Features include support for debugging, syntax highlighting, intelligent code completion, snippets, code refactoring, and embedded Git. Users can change the theme, keyboard shortcuts, preferences, and install extensions that add functionality. \n\nArch Linux, Manjaro:\n```shell\nsudo pacman -S code\n```\n\nDebian, Ubuntu, Linux Mint:\n```shell\nsudo apt install code\n```\n\nCentOS, RHEL, Fedora:\n```shell\nsudo dnf install code\n```\n\n## System Fetch\nSystem Fetch, is very useful tools for extracting essential details on your Linux system OS.\n\n### screenfetch\nscreenfetch is a \"Bash Screenshot Information Tool\". This handy Bash script can be used to generate one of those nifty terminal theme information + ASCII distribution logos you see in everyone's screenshots nowadays. It will auto-detect your distribution and display an ASCII version of that distribution's logo and some valuable information to the right. There are options to specify no ASCII art, colors, taking a screenshot upon displaying info, and even customizing the screenshot command! This script is very easy to add to and can easily be extended. It’s very easy to use. Simply run the following command in terminal:\n\nUsage:\n```shell\nscreenfetch\n```\n\nArch Linux, Manjaro:\n```shell\nsudo pacman -S screenfetch \n```\n\nDebian, Ubuntu, Linux Mint:\n```shell\nsudo apt install screenfetch \n```\n\nFedora:\n```shell\nsudo dnf install screenfetch\n```\n\n### neofetch\nNeofetch is a system information tool written in the Bash shell scripting language. On the left side is always a logo of the distribution, rendered in ASCII art. Unlike a system monitor, the tool only features a static display of the computer's basic hardware and software configurations and their versions, typically operating system, the host (namely the technical name of the machine), uptime, package managers, the shell, display resolution, desktop environment, window manager, themes and icons, the computer terminal, CPU, GPU, and RAM. Neofetch can also display images on the terminal with w3m-img in place of the ASCII logo art. Neofetch hasn't been updated and appears to be inactive since about December 9th, 2021. It’s very easy to use. Simply run the following command in terminal:\n\nUsage:\n```shell\nneofetch\n```\n\nArch Linux, Manjaro:\n```shell\nsudo pacman -S neofetch \n```\n\nDebian, Ubuntu, Linux Mint:\n```shell\nsudo apt install neofetch \n```\n\nFedora:\n```shell\nsudo dnf install neofetch\n```\n","funding_links":[],"categories":["Others"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdwyl%2Fdev-setup","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdwyl%2Fdev-setup","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdwyl%2Fdev-setup/lists"}