mgsisk / providence

Opinionated Vagrant shell provisioner for web development.

Hi, I'm Mike

I’m an award-winning designer and developer with a passion for the web, new media, and bringing creative ideas to life. I live in Kalamazoo and work in higher education, but I’m always open to new opportunities.

providence's Issues

GitHub CLI source missing in v0.1.5

Expected Behavior
The github keyword should setup the GitHub CLI apt source, signing key, and install gh via apt.

Current Behavior
v0.1.5 never adds the GitHub CLI apt source to /etc/apt/sources.list.d/prov.list, which results in faulty provisioning if the github keyword is set.

Reproduction Steps
Attempt to provision with v0.1.5 with any setup that includes the github keyword.

Suggested Fix
Need to update the provisioner to include the correct GitHub CLI apt source.

Context
This is a result of some confusion on my part with cli/cli#6175; a modification was made to pull gh directly from github.com, which was then backed out when the signing key was updated and the apt source was usable again.

Release step fails in build action

Expected Behavior
The release step of the build action should create a release with the generated provisioner.sh file attached for any tags.

Current Behavior
This step currently fails, because the sed command is expecting the BSD version of sed but the release step is using the GNU version.

Reproduction Steps

vagrant up
vagrant ssh
cd /vagrant
npm run make.sh

Suggested Fix
Refactor src/make.sh to work with BSD or GNU sed.

Broaden the scope of Providence provisioning beyond Vagrant

Expected Behavior
At least some of what Providence does could be more useful to more basic Linux system provisioning.

Current Behavior
At the moment, however, Vagrant makes several Vagrant-oriented assumptions that prevent it from being used as-is to, for example, provision a generic Debian system.

Alternatives Considered
Something like Homebrew is really the ideal way to handle this, but – for very particular system setups – Providence might be a decent alternative.

Suggested Implementation
Generalize some of the more basic assumptions Providence makes (e.g. user name, available apps, etc.) so that it can be run as a general system provisioner for Debian-based setups.

Context
The idea for this comes in trying to setup Debian under WSL on Windows 11. For whatever reason Homebrew refuses to play nice, but Providence may be a handy alternative for particular needs.

WP-CLI is misconfigured

Expected Behavior
WP-CLI should default to a path of /srv/web

Current Behavior
WP_SRV does not receive a default value, so the path in ~/.wp-cli/config.yml is empty. This results in unintended provisioning side effects.

Reproduction Steps
vagrant up while trying to provision WordPress without WP_SRV set.

Suggested Fix
WP_SRV should have a default value set to /srv/web, like other *_SRV environment variables.