Skip to content
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.

Fix inconsistent service name #24

Merged

Conversation

gblair
Copy link
Member

@gblair gblair commented Dec 14, 2017

When the new tld option was introduced (awesome, BTW!), the name of the service became tied to the TLD used. However, "dev" is hard-coded as a service name prefix in the boxen gem. Also, we could conceivably add more TLDs to our Dnsmasq setup, but we won't run a separate service for each one. Lastly, it might be nice to stick with the convention observed in other boxen-managed services where the service name is not tied to the configuration of the service.

When the new tld option was introduced, the name of the service became
tied to the TLD used. This is screwy, because "dev" is hard-coded as a
service name prefix in the boxen ruby gem.  We could conceivably add
more TLDs to our Dnsmasq setup, but we won't run a separate service for
each one. Also, we should stick with the convention observed in other
boxen-managed services where the service name is not tied to the
configuration of the service.
@jacobbednarz
Copy link
Member

Thanks for this! Past Jacob seems to have ignored the advice given at #17 (comment).

@jacobbednarz jacobbednarz merged commit d341482 into boxen:master Dec 14, 2017
@jacobbednarz
Copy link
Member

Released in 2.0.5. Much appreciated! 🍰

@gblair gblair mentioned this pull request Dec 19, 2017
@gblair gblair deleted the bugfix/inconsistent-service-name branch December 19, 2017 23:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants