Add initial support for Vapor connections #151
Merged
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
Member
|
|
Member
Author
|
It’s intentional. The Vapor option only appears if the project contains a vapor.yml configuration file; otherwise, the option is not shown at all. |
Member
Member
Author
|
Ok for the documentation! Anyway, I asked some acquaintances who use Vapor to run some tests to make sure everything works properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 pull request introduces the first implementation of the Vapor connections feature.
Key points:
• Added support for selecting and managing Laravel Vapor environments.
• Allows users to execute PHP code via Vapor CLI in the selected environment.
• Highlights the currently active environment with visual feedback.
• Restricted to projects containing a valid vapor.yml file.