Setup Laravel 10.x Homestead in Windows 10/11

Section – 1 [Install Software]

https://laravel.com/docs/10.x/homestead#installation-and-setup

vagrant_2.3.7_windows_amd64.msi – https://developer.hashicorp.com/vagrant/downloads

VirtualBox-6.1.46-158378-Win.exe – https://www.virtualbox.org/wiki/Download_Old_Builds_6_1

VirtualBox 6.1.46 (released July 18 2023) << This and Not the >> VirtualBox 7.0.10 platform packages – ​Windows hosts

According to: https://laravel.com/docs/10.x/homestead#installation-and-setup

Code Editor/IDE: PhpStorm-2023.1.4.exe or VSCodeSetup-x64-1.80.1.exe

Lastly install: Git-2.41.0.3-64-bit.exe – https://git-scm.com/downloads

Section – 2 [ENABLE VT-x in Hardware/BIOS/UEFI if disabled]

http://leonidassavvides.com/blog/2023/07/23/enable-vt-x-in-hp-z640-workstation/

Section – 3 [Installing Homestead]

https://laravel.com/docs/10.x/homestead#installing-homestead

Go To CLI Terminal in IDE/Editor or Windows Terminal or Git Bash Terminal and execute:

git clone https://github.com/laravel/homestead.git D:\htdocs_xampp\Homestead

where D:\htdocs_xampp\Homestead the Homestead directory, after entering this directory:

d:
cd d:\htdocs_xampp\Homestead

Next, execute the bash init.bat command from the Homestead directory to create the Homestead.yaml configuration file. The Homestead.yaml file is where you will configure all of the settings for your Homestead installation. This file will be placed in the Homestead directory: if there is a problem with the

init.bat 

use

./init.bat

Section – 4 [Configuring Homestead]

Follow the instructions at:

https://laravel.com/docs/10.x/homestead#configuring-homestead

For configuring the file: Homestead.yaml

Section – 5 [Launching The Vagrant Box]

After all, the steps above, it is time to:

Launching The Vagrant Box

You must have in mind the 4 most used CLI commands FROM CLI/Terminal at d:\htdocs_xampp\Homestead\:

vagrant up # if error on this - please Section 6 below
vagrant status
vagrant suspend
vagrant ssh

Section – 6 [Configuring SSH Keys]

In case the first attempt of running:

vagrant up

you getting

Please give the command to generate ssh keys in Windows:

ssh-keygen -t rsa -C "username@email.com"

This will create the:

C:\Users\lwdls\.ssh\id_rsa.pub
C:\Users\lwdls\.ssh\id_rsa

Then you have to go to Homestead.yaml and edit the SSH Keys with the correct Keys you have just created:

authorize: C:\Users\lwdls.ssh\id_rsa.pub
keys:
     - C:\Users\lwdls.ssh\id_rsa

Then you return to Section – 5 and give the command: vagrant up

The first time you have to await some time to download the Vagrant VM – Ubuntu Server from the repositories…

After the VM OK is launched go to: http://homestead.test/phpinfo.php to see the webpage of phpinfo():

phpinfo.php

<?php
phpinfo();
?>

if any problem put the phpinfo.php

in

public/phpinfo.php

to stop the VM – shutdown the PC – give

vagrant suspend

To add additional sites:

Adding Additional Sites

https://laravel.com/docs/10.x/homestead#adding-additional-sites

To create a Laravel Site – start with download Laravel files with the:

https://laravel.com/docs/10.x/installation#your-first-laravel-project

At Terminal d:\htdocs_xampp\

composer create-project laravel/laravel example-laravel-app

Composer can be installed from:

https://getcomposer.org/download/

Also, the composer comes preinstalled in Homestead/Vagrant/VM

And, a second way is:

After:

vagrant up 

Give:

vagrant ssh

and from Terminal at /home/vagrant/ give the command:

 composer create-project laravel/laravel example-laravel-app

Any way you choose, be sure to edit the Homestead.yaml and every new website added to run:

vagrant reload --provision

And lastly

To run a new URL locally modify the host file at:

On macOS and Linux, this file is located at /etc/hosts. On Windows, it is located at C:\Windows\System32\drivers\etc\hosts:

192.168.56.56 homestead.test
192.168.56.56 another1.test
192.168.56.56 another2.test

Again, according to

Homestead.yaml

After, download the Laravel 10.x bootstrap code base, view the Laravel homepage accordingly by going to http://another1.test.

Happy Laravel Web Development & Coding…!

Enable VT-x in hp Z640 Workstation

Symptom – when going to vagrant up – to start a VM for the first time in this OS/PC

The msinfo32 shows: VT-x is disabled

Follow the Steps for the result: VT-x enabled

===

STEP BY STEP – Follows

0 – reboot the PC

Go – Security[3] and after System Security[4]

VT-x is disabled[all three], We will enable all

After confirming it

Go: Main[7] + Save & Exit

now msinfo32 will show:

All Done!

IBM Compatible vs Mac Clones; The nostalgic era of legal Mac Clones Computers, the era without the Apple Computer monopoly; This has been just a few years before the turn of the century, between 1995-1999


It was, the magazine PC-KYPRIAKO a Cyprus πŸ‡¨πŸ‡Ύ magazine for computers in Greek I started to read at the age of 14 years old from 1989-1990… learned my first computer experience, but without a PC, only by reading this Journal. Later in 1992, I got my first PC, an IBM-compatible MS-DOS Computer, 80386/i386, I think without a mouse!!! (since MS-DOS OS and Not MS-Windows OS). Two years later I upgraded the RAM & the OS to Windows 3.1 and started on Windows Office and Draw Apps like Word, Excel, and CorelDraw. I got a ballpoint mouse too.

In the mid-1990s, the personal computer market was dominated by IBM-compatible machines, but there was also a small but thriving market for Macintosh clones. These were computers that were legally licensed to run Apple’s operating system, from 1995+ but were made by third-party manufacturers instead of Apple itself. This was a unique period in the history of personal computing, and it’s worth taking a closer look at how it all came about.

In the early days of personal computing, Apple was one of the most innovative and successful companies in the industry. The original Macintosh, released in 1984, was a groundbreaking machine that set the standard for user-friendly graphical user interfaces. However, despite its initial success, Apple soon found itself struggling to compete with the much larger IBM-compatible market. By the early 1990s, Macintosh sales had stagnated, and the company was in danger of being marginalized.

To boost sales and increase market share, Apple decided to license its operating system to third-party manufacturers. This was a bold move, as it meant giving up some control over the hardware and software ecosystem that had made Apple successful in the first place. However, the hope was that by expanding the market for Macintosh-compatible machines, Apple could regain its position as a major player in the personal computing world.

The first company to take advantage of Apple’s licensing program was a company called Power Computing, which released its first Macintosh clone in 1995. The Power Macintosh line of computers was a huge success, offering consumers a wider range of choices at lower prices than Apple’s machines. Other companies soon followed suit, including UMAX, Motorola, and DayStar Digital.

At the time, many people thought that the Mac clone market was the future of personal computing. Apple’s market share was still relatively small, and the clones seemed like a viable way to expand the Macintosh ecosystem. However, things didn’t quite work out that way. Although the clones were popular among consumers, they were not successful enough to bring Apple back to dominance. They may have hurt the company more than they helped it.

One of the biggest problems with the Mac clone market was that it created a fragmented hardware and software ecosystem. Because there were so many different manufacturers making different types of Macintosh-compatible machines, software developers had a hard time creating software that would work reliably across all of them. This meant that the Macintosh ecosystem became much less attractive to developers, who were already more focused on the larger IBM-compatible market.

Another problem was that the Mac clones were often seen as inferior to Apple’s machines. Although they were cheaper, they were also less reliable and less well-designed. This meant that even Mac users often preferred to stick with Apple’s machines, rather than switch to a clone.

In the end, the Mac clone market was short-lived. By the late 1990s, Apple had regained some of its momentum with the release of the iMac and other popular machines. At the same time, the market for IBM-compatible machines was starting to shrink, as consumers began to shift their focus to newer devices like smartphones and tablets.

Looking back on this era, it’s clear that the Mac clone market was an interesting experiment in the history of personal computing. Although it didn’t succeed, it showed that there was a demand for a wider range of hardware options in the Macintosh ecosystem. And who knows – if things had gone differently, we might be living in a world today where Mac clones are just as common as IBM-compatible machines.


MacOS Alternatives in History & Now:

1

Mac Clones Computers πŸ–₯️ [1995 – 1999]

The hardware had Apple hardware Specifications and ran MacOS.

2

Mac Hackintosh Computers πŸ–₯️ [200X – 2023]

Hardware has IBM/Windows Specifications (Not all hardware is compatible with this process*, you have e.g. built a PC in the case with compatible parts like Intel processor, etc. AMD usually does not work) but runs MacOS.

3

MacOS VMs on MacOS using VMware, VirtualBox, or Parallels** πŸ–₯️ [200X – 2023]

Hardware Apple Mac, host MacOS, running Guest MacOS isolated OS.

4

MacOS VMs on Windows or Linux using VMware, or Virtual Box*** πŸ–₯️ [2006 – 2023]

Hardware IBM/Windows, host Windows 10/11 OS, running Guest MacOS isolated OS.


————notes————

* You must do your research for hardware compatibility.

** You must get a good Mac, as VMs usually need additional hardware resources like RAM over +16GB and an Intel processor over +4 cores.

*** You must do your research again for hardware compatibility, and get a good PC, as VMs usually need additional hardware resources like RAM over +16GB and an Intel processor over +4 cores.


————links————

The Macintosh Clones

https://everymac.com/systems/mac-clones/index-mac-clones.html
https://hackintosh.com/

Virtualization on a Mac (Apple.com)


https://www.makeuseof.com/tag/macos-windows-10-virtual-machine/