Setting Up Fedora Workstation for Software Development

Table of Contents

A guide to setting up Fedora Workstation for DevOps and software development. This is current for Fedora 40.

Installation #

Enable Disk Encryption #

Enable disk encryption when prompted during the setup process.

Disk encryption is the only protection against anyone with physical access to your computer. All other security measures will be completely bypassed if someone with physical access either restarts your computer with a bootable pen drive, or removes the internal hard drive and attaches it to another computer.

Set a Password for UEFI or BIOS #

Once you have installed Fedora, restart your computer, and press the function key to enter the setup menu for the UEFI firmware, or BIOS. Change the boot options so that the computer only boots from the hard drive, and set both a user password for startup, and an administrator password to protect the firmware menus.

Do This First #

Log in once, run the Software utility, and ensure that the operating system has the latest updates. After all of the updates have been applied, restart the computer.

User Settings #

Select Settings > Privacy & Security. Check these settings:

Always set Thunderbolt Access to Only USB and Display Port devices can attach. unless you know that you need to connect other types of devices to your computer.
Set Location > Automatic Device Location to off.
Adjust the File History & Wastebasket settings if you need to.

Installing Desktop Applications with Flatpak #

Flatpak is now the standard for desktop software packages on Linux. Flatpak offers newer versions of products than Fedora itself, as well as providing software that is not available from Fedora RPM repositories, such as Slack.

The Software utility uses the Flathub service for Flatpak packages. Software shows both Flatpak and RPM packages for apps. If a Flatpak is available, use that package rather than RPM.

Install code editors and IDEs with RPM packages, not Flatpak. Currently, security features for Flatpak may prevent application plugins from working correctly.

Useful software that you can install as Flatpaks include:

Beekeeper Studio for working with databases
Draw.io for drawing diagrams
Joplin for note-taking

Setting Up for Development #

Text Editors #

Fedora includes the command-line editor nano and a small version of vim with a limited set of features, as well as a desktop text editor with basic support for programming. Add the code editors or IDEs that you would prefer to use.

If you do not have a preferred editor, consider using a version of Visual Studio Code. To work with a modern Vim editor, install Neovim.

Visual Studio Code #

Visual Studio Code is a powerful desktop editor for programming, with built-in support for version control and debugging. The large range of extensions for Visual Studio Code enable it to work with every popular programming language and framework. It is available free of charge.

The Microsoft releases of Visual Studio Code are proprietary software with telemetry enabled by default, and download extensions from a proprietary Microsoft app store. if you have issues or concerns about the Microsoft releases, use the RPM packages that are provided by the vscodium project.

Extensions may fail if you use the Visual Studio Code OSS Flatpak.

Neovim #

If you would like a modern Vim editor with a good default configuration, set up Neovim. To install Neovim, enter this command in a terminal window:

sudo dnf install neovim

Setting The EDITOR Environment Variable #

Whichever text editor you choose, remember to set the EDITOR environment variable in your ~/.bashrc file, so that this editor is automatically invoked by command-line tools like your version control system. For example, put this line in your profile to make Visual Studio Code the favored text editor:

export EDITOR="code"

Configuring Git #

Fedora Workstation includes the Git version control system. Always set your details for Git before you create or clone repositories on a new system. This requires two commands in a terminal window:

git config --global user.name "Your Name"
git config --global user.email "you@your-domain.com"

The global option means that the setting will apply to every repository that you work with in the current user account.

To enable colors in the output, which can be very helpful, enter this command:

git config --global color.ui auto

Add a GPG key to Git before you commit to shared projects. The next section explains how to do this.

Using a GPG Key #

Always use GPG to sign the commits that you make in code repositories, especially for shared projects like Open Source software. This means that each commit can be linked to the author.

To create a GPG key, run the gpg command in a terminal window. For example:

gpg --full-gen-key

GPG will prompt you for several options. Use these values:

Select the RSA and RSA algorithm
Choose a key length of 4096
Accept the default option to have no expiration date for your key
Enter the same email address that you will use for code hosting sites, such as Codeberg or GitHub

Once you have created a GPG key, configure Git to use it.

First get the ID of the key:

gpg --list-secret-keys --keyid-format=long

This displays an output like this:

pub   rsa4096/C36CB86CB86B3716 2022-01-18 [SC]
      BF18AC2876178908D6E71267D36CB86CB86B3716
uid                 [ultimate] Anne Example <anne@example.org>
sub   rsa4096/B7BB94F0C9BA6CAA 2022-01-18 [E]

In this example, the key ID is C36CB86CB86B3716.

Next, configure Git to use this key:

git config --global user.signingkey C36CB86CB86B3716
git config --global commit.gpgsign true

Finally, add your GPG key to your accounts on code hosting services that you use:

If you use multiple code hosting services for your projects, use the same GPG key for all of them. This ensures that copies of the same commits can be verified everywhere.

Setting Up A Directory Structure for Projects #

To keep your projects tidy, I would recommend following these guidelines. They may seem slightly fussy, but they pay off when you have many projects, some of which are on different version control hosts.

First create a top-level directory with a short, generic name like repos. For each repository host, create a subdirectory in repos. Add a subdirectory that matches your username. The final directory structure looks like this:

repos/
    codeberg.org/
        my-codeberg-username/
            a-project/
    gitlab.com/
        my-gitlab-username/
            a-project/
            another-project/

