Add labels for local domain names with OrbStack #158
+24
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All OrbStack needs to access a container using a domain name (usually *.local) is to add a label to that service with the domain name you want to use. OrbStack handles provisioning an SSL certificate for that hostname. The other nice thing about it is that you don’t need to include a port. So, if you have an app server running on port 3000, instead of accessing it with **http://localhost:3000**, you can access it at **https://webapp.local**. 🙂 I’m sure that I didn’t cover all of the services that can be accessed individually. We can add lablels for anything I missed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All OrbStack needs to access a container using a domain name (usually *.local) is to add a label to that service with the domain name you want to use. OrbStack handles provisioning an SSL certificate for that hostname. The other nice thing about it is that you don’t need to include a port. So, if you have an app server running on port 3000, instead of accessing it with http://localhost:3000, you can access it at https://webapp.local. 🙂
I’m sure that I didn’t cover all of the services that can be accessed individually. We can add lablels for anything I missed before merging if you want to point them out (or add them yourself).
@coleam00, as you will see, there is no impact on how everything will run using Docker Desktop. This is just an enhancement to enable quality of life features in OrbStack.