From 627138ad99f5a39a2fe6783505edaee10449af4d Mon Sep 17 00:00:00 2001 From: Connor Olding Date: Wed, 6 Sep 2023 16:10:29 -0700 Subject: [PATCH] strip down and rewrite Vagrantfile --- Vagrantfile | 88 +++-------------------------------------------------- 1 file changed, 5 insertions(+), 83 deletions(-) diff --git a/Vagrantfile b/Vagrantfile index 38f30cc..b648f2d 100644 --- a/Vagrantfile +++ b/Vagrantfile @@ -1,90 +1,12 @@ -# -*- mode: ruby -*- -# vi: set ft=ruby : - -# All Vagrant configuration is done below. The "2" in Vagrant.configure -# configures the configuration version (we support older styles for -# backwards compatibility). Please don't change it unless you know what -# you're doing. Vagrant.configure("2") do |config| - # The most common configuration options are documented and commented below. - # For a complete reference, please see the online documentation at - # https://docs.vagrantup.com. + config.ssh.insert_key = true - # Every Vagrant development environment requires a box. You can search for - # boxes at https://vagrantcloud.com/search. config.vm.box = "boxomatic/alpine-3.18" - config.vm.box_version = "20230515.0.1" - # config.vm.box = "generic/alpine317" - # config.vm.box_version = "4.2.16" - - # Disable automatic box update checking. If you disable this, then - # boxes will only be checked for updates when the user runs - # `vagrant box outdated`. This is not recommended. - # config.vm.box_check_update = false - - # Create a forwarded port mapping which allows access to a specific port - # within the machine from a port on the host machine. In the example below, - # accessing "localhost:8080" will access port 80 on the guest machine. - # NOTE: This will enable public access to the opened port - # config.vm.network "forwarded_port", guest: 80, host: 8080 - - # Create a forwarded port mapping which allows access to a specific port - # within the machine from a port on the host machine and only allow access - # via 127.0.0.1 to disable public access - # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1" - - # Create a private network, which allows host-only access to the machine - # using a specific IP. - # config.vm.network "private_network", ip: "192.168.33.10" - - # Create a public network, which generally matched to bridged network. - # Bridged networks make the machine appear as another physical device on - # your network. - # config.vm.network "public_network" - - # Share an additional folder to the guest VM. The first argument is - # the path on the host to the actual folder. The second argument is - # the path on the guest to mount the folder. And the optional third - # argument is a set of non-required options. - # config.vm.synced_folder "../data", "/vagrant_data" - - # Disable the default share of the current code directory. Doing this - # provides improved isolation between the vagrant box and your host - # by making sure your Vagrantfile isn't accessable to the vagrant box. - # If you use this you may want to enable additional shared subfolders as - # shown above. - # config.vm.synced_folder ".", "/vagrant", disabled: true - - # Provider-specific configuration so you can fine-tune various - # backing providers for Vagrant. These expose provider-specific options. - # Example for VirtualBox: - # - # config.vm.provider "virtualbox" do |vb| - # # Display the VirtualBox GUI when booting the machine - # vb.gui = true - # - # # Customize the amount of memory on the VM: - # vb.memory = "1024" - # end - # - # View the documentation for the provider you are using for more - # information on available options. - - # config.vm.synced_folder ".", "/vagrant" - # config.vm.hostname = "stargazing" - # config.vm.network "private_network", type: "dhcp" - # config.vm.network "private_network", ip: "192.168.13.37" - - config.ssh.insert_key = false config.ssh.username = "root" config.ssh.password = "vagrant" - # Enable provisioning with a shell script. Additional provisioners such as - # Ansible, Chef, Docker, Puppet and Salt are also available. Please see the - # documentation for more information about their specific syntax and use. - config.vm.provision "shell", inline: <<-SHELL - apk update && apk upgrade - apk add autoconf gcc gperf linux-headers make musl-dev ninja patch pkgconf xz zip - sh /vagrant/notwa-util/doit9 - SHELL + config.vm.provision "shell", name: "motd", inline: "echo them do be stars tho > /etc/motd" + config.vm.provision "shell", name: "update", inline: "apk update && apk upgrade" + config.vm.provision "shell", name: "install", inline: "apk add autoconf gcc gperf linux-headers make musl-dev ninja patch pkgconf ripgrep xz zip" + config.vm.provision "shell", name: "build", inline: "exec sh /vagrant/notwa-util/doit11" end