Inception: a 42 Project to learn Docker

Usage

Option 1: GitHub Codespace

GitHub Codespaces provides a convenient way to work with code in the cloud. If you're new to Codespaces, follow these steps to get started:

1. Click the "Code" button on this GitHub repository's main page.

2. In the dropdown menu, select "Open with Codespaces."

3. Follow the on-screen prompts to create a new Codespace for this repository.

4. Once the Codespace is ready, you can run make command where the Makefile is and the Docker containers will be created

5. Unfortunately you need to use curl to open the webpage if the clicking on the link (port 443) did not work. Or you can try 2nd option with Virtual Machine below.

curl -k https://codespace.42.fr -> to open the webpage and skipping the certificate is private warning

curl http://codespace.42.fr -> will give error, as only port 443 and not 80 is set according to subject

If curl is not already installed, run sudo apt install curl

Option 2: Virtual Machine

If you prefer to work with a virtual machine, you can download a ready-to-run Debian virtual machine image from LinuxVMImages which means you don't need to create partitions or setup anything. Here are the steps to set up the virtual machine:

1. Download the Debian or any other Linux virtual machine image from LinuxVMImages.

2. You can either install a gui version for convenience which uses more space. Or non-gui version. I first downloaded non-gui version then installed gnome desktop via command: sudo apt install gnome-core so that it only had necessary software instead of a lot of programs.

3. You just need to click on the .vbox file to run the VM

4. If you get an Error regarding Audio (WAS) then open the .vbox file in Text editor and Remove the line where Audio driver and "WAS" is written

5. If there is an Error regarding USB 2.0, then edit the Settings of the VM in Virtual Box, in the settings USB, just disable USB 2.0

6. After starting VM, just clone the repository and run make

.env File

Do not push any .env file to Vogsphere or put any passwords in other configuration files. The .env file here is just for testing purposes and are random/fake passwords.