You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that more devs than just me may use this script, let's get a todo list of ways it could make devs' lives easier.
Note: there's a bunch of copy-pasta between deploy_buttonmen_site and the other scripts in its directory like the teardown script. That's not a super high priority to change, but anyone who picks up this issue should make any relevant changes consistently in all scripts, not just the deploy one.
Under local use, deploy_buttonmen_site always has docker stand up the site with the http port mapped to 8080 on the host machine. It should be possible to override that if the dev prefers a different port.
deploy_buttonmen_site uses sed to change deploy/vagrant/manifests/init.pp to pick up site-specific DB and FQDN parameters. It doesn't undo those changes, which means devs have to manually clean up their workspaces before committing. The script should do the cleanup itself on successful site deploy.
The text was updated successfully, but these errors were encountered:
Now that more devs than just me may use this script, let's get a todo list of ways it could make devs' lives easier.
Note: there's a bunch of copy-pasta between
deploy_buttonmen_site
and the other scripts in its directory like the teardown script. That's not a super high priority to change, but anyone who picks up this issue should make any relevant changes consistently in all scripts, not just the deploy one.deploy_buttonmen_site
always has docker stand up the site with the http port mapped to 8080 on the host machine. It should be possible to override that if the dev prefers a different port.deploy_buttonmen_site
uses sed to changedeploy/vagrant/manifests/init.pp
to pick up site-specific DB and FQDN parameters. It doesn't undo those changes, which means devs have to manually clean up their workspaces before committing. The script should do the cleanup itself on successful site deploy.The text was updated successfully, but these errors were encountered: