aymanalhattami

Reverb Walkthrough

This is a walkthrough of how to configure Laravel Reverb for production using services like Laravel Forge or Ploi. The first step is nginx configuration changes, then .env changes and finally spinning up your Reverb server.

1. Configuring Nginx

Ensure your nginx site configuration has the following inside the server block:

 location /app {

aymanalhattami

Pull request norms

• It's recommended to divide PR into independently mergeable parts. This not only promotes simpler designs but also reduces coupling.
• It's best to break down the PR into smaller related commits rather than having a single PR with many changes. Reviewers find it difficult to go through 50+ file changes in one go.
• At least 1-2 developer approvals are required for a PR review, except for simple changes like typo fixes or documentation updates.
• A well-written description of the PR is crucial for the reviewer to understand the code's purpose.
• Additionally, PR labels can help to give a clearer picture of the PR's status or functionality.

Here's an example of a PR with related commit messages -

aymanalhattami

Git Commit Best Practices - How to Write Meaningful Commits

The purpose of this gist is to gather the best practices for using git in one convenient location and to educate more people about the standards. Especially when collaborating with others, it is essential to establish conventions to follow.

Commit Message norms

1. Make clean, single-purpose commits

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. It is better to keep commits as small and focused as possible for many reasons, some of them include: