[pull] main from serversideup:main #59
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
…r health checks, task scheduler, and Reverb setup instructions.
…y and improve error handling for isolated migrations. Added debug logs for new environment variables related to migrations.
…n belongs to uid X instead of Y` for FPM-NGINX on Alpine
…roved error handling. Added support for multiple databases, migration modes, and seeding. Updated documentation to reflect these changes and added a new script for testing database connections.
…php variation - Introduced a HEALTHCHECK command in the Dockerfile with specified parameters. - Updated Caddyfile to define healthcheck endpoints and log skipping for both default and custom healthcheck paths. - Enhanced full Caddyfile to redirect localhost healthcheck requests to HTTPS.
* Fix missing gettext, procps and zip on FrankenPHP Variation * Remove gettext (we don't need envsubst for FrankenPHP) * Update default configurations to include libstdc++6 and clarify procps requirements for Debian images * Removed zip -- we don't need it --------- Co-authored-by: Jay Rogers <[email protected]>
…the new hash in contributing documentation
…HP variation' in the getting started guide.
- Introduced a new section explaining what Docker is and its advantages for containerizing applications. - Added a demo video link for the Spin project to help users get started with Docker. - Updated the FPM-NGINX section to reflect its historical significance and current relevance. - Marked the NGINX Unit variation as deprecated due to its discontinuation. - Added a new section for the FrankenPHP variation, highlighting its features and benefits.
…ns, including detailed descriptions for CLI, FPM, FPM-Apache, FPM-NGINX, and FrankenPHP. Marked NGINX Unit as deprecated and provided migration guidance. Improved overall structure for better user understanding.
…EADME for clarity. Refactor app components and CSS for improved styling and structure.
…docs-update # Conflicts: # docs/content/1.getting-started/3.installation.md
…docker-php into feature/280-pr-docs-update
…FPM-NGINX, and FrankenPHP variations. Marked NGINX Unit as deprecated and provided migration guidance. Improved overall structure for better user understanding.
…sideup/docker-php into 280-create-a-frankenphp-variation
This fixes #261 in the FrankenPHP images. (See also b9118b4.) Co-authored-by: Jay Rogers <[email protected]>
…sion 4 This new documentation outlines the migration process, highlights new features, and provides a checklist for users transitioning from version 3 to version 4, ensuring a smooth upgrade experience without breaking changes.
…names explanation This update introduces a new section on service names in Docker Compose, detailing how to define and reference services in the `compose.yml` file. It includes examples for clarity and improves the overall understanding of container management.
… guidance This update expands the section on using Docker with WordPress, emphasizing security optimizations, compatibility challenges, and recommended practices. It includes detailed explanations of deployment strategies and the importance of adhering to WordPress conventions for better plugin compatibility.
… for clarity and impact This update enhances the introductory content for the serversideup/php Docker images, emphasizing their production readiness, security, and performance optimizations. It also updates button labels and section headings to better reflect the content and improve user engagement.
…anced configuration details This update enhances the section on running Laravel queue workers with Docker, emphasizing the use of Artisan commands and the importance of graceful shutdowns. It also introduces advanced configuration options for managing multiple processes within a single container.
…and best practices This update clarifies the process of running Laravel Horizon with Docker, emphasizing the use of Artisan commands, the necessity of a running Redis instance, and the importance of graceful shutdowns. Key points for configuration and health checks are also introduced to improve user understanding.
This update enhances the section on running Laravel's task scheduler in Docker, emphasizing the use of the `schedule:work` command instead of `cron`. Key points regarding service configuration, graceful shutdowns, and defining schedules within Laravel are also included for better user guidance.
This update introduces tips for running multiple processes within a single container for both queue workers and Horizon, emphasizing the use of S6 Overlay scripts. Additionally, it clarifies the role of the `schedule:work` command in the task scheduler section, improving overall guidance for users working with Laravel in Docker environments.
…processes in Docker This update standardizes the tips for managing multiple processes within a single container across various sections, including task scheduler, queue, Horizon, and Reverb. It emphasizes the use of S6 Overlay service scripts and provides clearer instructions for users running `fpm-nginx` or `fpm-apache`, improving overall documentation consistency and usability.
…redundant details on Debian and Alpine
… practices of running containers as non-root users. Added sections on implications for web server ports and file permissions, along with recommended methods for running services on standard HTTP/HTTPS ports.
…ration (#608) Co-authored-by: Jay Rogers <[email protected]>
…irst design, health checks, production-grade configurations, and orchestrator deployments. Added information on environment variable consistency and support for multiple operating systems, emphasizing best practices for production environments.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )