[WIP] a hacky implementation of services #35
Draft
Conversation
This file contains 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
|
interesting idea :) |
|
Any progress on this? It's a great idea. |
|
There also was a nixcon talk at some point where they used docker-compose as a job runner for this. |
|
x-ref #47 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a hacky implementation of services.
User can define a service in their devshell.toml that will be started automatically when they enter the devshell.
User can check logs for a service with
serviceViewer service-name.This doesn't yet cover a case where one service might depend on another, say a backend service that depends on postgres and redis.
Not intended to be merged yet, or maybe ever, it was just a fun little proof of concept.