Moved this snippet to a dedicated repository: https://github.com/fastvoid/laravel-dutch-validation
function my_remove_wp_seo_meta_box() { | |
remove_meta_box('wpseo_meta', YOUR_POST_TYPE_NAME_HERE, 'normal'); | |
} | |
add_action('add_meta_boxes', 'my_remove_wp_seo_meta_box', 100); |
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
There are times notifications aren't wanted about either a changed repo file or a new file that needs to be added to the repo. However, adding the name of the file to .gitignore
might not be a good option, either. For example, locally-generated files that other users aren't likely to generate (e.g., files created by an editor) or files of experimental test code might not be appropriate to appear in a .gitignore
file.
In those cases, use one of these solutions:
-
If the file is a changed repo file
Use the command:
git update-index --assume-unchanged "$FILE"
# Mailhog | |
MAIL_MAILER=smtp | |
MAIL_HOST=0.0.0.0 | |
MAIL_PORT=1025 | |
MAIL_USERNAME=null | |
MAIL_PASSWORD=null | |
MAIL_ENCRYPTION=null |
<?php | |
namespace Tests\Feature; | |
use App\User; | |
use Tests\TestCase; | |
use Livewire\Livewire; | |
use Illuminate\Support\Facades\Route; | |
use Illuminate\Foundation\Testing\RefreshDatabase; |