Initializes project with serverless tinker setup#4
Merged
Conversation
Sets up the initial project structure for a serverless tinker environment. - Adds .dockerignore to exclude vendor directories. - Configures funding information. - Creates run-tests workflow for CI. - Adds CHANGELOG.md. - Configures composer.json with project details and dependencies. - Renames config/skeleton.php to config/sls-tinker.php. - Adds public/index.html for act logs viewer. - Updates README.md with project details. - Configures commands and service providers. - Introduces Lambda related components.
Updates the testing setup to correctly install and test the local package within a Laravel application. - Adds the `package/` directory to `.dockerignore` to prevent including it in the initial build context. - Modifies the workflow to create a Laravel application in a subdirectory called `app`, then installs the package from the local path within that application. - Fixes an issue where the port was incorrectly calculated in the test workflow. - Updates paths and working directories to reflect the new structure. - Adds a new Dockerfile for testing. - Upgrades pest dependencies to allow v2 and v3.
Updates the checkout path for the package code in the workflow to be relative. This ensures the workflow functions correctly regardless of the specific directory it is run from.
Sets up a comprehensive CI workflow to run tests against different combinations of PHP versions, Laravel versions, and serverless platforms (Vapor and Bref). This ensures compatibility and stability across various deployment environments. It creates separate Docker images for each platform to properly simulate lambda environments. The workflow also installs the package from a local path to facilitate testing during development.
Ensures a clean environment for composer install during CI, preventing potential issues caused by outdated cached files.
This commit introduces platform support for both Vapor and Bref, allowing the package to be used seamlessly with either serverless environment.
It achieves this by:
- Introducing a configuration option to specify the platform ('bref' or 'vapor').
- Modifying the Lambda invocation result handling to correctly parse the output format for each platform.
- Adjusting the environment variable name and test execution to account for different platforms.
- Updating the README to provide a more comprehensive overview of the package and its features.
This change enhances the package's usability and makes it more versatile for different serverless deployments.
Moves the test logic into a reusable composite action. This allows for cleaner and more maintainable workflow definitions. The main workflow now calls the composite action for each platform.
Updates the workflow to use the test action located within the 'package' directory. This ensures that the correct test action is used, especially in a monorepo setup where multiple packages might have their own test actions.
Updates the funding section in README.md to point to the GitHub Sponsors page. This simplifies the support information and directs users to the official GitHub sponsorship platform.
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
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.
No description provided.