With Docksal you can initialize a basic LAMP stack with no configuration.
In this case a default configuration will be used to provision containers and set up a virtual host.
Initial configuration is done once per project (e.g., by a team lead) and committed to the project repo.
Presence of the .docksal folder in the project directory is a good indication the project is using Docksal.
Create a project directory structure:
mkdir ~/projects/myproject
mkdir ~/projects/myproject/docroot
mkdir ~/projects/myproject/.docksal
The docroot directory is mounted as the web server document root.
The .docksal directory is where all Docksal configurations and commands for the project are stored.
Is your Project Root the same as your Document Root? If so, you can accomplish this by running fin config set DOCROOT=. which sets the value in the .docksal/docksal.env file.
cd ~/projects/myproject
fin project start
You will see output similar to the following:
Starting services...
Creating network "myproject_default" with the default driver
Creating volume "myproject_project_root" with local driver
Creating myproject_cli_1
Creating myproject_db_1
Creating myproject_web_1
Connected vhost-proxy to "myproject_default" network.
Note: SSH key passphrase
If you are being asked for an SSH key passphrase for id_dsa or id_rsa,
remember, that these are your keys loaded from your ~/.ssh folder into the ssh-agent container.
That’s why their paths look like /root/.ssh/.... That is the path inside the ssh-agent container.
Provide password(s) if you want to use git or drush commands, that require ssh access within Docksal
(e.g., often a project init script or a composer script contains a repository checkout,
which would require an ssh key for access).
Your project stack is now running. Access it in your browser: http://myproject.docksal
!!! tip “VIRTUAL HOST name”
By default the virtual host name is equal to the project’s folder name sans spaces and dashes,
with the .docksal domain appended to it.
myproject => myproject.docksal