Manage Kubernetes Clusters with PHP and Laravel

 Laravel PHP K8s is a package that provides access to features offered by the excellent renoki-co/php-k8s package in Laravel. The underlying PHP K8s package is a PHP handler for the Kubernetes Cluster API. With it, you can automate the management of creating, deleting, updating, etc. individual Kubernetes resources directly from PHP.

Here is an example of how PHP K8s provides an object-oriented way to generate Kubernetes resources and configuration dynamically:

 1use RenokiCo\PhpK8s\KubernetesCluster;
 2 
 3// Create a new instance of KubernetesCluster
 4$cluster = new KubernetesCluster('http://127.0.0.1:8080');
 5 
 6// Create a new NGINX service.
 7$svc = $cluster->service()
 8    ->setName('nginx')
 9    ->setNamespace('frontend')
10    ->setSelectors(['app' => 'frontend'])
11    ->setPorts([
12        [
13            'protocol' => 'TCP',
14            'port' => 80,
15            'targetPort' => 80
16        ],
17    ])
18    ->create();

Which would equal the following YAML configuration:

 1apiVersion: v1
 2kind: Service
 3metadata:
 4  name: nginx
 5  namespace: frontend
 6spec:
 7  selector:
 8    app: frontend
 9  ports:
10    - protocol: TCP
11      port: 80
12      targetPort: 80

The Laravel PHP package helps further with the above by handling connection configuration and allowing you to access the Kubernetes cluster. Here are some examples from the readme to get a taste of what you can do with this Laravel package:

1use RenokiCo\LaravelK8s\LaravelK8sFacade;
2 
3foreach (LaravelK8sFacade::getAllConfigMaps() as $cm) {
4    // $cm->getName();
5}

There are multiple ways to connect to the cluster instance, which means you can configure them and specifiy the connection type to use from the k8s.php config:

1// Specify the cluster connection type and get the cluster
2$cluster = LaravelK8sFacade::connection('http')->getCluster();
3 
4// Get the cluster using the default connection type
5$cluster = LaravelK8sFacade::getCluster();

You can learn more about this package, get full installation instructions, and view the source code on GitHub. I'd also recommend reading through the renoki-co/php-k8s documentation to learn how to manage Kubernetes with this package.

Read More

Laravel Themer package: add multi-theme support for Laravel application

 This Laravel Themer package adds multi-theme support to your Laravel application. It also provides a simple authentication scaffolding and presets for Bootstrap, Tailwind, Vue, and React as a starting point for building a Laravel application.

In my opinion, this Laravel Themer package is a better alternative to the official laravel/ui & laravel/breeze packages because of the following features:

• Any number of themes
• Fallback theme support (WordPress style); It allows creating a child theme to extend any theme
• Provides authentication scaffolding similar to laravel/ui & laravel/breeze
• Exports all auth controllers, tests, and other files similar to laravel/breeze
• Provides frontend presets for Bootstrap, Tailwind, Vue 2, Vue 3, and React

If you don't want to use this package's auth scaffolding, instead, you want to use Laravel Fortify, no problem with that. You can use Laravel Themer with Fortify as well. Laravel Fortify is a frontend agnostic authentication backend for Laravel, and it does not provide views or frontend presets. So, use Fortify for backend authentication and Laravel Themer for your views, presets, and for multi-theme support.

Video Tutorial

Installation

Install via composer

1composer require qirolab/laravel-themer

Publish a configuration file:

1php artisan vendor:publish --provider="Qirolab\Theme\ThemeServiceProvider" --tag="config"

Creating a theme

Use the following command to create a theme:

1php artisan make:theme

Middleware to set a theme

Register ThemeMiddleware in app\Http\Kernel.php:

1protected $routeMiddleware = [
2    // ...
3    'theme' => \Qirolab\Theme\Middleware\ThemeMiddleware::class,
4];

Examples for middleware usage:

1Route::get('/dashboard', 'DashboardController@index')
2    ->middleware('theme:dashboard-theme');

Theme methods:

 1// Set active theme
 2Theme::set('theme-name');
 3 
 4// Get current active theme
 5Theme::active();
 6 
 7// Get current parent theme
 8Theme::parent();
 9 
10// Clear theme. So, no theme will be active
11Theme::clear();
12 
13// Get theme path
14Theme::path($path = 'views');
15// output:
16// /app-root-path/themes/active-theme/views
17 
18Theme::path($path = 'views', $themeName = 'admin');
19// output:
20// /app-root-path/themes/admin/views
21 
22Theme::getViewPaths();
23// Output:
24// [
25//     '/app-root-path/themes/admin/views',
26//     '/app-root-path/resources/views'
27// ]

webpack.mix.js Configuration

After creating a new theme, it creates a separate webpack.mix.js file for that theme. So, to compile the theme's webpack.mix.js file it should be included in the app's webpack.mix.js that is located in the root path.

1// add this in the root `webpack.mix.js`
2require(`${__dirname}/themes/theme-name/webpack.mix.js`);

In the case of multiple themes, If you add multiple webpack.mix.js of different themes. Then webpack may not compile these correctly. So, you should modify the root webpack.mix.js with the following code:

1let theme = process.env.npm_config_theme;
2 
3if(theme) {
4   require(`${__dirname}/themes/${theme}/webpack.mix.js`);
5} else {
6    // default theme to compile if theme is not specified
7  require(`${__dirname}/themes/theme-name/webpack.mix.js`);
8}

Now, you can use the following command to compile assets for a particular theme:

1npm run dev --theme=theme-name

Read More