Requirements

Install Vagrant.
Install VirtualBox.
Make sure to have enough space on your default drive. Go to Troubleshooting for changing the default location where Vagrant and VirtualBox store its data.

Run

Clone this repository:

git clone https://github.com/ed3899/vagrant-base-ubuntu-jammy <MY_PERSONAL_VM>

Create a local branch:
```
git branch -b <MY_LOCAL_BRANCH>
```

On the Vagrantfile, select your tags by uncommenting them (some tags may require additional setup, go to Tags):

  ansible.tags = [
    #? Cloud providers
    # "aws",
    #? Containerization
    # "docker",
    #? Dbs
    # "mysql",
    # "pg-15",
    #? IaC
    # "pulumi",
    #? Orchestration
    # "helm",
    # "kind",
    # "kubectl",
    # "minikube",
    #? Programming languages
    # "dotnet_sdk",
    # "go",
    # "node_js",
    # "python_anaconda",
    # "rust",
    #? Terminal
    # "starship",
    #? UI
    # "gui",
    #? Vc
    # "git",
    # "github",
  ]

Change that according to the tags you wish to run. Each tag maps to an ansible play. The order you pick doesn't matter.

And run:
```
vagrant up
```
If you ran into issues while downloading the box, go to Troubleshooting
Once changes are done, ssh into the VM:
```
vagrant ssh
```
If you've picked a new tag after the initial provisioning, run:
```
vagrant provision
```
If for some reason you lose you ssh connection, run:
```
vagrant reload
```
and try sshing again.
If you want to reboot the machine and provision again, run:
```
vagrant reload --provision
```
and try sshing again.

Share folders

On the Vagrantfile, make sure you shared the additionals folders you would like to have in sync with the VM with the following line:

config.vm.synced_folder "./HOST/FOLDER", "/GUEST/FOLDER", owner: "vagrant", group: "vagrant", create: true

By default the ansible and assets folders are shared.

The first one is needed for provisioning while the latter is for resources you would like to share with your VM, place those in there anytime, no need to reload (i.e images, csv, etc).

This is useful if you decide to SSH via VS Code Remote SSH Extension or another method (see Using with VS Code Remote SSH Extension)

Be mindful of sharing folders with initialized git repositories. If you decide to fork and make changes to this repository some of those may conflict with children repos.

Add those to the .gitignore file of this repo to avoid conflicting repo issues with the children.

Or you can set them as git sub-modules.

Once done, reload the vm for the changes to take effect:

vagrant reload

Tags

In order to install tools, uncomment the choosen tag.

Cloud providers

AWS

If using the aws tag.

Create or fill:

ansible\playbooks\secrets\main.yml

With values:

aws:
  access_key_id: YOUR_KEY
  secret_access_key: YOUR_SECRET_KEY
  region: us-west-2
  output: json

This file is ignored by git

Containerization

Docker

If using with VS Code remote extension an extension like Docker can help you manage your containers from the VS Code IDE.

Databases

If using with VS Code remote extension an extension like SQLTools can help you manage your tables and databases, you can pick multiple drivers.

MySQL

The MySQL database has the following credentials:

user: root
password: my-secret-pw

user: vagrant
password: my-secret-pw

If you want to interact with your database from a VSCode extension, make sure you've got a Private Network on Vagrant between the host and the guest.

Postgres

All postgreSQL tags have the following available users and database:

user: postgres
password: postgres
database: vagrant

If you want to interact with your database from a VSCode extension, make sure you've got a Private Network on Vagrant between the host and the guest.