Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/zbhavyai/fedora-setup
Setting up development environment on a Fedora Workstation
https://github.com/zbhavyai/fedora-setup
bash dnf docker dotfiles eclipse flatpak git gnome-terminal intellij-idea podman python ssh vim virtualbox vscode
Last synced: 2 months ago
JSON representation
Setting up development environment on a Fedora Workstation
- Host: GitHub
- URL: https://github.com/zbhavyai/fedora-setup
- Owner: zbhavyai
- License: mit
- Created: 2022-04-06T01:23:52.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-11-14T18:53:34.000Z (3 months ago)
- Last Synced: 2024-11-14T19:39:58.582Z (3 months ago)
- Topics: bash, dnf, docker, dotfiles, eclipse, flatpak, git, gnome-terminal, intellij-idea, podman, python, ssh, vim, virtualbox, vscode
- Language: Shell
- Homepage:
- Size: 455 KB
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Fedora Workstation Setup
Welcome to the guide for setting up a development environment on a new [Fedora Workstation](https://fedoraproject.org/workstation/) with GNOME DE. This guide aims to streamline the setup process, automating certain tasks for my own convenience. This also serve as my dotfiles repository.
## What's automated
- Package installation and removal using `dnf`
- Font management, including installation and removal
- Installation of Google Chrome
- Installation of some Flatpak applications
- Update key bindings for the GNOME Shell
- Configuration of essential configuration files:
- `.bashrc`
- `.gitconfig`
- `.vimrc`
- SSH configuration for seamless remote access
- Installation of VS Code and some extensions
- Some miscellaneous settings like
- Tweak to ignore lid switch behavior
- App folders in the GNOME shell
- Interface settings like icon theme, fonts, color theme, etc.
- Customizing preferences for GNOME apps like GNOME Text Editor, Nautilus, and Terminal## What's not automated
Certain software packages or configurations tailored to specific needs won't be automatically set up - like [konsole](./konsole/) and [pgadmin](./postgres/) which I don't need on all the machines. This includes software that isn't universally required or configurations that demand manual intervention.
## How to use
To begin the setup process, simply execute the [setup.sh](setup.sh) script. You may be prompted to enter your password, as some commands require `sudo` privileges.
```shell
./setup.sh
```