Skip to content

ottenwbe/developer-environment-setup

Repository files navigation

developer-environment-setup

This ansible playbook is used by me to automate the setup of my Linux developer machines. If you frequently reinstall your system, you know why these scripts had been created. Therefore, this repository will be updated whenever I setup a new machine (commits to master).

Supported Linux Distributions

Right now the only tested Distributions are:

  • Fedora 33
  • Fedora 34

Structure

.
├── bootstrap_local.sh  // Script to bootstrap the ansible environment before executing the playbook
├── site.yml            // Playbook that wraps all tasks, roles, ...
├── ... 
├── roles/              // Roles to be executed by the playbook
│   ├── common          // Installation of common tools, external repos (rpm-fusion...), etc. 
│   ├── user            // Creation of users
│   ├── zsh             // Installation of zsh for each user
│   ├── cpp             // Everything needed for C(pp) development
│   ├── go              // Everything needed for Golang development
│   ├── java            // Everything needed for Java development
│   ├── python          // Everything needed for Python development
│   └── ruby            // Everything needed for Ruby development       
└── test/               // Test the playbook in docker images
    └── docker/

Usage

First of all, clone this repository.

git clone https://github.com/ottenwbe/developer-environment-setup.git

The bootstrap_local.sh script installs ansible as a prerequisite for executing the playbook. On a local Fedora installation where ansible is not installed the playbook can be executed as follows:

sh bootstrap_local.sh hosts <your user> Fedora

On a local Linux installation where ansible is installed the playbook can be executed as follows:

ansible-playbook -i hosts site.yml --connection=local --extra-vars '{"users": ["your user"]}' --ask-become-pass

Go Specific Details

You can specify a specific go version to install.

"go_version": "1.17.1.linux-amd64"

Testing

The playbook can be tested in a Docker container---more or less.

Docker

NOTE: On an SELinux, i.e., Fedora, first execute the following command in the root directory of the project.

chcon -Rt svirt_sandbox_file_t "${PWD}"

On a non SELinux you can simply build a docker image and execute the playbook in a container. Replace one of the 'testuser's' with a username that suits you and run the following commands:

docker build --file=test/docker/Dockerfile.fedora --build-arg "FEDORA_VERSION=33" --tag=fedora33:ansible test/docker
docker run --name=test-fedora --volume="${PWD}":/home/ansible:ro fedora33:ansible ansible-playbook -i /home/ansible/test/docker/test_hosts /home/ansible site.yml --connection=local --become --extra-vars '{"users": ["testuser1","testuser2"], "go_version": "1.17.2.linux-amd64" "}' --skip-tags "systemd"

or simply use the test scripts

sh test/test.sh 33

Note: We skip everything related to systemd, since systemd is not monitoring our services in the container.

After the test has finished you can stop the container and remove it:

docker rm test-fedora

Note

I created this project for the purpose of educating myself and personal use. If you are interested in the outcome, feel free to contribute; this work is published under the MIT license.

About

Ansible playbook to setup Linux developer machines.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published