Helical_Insight wants to install Discourse on their Windows 8 localhost, but lacks knowledge on Rails apps. simon suggests upgrading to Windows 10 and following the guide for setting up a dev environment, or installing Linux.
D8vid offers an alternative using Vagrant, a virtual machine manager, to provide a WSL-like environment on Windows 8. However, sam notes that Vagrant is not supported and recommends using WSL2 or a VM instead.
D8vid clarifies that Vagrant is just a VM manager, but sam emphasizes that maintaining a Vagrant config and publishing an image are not feasible. Instead, sam recommends using WSL2 + Docker dev for a low-touch setup and provides a link to the Beginners Guide to Install Discourse for Development using Docker.
D8vid responds that Vagrant can still be useful, referencing a Vagrantfile and instructions for hacking on discourse_docker.
I wanted to Install Discourse on my local machine I have windows 8 as OS, Please help in the installation of Discourse in my localhost.
I have installed my website on my local and now I want to install discourse
Vagrant, a virtual machine manager written in Ruby, is an option for Windows 8; it provides a WSL-like environment (Windows Subsystem for Linux, a Windows 10 feature).
Vagrant can use Docker, Hyper-V or VirtualBox as a virtual machine provider, in case you already have one of those installed. If not, the easiest tool to use for setup is Chocolatey; once Chocolatey is installed, the command choco install -y virtualbox vagrant will install both Vagrant and VirtualBox.
From there, follow the Vagrant Project Setup guide to install an Ubuntu VM, e.g. vagrant init hashicorp/bionic64 (or bionic32 if your Windows 8 install is 32-bit).
Vagrant is just a VM manager, for VMs provided by Microsoft’s Hyper-V, or VirtualBox, or VMware (more involved setup, but possible to use). In that sense, Vagrant is a lot like WSL2 which just provides a specialized Hyper-V VM with some additional Microsoft-sanctioned Windows/Linux integration.
I may be mistaken but the expectation with vagrant would be that we maintain config for it and publish an image. These are 2 things that are not on the table.
For a very low touch setup that allows you to go from 0 - 100 very quickly use WSL2 + Docker dev
Forgot this thread was left dangling. Vagrant is just a dev tool (a VM manager) that doesn’t strictly need a config file to be useful, and certainly not a dedicated image (it’ll quickly bring up a VM capable of hosting Docker & running Discourse scrips like discourse-setup & launcher just fine).