summaryrefslogtreecommitdiff
path: root/www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html')
-rw-r--r--www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html18
1 files changed, 9 insertions, 9 deletions
diff --git a/www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html b/www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html
index c8d0a7f..844ba66 100644
--- a/www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html
+++ b/www/posts/laravel/2020-12-21/installing-laravel-homestead-in-arch-linux/index.html
@@ -24,22 +24,22 @@ $ git checkout release</code></pre><p>Create the Homestead.yaml file by using th
$ echo &quot;&lt;?php phpinfo();&quot; &gt; ~/projects/testsite/public/index.php</code></pre><h3>Setting up SSH</h3><p>I like to use unique ssh keys for servers that I connect to and that includes any virtual machines running on my local machine. The ssh-keygen command generates a new key that I store in a directory separate from my other ones.</p><pre><code class="shell">$ mkdir ~/.ssh/homestead
-$ ssh-keygen -t rsa -b 4096 -f ~/.ssh/homestead/id_rsa</code></pre><h3>Hostname Resolution</h3><p>Since I am using one instance of Homestead for multiple sites I need to configure the host machine so that requests are directed to the correct site on the virtual machine. This is done by adding an entry into the /etc/hosts file for each site. </p><p>First I need to know the IP address of the virtual machine. This can be done by looking in the Homestead.yaml file for the ip entry.</p><pre><code class="yaml">ip: &quot;192.168.10.10&quot;</code></pre><p>Then for each site that will be hosted on the virtual machine add it's domain and ip to the /etc/hosts file. </p><pre><code class="shell">$ sudo nvim /etc/hosts</code></pre><pre><code class="shell">192.168.10.10 testsite.local</code></pre><h2>Configuring Homestead</h2><p>Homestead is configured by editing the Homestead.yaml file that was created with the init.sh command earlier.</p><pre><code class="shell">$ cd ~/.local/share/homestead
+$ ssh-keygen -t rsa -b 4096 -f ~/.ssh/homestead/id_rsa</code></pre><h3>Hostname Resolution</h3><p>Since I am using one instance of Homestead for multiple sites I need to configure the host machine so that requests are directed to the correct site on the virtual machine. This is done by adding an entry into the /etc/hosts file for each site. </p><p>First I need to know the IP address of the virtual machine. This can be done by looking in the Homestead.yaml file for the ip entry.</p><pre><code class="yaml">ip: &quot;192.168.10.10&quot;</code></pre><p>Then for each site that will be hosted on the virtual machine add it&#039;s domain and ip to the /etc/hosts file. </p><pre><code class="shell">$ sudo nvim /etc/hosts</code></pre><pre><code class="shell">192.168.10.10 testsite.local</code></pre><h2>Configuring Homestead</h2><p>Homestead is configured by editing the Homestead.yaml file that was created with the init.sh command earlier.</p><pre><code class="shell">$ cd ~/.local/share/homestead
$ nvim Homestead.yaml</code></pre><p>First tell Vagrant that Virtualbox will be providing the virtual machine.</p><pre><code class="yaml">set provider: virtualbox</code></pre><p>Vagrant needs to setup the ssh keys between the host and the guest so that you can connect via ssh. Enter the path to the one created earlier.</p><pre><code class="yaml">authorize: ~/.ssh/homestead/id_rsa.pub
keys:
- ~/.ssh/homestead/id_rsa</code></pre><p>Share the project folder with the virtual machine. This setting will make the directory /home/vagrant/projects/testsite available in the virtual machine. The contents of this directory will be shared with the host machine directory ~/projects/testsite.</p><pre><code class="yaml">folders:
- map: ~/projects/testsite
- to: /home/vagrant/projects/testsite</code></pre><p>Setup Homestead so that it can serve the application through the 'domain' testsite.local. Note how this matches the name added to /etc/hosts earlier.</p><pre><code class="yaml">sites:
+ to: /home/vagrant/projects/testsite</code></pre><p>Setup Homestead so that it can serve the application through the &#039;domain&#039; testsite.local. Note how this matches the name added to /etc/hosts earlier.</p><pre><code class="yaml">sites:
- map: testsite.local
to: /home/vagrant/projects/testsite/public</code></pre><p>Have Homestead create a database for our application.</p><pre><code class="yaml">databases:
- - testsite</code></pre><p>Since I'm using a database ensure that a database server is installed on the virtual machine.</p><pre><code class="yaml">features:
+ - testsite</code></pre><p>Since I&#039;m using a database ensure that a database server is installed on the virtual machine.</p><pre><code class="yaml">features:
- mariadb: true</code></pre><h2>Launching Homestead</h2><p>Homestead is started with the vagrant up command. It may take a while for Homestead to launch if this is the first time running this command as Vagrant has to first download the actual virtual machine file.</p><pre><code class="shell">$ cd ~/.local/share/homestead
$ vagrant up</code></pre><p>Once the machine is booted I can browse to http://testsite.local/ to see the simple site that is now served by Homestead.</p><h2>Installing a Laravel Site</h2><p>Now that Homestead is installed and serving a simple site its time to move onto installing the first Laravel application. Since Homestead provides all the tools required to do this the first thing to do is connect to the virtual machine.</p><pre><code class="shell">$ cd ~/.local/share/homestead
-$ vagrant ssh</code></pre><p>Once connected to the virtual machine navigate to the project folder of the site. Remember that this is the folder that is also been shared with the host machine.</p><pre><code class="shell">$ cd ~/projects/testsite</code></pre><p>Clear the contents of this folder otherwise composer will complain about a non-empty directory.</p><pre><code class="shell ">$ rm -rf public</code></pre><p>Use composer to install a Laravel project.</p><pre><code class="shell">$ composer create-project laravel/laravel .</code></pre><h2>Setting Up The Application Database</h2><p>Once Larvel is installed a database needs to be created for the application. Connect to the database server with the mysql command.</p><pre><code class="shell">$ mysql -uhomestead -psecret</code></pre><p>Check that the application's database was created when the virtual machine was first booted.</p><pre><code class="mysql">SHOW DATABASES;
+$ vagrant ssh</code></pre><p>Once connected to the virtual machine navigate to the project folder of the site. Remember that this is the folder that is also been shared with the host machine.</p><pre><code class="shell">$ cd ~/projects/testsite</code></pre><p>Clear the contents of this folder otherwise composer will complain about a non-empty directory.</p><pre><code class="shell ">$ rm -rf public</code></pre><p>Use composer to install a Laravel project.</p><pre><code class="shell">$ composer create-project laravel/laravel .</code></pre><h2>Setting Up The Application Database</h2><p>Once Larvel is installed a database needs to be created for the application. Connect to the database server with the mysql command.</p><pre><code class="shell">$ mysql -uhomestead -psecret</code></pre><p>Check that the application&#039;s database was created when the virtual machine was first booted.</p><pre><code class="mysql">SHOW DATABASES;
+--------------------+
| Database |
@@ -50,16 +50,16 @@ $ vagrant ssh</code></pre><p>Once connected to the virtual machine navigate to t
| performance_schema |
| sys |
| testsite |
-+--------------------+</code></pre><p>If the database does not exist create it with the below SQL.</p><pre><code class="mysql">CREATE DATABASE testsite;</code></pre><p>Create a MySQL user for the application and grant permissions to use the application database.</p><pre><code class="mysql">CREATE USER 'testsite'@'localhost' IDENTIFIED BY 'testsite';
++--------------------+</code></pre><p>If the database does not exist create it with the below SQL.</p><pre><code class="mysql">CREATE DATABASE testsite;</code></pre><p>Create a MySQL user for the application and grant permissions to use the application database.</p><pre><code class="mysql">CREATE USER &#039;testsite&#039;@&#039;localhost&#039; IDENTIFIED BY &#039;testsite&#039;;
-GRANT ALL PRIVILEGES ON testsite.* TO 'testsite'@'localhost';</code></pre><p>Exit the database server.</p><pre><code class="mysql">exit</code></pre><p>To check the new MySql user account simply connect as that user with the credentials used earlier.</p><pre><code class="shell">$ mysql -utestsite -ptestsite</code></pre><p>The result of the SHOW DATABASE sql should show that the user account can see the application database.</p><pre><code class="mysql">SHOW DATABASES;
+GRANT ALL PRIVILEGES ON testsite.* TO &#039;testsite&#039;@&#039;localhost&#039;;</code></pre><p>Exit the database server.</p><pre><code class="mysql">exit</code></pre><p>To check the new MySql user account simply connect as that user with the credentials used earlier.</p><pre><code class="shell">$ mysql -utestsite -ptestsite</code></pre><p>The result of the SHOW DATABASE sql should show that the user account can see the application database.</p><pre><code class="mysql">SHOW DATABASES;
+--------------------+
| Database |
+--------------------+
| information_schema |
| testsite |
-+--------------------+</code></pre><h2>Configuring The Laravel Application</h2><p>Edit the supplied .env file.</p><pre><code class="shell">$ vim .env</code></pre><p>If one does not exist then copy the example file.</p><pre><code class="shell">$ cp .env.example .env</code></pre><p>Change the environment variables to match those below. Some of changes ensure that Laravel can connect to the database created earlier.</p><pre>APP_NAME='Test Site'
++--------------------+</code></pre><h2>Configuring The Laravel Application</h2><p>Edit the supplied .env file.</p><pre><code class="shell">$ vim .env</code></pre><p>If one does not exist then copy the example file.</p><pre><code class="shell">$ cp .env.example .env</code></pre><p>Change the environment variables to match those below. Some of changes ensure that Laravel can connect to the database created earlier.</p><pre>APP_NAME=&#039;Test Site&#039;
APP_URL=http://testsite.local
@@ -68,9 +68,9 @@ DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=testsite
DB_USERNAME=testsite
-DB_PASSWORD=testsite</pre><p>Now when you browse to http://testsite.local you will see the Laravel welcome page.</p><h2>Simplified SSH</h2><p>I prefer to just use the host system's ssh command to connect to Homestead as it cuts out having to navigate to the Homestead directory and running vagrant ssh.</p><p>To simplify ssh I first add a hostname for the virtual machine to the file /etc/hosts/</p><pre><code class="shell">192.168.10.10 homestead</code></pre><p>I then edit ~/.ssh/config and add the below configuration. This tells ssh to automatically use the keys and username specified when connecting to the virtual machine.</p><pre><code class="ssh">Host homestead
+DB_PASSWORD=testsite</pre><p>Now when you browse to http://testsite.local you will see the Laravel welcome page.</p><h2>Simplified SSH</h2><p>I prefer to just use the host system&#039;s ssh command to connect to Homestead as it cuts out having to navigate to the Homestead directory and running vagrant ssh.</p><p>To simplify ssh I first add a hostname for the virtual machine to the file /etc/hosts/</p><pre><code class="shell">192.168.10.10 homestead</code></pre><p>I then edit ~/.ssh/config and add the below configuration. This tells ssh to automatically use the keys and username specified when connecting to the virtual machine.</p><pre><code class="ssh">Host homestead
IdentityFile ~/.ssh/homestead/id_rsa
- User vagrant</code></pre><p>From now on I can simply do ssh homestead from any directory to connect to the Homestead virtual machine.</p><h3>Links</h3><a href="https://laravel.com/docs/8.x/homestead/">Laravel Homestead</a><a href="/posts/larvel/">Laravel - Read More Posts.</a><p>I don't have comments as I don't want to manage them. You can however contact me at the below address if you want to.</p><a href="mailto:david@davidtsadler.com">Email david@davidtsadler.com</a><h3>License</h3><a href="https://creativecommons.org/licenses/by-sa/4.0/">The contents of this site is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.</a><p>Copyright © 2021 David T. Sadler.</p><a href="/">Return to Homepage.</a></section>
+ User vagrant</code></pre><p>From now on I can simply do ssh homestead from any directory to connect to the Homestead virtual machine.</p><h3>Links</h3><a href="https://laravel.com/docs/8.x/homestead/">Laravel Homestead</a><a href="/posts/larvel/">Laravel - Read More Posts.</a><p>I don&#039;t have comments as I don&#039;t want to manage them. You can however contact me at the below address if you want to.</p><a href="mailto:david@davidtsadler.com">Email david@davidtsadler.com</a><h3>License</h3><a href="https://creativecommons.org/licenses/by-sa/4.0/">The contents of this site is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.</a><p>Copyright © 2021 David T. Sadler.</p><a href="/">Return to Homepage.</a></section>
<script defer src="/js/highlight.min.js"></script>
<script defer src="/js/site.js"></script>
</body>