✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨
SUPPORT MY WORK - Everything Helps Thanks
YouTube 🔗 https://YouTube.GetMeTheGeek.com
Buy Me a Coffee ☕ https://www.buymeacoffee.com/getmethegeek
Hire US 🔗 https://getmethegeek.com
Digital Ocean referral 🔗 https://tiny.cc/plxdigitalocean
✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨
name: Security audit | |
on: | |
schedule: | |
- cron: '0 0 * * *' | |
push: | |
paths: | |
- '**/Cargo.toml' | |
- '**/Cargo.lock' | |
jobs: | |
security_audit: |
image: "rust:latest" | |
default: | |
before_script: | |
- rustc --version | |
- cargo --version | |
stages: | |
- test |
<?php | |
namespace App\Traits; | |
trait HasLinks | |
{ | |
// $model->links = array | |
public function getLinksAttribute(): array | |
{ |
<?php | |
/** | |
* In your Livewire model for the list of items | |
*/ | |
class ItemList extends Component | |
{ | |
// rest of component |
Original AlpineJS | Svelte Translation | Explanation |
---|
There are many approaches to implementing a reuse of a common preset for Docker services for multiple environments, such as production and local environments.
This makes it possible to ensure the highest consistency for different environments with the same code-base. Implementing reuse of docker compose options also makes it easier to manage them.
I found on github a project called serversideup/spin. They took an approach using a feature called Docker overrides, to change some properties of common services for different environments.
After reading through their documentation, I realized that there are a few real-life cases where this project can not implement (or is difficult to archive).
2023/12/18: This script has been improved and moved to the following repository:
https://github.com/shinsenter/docker-squash
You are probably wondering how Laravel made some starter kits to be easily installable using just the following commands:
composer install laravel/breeze # Quickly integrates the starter kit to the composer environment
php artisan breeze:install # Quickly integrates the starter kit to the Laravel environment
If you want to build a project with the same installation setup, you are on the right track. This documentation is all about doing exactly just that. Without further ado, let's just jump right into it!
name: Deploy Application | |
env: | |
SIDECAR_APP_NAME: ${{ secrets.SIDECAR_APP_NAME }} | |
SIDECAR_ACCESS_KEY_ID: ${{ secrets.SIDECAR_ACCESS_KEY_ID }} | |
SIDECAR_SECRET_ACCESS_KEY: ${{ secrets.SIDECAR_SECRET_ACCESS_KEY }} | |
SIDECAR_REGION: ${{ secrets.SIDECAR_REGION }} | |
SIDECAR_ARTIFACT_BUCKET_NAME: ${{ secrets.SIDECAR_ARTIFACT_BUCKET_NAME }} | |
SIDECAR_EXECUTION_ROLE: ${{ secrets.SIDECAR_EXECUTION_ROLE }} | |
VAPOR_API_TOKEN: ${{ secrets.VAPOR_API_TOKEN }} |