viezel

alias: "EV Charging OFF"
description: ""
trigger:
  - platform: numeric_state
    entity_id: sensor.solar_realtime_power
    for:
      hours: 0
      minutes: 1
      seconds: 0
    below: 1

viezel

regions:
  - eu-west-1
  - global

account-blocklist:
- 1234567890

accounts:
  "888222333444": {} # your account id

viezel

Quickly get Octane running on Laravel Forge

• Spin up a new App server, choose PHP 8
• SSH into it and run sudo -i to become root
• Run pecl install swoole and enable what you need. (I disabled curl as it did not work for me)
• Add a new site to your server and use git to pull in your Laravel project that has Octane installed.
• Go to "Network" within the overall server settings
• Add new Firewall rule
  • name: Swoole
• port: 9501

viezel

Quickly get Octane running on Laravel Forge

1. Spin up a new App server, choose PHP 8
2. SSH into it and run sudo -i to become root
3. Run pecl install swoole and enable what you need. (I disabled curl as it did not work for me)
4. Add a new Site to your server and use git to pull in your Laravel project that has Octane installed.
5. Point your DNS to your new site
6. Enable SSL using Lets Encrypt
7. Change your new Sites Nginx settings to (assuing your site is named octane.example.com):

viezel

Intro

I wanted to quickly take Laravel Octane beta for a spin, as we have been using Swoole for some time and wanted to see how official support performs vs what we have.

Test 2: Forge server

Next test is more real world as we now have a web server and database server within a VPC.

Using Laravel Forge

viezel

Gitlab CI: Build docker images and deploy to AWS ECR

It takes some tries to get Gitlab CI to build and deploy to AWS, since you need to use docker in docker (dind). Here is what works for me.

Notice: Gitlab runner

• runner must be privileged
• see changes to runner volumes

viezel

Use Invoker with Docker

composer require viezel/dock --dev
php artisan dock:install

Now publish the docker-compose

viezel

fields @timestamp, @message

# Lambda
| filter @message not like "START RequestId"
| filter @message not like "END RequestId"
| filter @message not like "REPORT RequestId"

# FPM
| filter @message not like "NOTICE: ready to handle connections"
| filter @message not like "NOTICE: fpm is running"

viezel

SELECT 
    table_schema 'Database Name',
    SUM(data_length + index_length) 'Size in Bytes',
    ROUND(SUM(data_length + index_length) / 1024 / 1024, 2) 'Size in MiB'
FROM information_schema.tables 
GROUP BY table_schema;

viezel

Possible bug: Config persists between queue jobs ?

I think i found a bug in handling of queue jobs in Laravel. If I run laravel queue jobs with config cached in laravel, then runtime configs persists between jobs.

Expected result: Second job does not know of runtime config.

How to reproduce