Creating SSH Keys #

You may use SSH to access Git repositories or remote UNIX systems. Fedora includes the standard OpenSSH suite of tools.

To create an SSH key, run the ssh-keygen command in a terminal window. For example:

ssh-keygen -t ed25519 -C "Me MyName (MyDevice) <me@mydomain.com>"

Create a separate SSH key for each set of systems that you access.

Setting Up Homebrew #

The Homebrew package management system provides the latest versions of tools. Always use Homebrew to install tools that are frequently updated, like the AWS CLI and Trivy.

Follow the instructions on the Homebrew site to install it.

To check that Homebrew is installed correctly, run this command in a terminal window:

brew doctor

To update the index of available packages, run this command in a terminal window:

brew update

Working with Programming Languages #

Avoid using the Fedora packages for programming languages. Instead, use version manager tools. These enable you to install the correct version of the required programming language and dependencies for each of your projects. Use Homebrew to install version manager tools.

Use pyenv for Python and rustup for Rust. The standard go tool manages versions of Go. If you work with Terraform or OpenTofu, use tenv. Consider using the mise version manager for JavaScript, as it provides a consistent set of features for managing many tools, including Node.js, Deno and Bun.

Alternatively, Fedora Workstation includes toolbx to help you manage container environments for developing your projects. Container environments also enable you to have separate versions of software for each of your projects.

Using Version Managers #

To install a version manager, use the process that the documentation for the product recommends.

If you use a version manager, you will also need to install compiler tools for the C programming language. Installations of Python, Node.js and other languages use GCC to compile components that are written in C. To provide GCC use the Fedora packages for GCC:

sudo dnf install gcc

We use the GCC compiler for this purpose because it is compatible with the widest range of C code. If you are developing your own C code, consider using the Clang compiler for your project.

Terraform and OpenTofu #

Use the tenv version manager to install versions of Terraform and OpenTofu. To install tenv with Homebrew, run this command in a terminal window:

brew install tenv cosign

Always install cosign along with tenv. If cosign is present, tenv automatically uses it to carry out signature verification on the binaries that it downloads.

Avoid Using The System Python Installation #

Fedora includes an installation of Python 3, which is used by system tools. Avoid using this system installation yourself. Instead, manage your own installations of Python with containers or version managers, as explained in the previous section.

Working with Containers #

Fedora Workstation automatically has support for running containers with Podman. This provides the features of Docker for running container images. It also includes toolbx, which uses containers to manage environments for developing your projects.

To use a graphical interface for working with containers, add Podman Desktop to your system. To install Podman Desktop, go to Software, search for Podman Desktop, select the entry from the list, and choose Install.

To create container images, install buildah. This command-line tool provides the same features as Docker for building container images.

Podman #

Podman replaces Docker for running container images, and also has additional features to integrate better with both the Linux operating system and Kubernetes. For example, you can run Podman containers as standard system services.

Podman accepts the same syntax as the docker command-line tool, and will read Dockerfiles. Both Docker and Podman use the OCI image format, so that images created either product will work with the other. By default, Podman will check the Docker public registry for container images, as well as Quay registries.

For convenience, define a shell alias in your .bashrc file:

alias docker="podman"

This will redirect any call to Docker, so that it uses Podman instead.

The Usage Transfer page lists Docker commands, and the equivalents for Podman. This article explains the relationship between Podman, Buildah and Docker in more detail.

Use pods to run groups of containers. This feature of Podman replaces docker-compose.

If you need to run existing Docker Compose configurations, install podman-compose:

sudo dnf install podman-compose

The podman compose subcommand uses podman-compose to substitute for Docker Compose.

This enables you to convert Docker Compose configurations into Podman pod definitions at a later time. Use pods to benefit from the features of Podman, such as systemd integration and the facility to generate Kubernetes configurations from pod definitions.

Working with Virtual Machines #

Fedora Workstation installs GNOME Boxes by default, to enable you to create and manage virtual machines. GNOME Boxes provides a graphical interface for the standard KVM and QEMU software. You can also use these tools directly on the command-line.

SQL Databases #

Consider using containers to provide the database services for your Web applications. This will enable you to use different versions of the database servers for different projects, and ensure that you are running the same versions as the database instances on your production systems.

If you prefer to install services directly on to your workstation, Fedora provides packages for PostgreSQL and MariaDB. If you need a database server that is compatible with MySQL, install MariaDB. Otherwise, PostgreSQL is often a better choice for new applications.

Installing PostgreSQL #

To install PostgreSQL using dnf, enter these commands in a terminal window:

sudo dnf install postgresql-server
sudo postgresql-setup --initdb
sudo systemctl enable postgresql
sudo systemctl start postgresql

These commands install the server, the command-line tools, and the client libraries that are needed to compile adapters for programming languages.

To create a user account for yourself in PostgreSQL with administrative rights, enter this command in a terminal window:

sudo su - postgres
createuser -s YOU
exit

Replace YOU with the username of your account on Fedora.

The -s option means that your new PostgreSQL account is a superuser, with unlimited rights over the databases. Once you have a superuser account, you may use tools like createuser or log in to databases without using sudo or the -U option.

For example, to create an extra user account that is not a superuser:

createuser EXTRA-ACCOUNT

Replace EXTRA-ACCOUNT with the username of the new account.

Refer to the Fedora documentation for more information on working with PostgreSQL.