www.b65.ch

2024-11-24T00:22:09+00:00

Nick and Kee just want to dust off their Commodore 64. One more trip back to the world of Space Invaders, Pac-Man, and Donkey Kong. But their nostalgia trip ends with a surprise: in a game from the 1980s, the aging joystick heroes discover a secret message.

WELCOME TO DATACORP

Suddenly, their old hacker instincts are reawakened. The friends embark on a hunt through the jungle of bytes—and find another clue: it leads to Iowa, deep in the American Midwest. Now there’s no turning back. Magically drawn into a digital treasure hunt, the duo sets off on a journey to the USA. For these hobby computer archaeologists, an odyssey begins that spans half the world—and the history of games. But in the end, this game is about much more than just the next high score.

The start of the Nick and Kee Series and my introduction to Constantin Gillies the author of the series.

I initially encountered the book in audiobook format, but found it compelling enough to revisit in its written form.

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

The aging computer kids from the 1980s have long since found their way into the real world. Now, as secret IT agents, they rescue data from outdated computer systems. However, the thrill of adventure has long faded, and their lives now revolve around suburban homes, travel expenses, and mowing the lawn. Until a sudden death shatters the routine: Charles Irving, a legendary computer pioneer, collapses during his final public appearance. All that remains is his laptop, vintage 1982. Nick and Kee, the data rescuers, are tasked with safeguarding his digital legacy. But the mission quickly turns into a trap: unknown adversaries are tracking the friends, wiretapping them, and breaking into Nick’s house. Overnight, the hunters of lost data become the hunted themselves. A breathless chase across time zones begins—always following the trail of Irving’s last secret. And this secret seems to be worth more than a single life.

A story about growing up, friendship, and the yearning for the exciting days of the computer pioneer era, when life revolved around the C-64, Amiga, and other iconic machines.

The second novel in the Nick and Kee Series... the saga continues ;)

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

Bifröst: A Lightweight and Customizable Homepage Dashboard

In Norse mythology, Bifröst is the bridge between the land of mortals, Midgard, and the land of the gods, Asgard. The gods cross it every day to meet and decide things at Urdarbrunn (Well of Urd) under the tree Yggdrasill. The bridge is a rainbow. It was built by the Æsir and is guarded by the god Heimdall.

Bifröst is a minimalist startpage dashboard, offering a sleek and simple interface for managing quick links in your web browser. Forked from jeroenpardon/sui, Bifröst adds practical enhancements while maintaining a small footprint of just 125kb. Its primary purpose is to create a personal, easily configurable homepage that can be adapted to individual preferences.

Customization is made easy with a JSON-based configuration, allowing users to create and organize their sections with ease. Whether it’s for organizing bookmarks, monitoring services, or quickly accessing important web tools, Bifröst offers flexibility and functionality. Users can control its appearance and manage sections according to their specific needs, making it an ideal tool for those who like to personalize their browsing experience.

Additionally, Bifröst supports Docker, making the setup process streamlined for those who want to self-host it. With simple access control options and lightweight resource demands, this dashboard is designed for efficiency, offering a powerful solution for those who prefer a clean, fast, and efficient startpage without unnecessary bloat.

Check out the repository here to learn more about the customization possibilities of Bifröst.

2024-11-24T00:22:09+00:00

Measure Internet Speed with Fast.com

This project allows you to measure internet speed using the Fast.com CLI and send the results directly to an MQTT broker via a Docker container. You can set environment variables like SLEEP, MQTT_SERVER, MQTT_DOWN, and MQTT_UP to configure the interval between tests and topics for download/upload data. Optional authentication via MQTT_USER and MQTT_PASS is also supported.

This setup makes it easy to integrate network speed monitoring with an existing MQTT infrastructure.

You can find the source code and the instructions to run the docker container on https://github.com/simonjenny/fastcom-mqtt.

2024-11-24T00:22:09+00:00

Pac-Man in the arcade. Music from vinyl. No smoking bans. No cell reception—and only payphones. This is the world of Retroland, a theme park that recreates the 1980s. It’s here that Nick and Kee, two graying nerds, plan to spend one last buddy vacation together. But then the unthinkable happens: a stranger shoots at Kee, and the friends are forced to flee. It quickly becomes clear that they are not the target. Their pursuers are after a floppy disk Kee is carrying. A frantic chase through the bizarre backdrop of Retroland begins. But it’s not just Nick and Kee whose lives are in danger...

The final installment of the series. Will Kee get the girl? :)

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

If you are using the EFA bus timetable you can add a Departure Bus Timetable like this to your Home Assistant instance:

First up we need to configure a Rest Sensor in Home Assistant that will return the JSON response from the EFA API. Add this code to your configuration.yaml file. You will need to replace the "nameInfo_dm" with your desired station ID. You can find a list of station IDs here.

 - platform: rest
   unique_id: '7ed6dfcd3dbc7544c7c880d265b4bc54'
   resource: https://www.efa-bw.de/bvb3/XML_DM_REQUEST?laguage=de&typeInfo_dm=stopID&deleteAssignedStops_dm=1&useRealtime=1&mode=direct&outputFormat=rapidJSON&limit=4&nameInfo_dm=53032154&version=10.5.17.3
   scan_interval: 60
   json_attributes:
      - "stopEvents"
   name: "Abfahrten"

Then we need to add the sensor to our lovelace UI:


type: vertical-stack
cards:
  - type: custom:mushroom-title-card
    title: Abfahrten
  - type: horizontal-stack
    cards:
      - square: false
        columns: 2
        type: grid
        cards:
          - type: custom:mushroom-template-card
            primary: >-
              {{state_attr('sensor.abfahrten','stopEvents')[0].transportation.destination.name}}
            secondary: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[0].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t > 0) %}
              in {{t | round }}'  {% elif (t < 0) %} Verpasst {% elif (t > 59)
              %} Später {% elif (t > 120) %} Morgen {% endif %}
            icon: mdi:bus
            entity: sensor.abfahrten
            layout: horizontal
            tap_action:
              action: none
            hold_action:
              action: none
            double_tap_action:
              action: none
            icon_color: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[0].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t < 5) %}
              red {% elif (t < 9) %} orange {% elif (t > 8) %} green {% endif %}
            badge_icon: ''
            badge_color: ''
          - type: custom:mushroom-template-card
            primary: >-
              {{state_attr('sensor.abfahrten','stopEvents')[1].transportation.destination.name}}
            secondary: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[1].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t > 0) %}
              in {{t | round }}'  {% elif (t < 0) %} Verpasst {% elif (t > 59)
              %} Später {% elif (t > 120) %} Morgen {% endif %}
            icon: mdi:bus
            entity: sensor.abfahrten
            layout: horizontal
            tap_action:
              action: none
            hold_action:
              action: none
            double_tap_action:
              action: none
            icon_color: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[1].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t < 5) %}
              red {% elif (t < 9) %} orange {% elif (t > 8) %} green {% endif %}
            badge_icon: ''
            badge_color: ''
          - type: custom:mushroom-template-card
            primary: >-
              {{state_attr('sensor.abfahrten','stopEvents')[2].transportation.destination.name}}
            secondary: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[2].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t > 0) %}
              in {{t | round }}'  {% elif (t < 0) %} Verpasst {% elif (t > 59)
              %} Später {% elif (t > 120) %} Morgen {% endif %}
            icon: mdi:bus
            entity: sensor.abfahrten
            layout: horizontal
            tap_action:
              action: none
            hold_action:
              action: none
            double_tap_action:
              action: none
            icon_color: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[2].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t < 5) %}
              red {% elif (t < 9) %} orange {% elif (t > 8) %} green {% endif %}
            badge_icon: ''
            badge_color: ''
          - type: custom:mushroom-template-card
            primary: >-
              {{state_attr('sensor.abfahrten','stopEvents')[3].transportation.destination.name}}
            secondary: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[3].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t > 0) %}
              in {{t | round }}'  {% elif (t < 0) %} Verpasst {% elif (t > 59)
              %} Später {% elif (t > 120) %} Morgen {% endif %}
            icon: mdi:bus
            entity: sensor.abfahrten
            layout: horizontal
            tap_action:
              action: none
            hold_action:
              action: none
            double_tap_action:
              action: none
            icon_color: >-
              {% set t =
              ((state_attr('sensor.abfahrten','stopEvents')[3].departureTimeEstimated
              | as_datetime - now()).total_seconds() // 60)  %} {% if (t < 5) %}
              red {% elif (t < 9) %} orange {% elif (t > 8) %} green {% endif %}
            badge_icon: ''
            badge_color: ''

I am using the "mushroom-template-card" from the Mushroom repository.

And that's all there is to this.

2024-11-24T00:22:09+00:00

Computer forensic expert Schröder is facing a system crash. On one hand, there’s his new colleague Harriet—smart and sexy like Star Trek’s Seven of Nine. On the other, he’s investigating a mysterious murder: a nerd was shot, his computer destroyed. Using a clever trick, Schröder and Harriet manage to recover the data. Among it, they find numerous images of the moon, which the victim had restored for NASA. What did the deceased discover in the moon photos that he wasn’t supposed to see? The trail leads Schröder and Harriet to the vibrant city of Las Vegas, where they move from one dangerous situation to the next...

A dead nerd, a butt check on seven of nine and a mysterious object... then next series from Constantin Gillies is up to a furious start :)

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

Computer forensist Schröder has hit rock bottom: he's been fired from his company and dumped by his girlfriend Harriet. But a murder suddenly turns everything around: A man is poisoned with a chemical warfare agent at the airport. The only evidence is his digital watch, a model from the Eighties.

Investigator Harriet, who has been assigned to the case, asks Schröder to examine the relic. He senses that this might be his second chance with her and agrees. But suddenly everything goes awry: Hackers attack Harriet's computer, Schröder's neighbor is beaten up, and his friend Leines disappears without a trace.

The IT experts are themselves targeted by the perpetrators and time is running out for them: 00:10, 00:09...

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

Computer forensist Schröder can't believe it: his former colleague Harriet actually wants him to work with her at their company! Can he handle sitting next to this woman every day, who is clever and sexy like Seven of Nine from "Star Trek"? As Schröder still grapples with this idea, a mysterious assignment suddenly comes in: the US military asks Harriet and Schröder to repair the software of a spy satellite that's tumbling through orbit. Reluctantly, the IT experts agree.

But it quickly becomes clear that they're dealing with an extremely special old system. The trail leads back to the time of the Cold War - and the assignment turns into a deadly trap...

After the novels "The Object" and "00:01", this is the thrilling finale of the Schröder series... or so?

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

A task I often forget when developing Laravel Applications is updating .env.example. So I created a quick command to do that for me. Of course you could add this also to your CI pipeline, but ever so often a simple command like this is good enough.

The result of this you can view in the Github Repository or you simply add the package to your project via composer:

composer require --dev kuvvu/envexample

There are also some configuration options available:

<?php

return [

    /* Create a copy/backup of current env.example at start */

    'create_bakup' => false,
    'backup_file_name' => 'env.example.bak',

    /* All keys in this array will not be cleared upon copying to .env.example */

    'keep' => [
        'APP_NAME',
        'DB_CONNECTION',
        'DB_PORT',
        'MAIL_MAILER',
        'MAIL_HOST',
        'MAIL_PORT',
        'MAIL_ENCRYPTION',
        'MAIL_FROM_ADDRESS',
        'MAIL_FROM_NAME',
        'LOG_CHANNEL',
        'LOG_DEPRECATIONS_CHANNEL',
        'LOG_LEVEL',
        'BROADCAST_DRIVER',
        'CACHE_DRIVER',
        'FILESYSTEM_DISK',
        'QUEUE_CONNECTION',
        'SESSION_DRIVER',
        'SESSION_LIFETIME',
        'AWS_DEFAULT_REGION',
        'AWS_USE_PATH_STYLE_ENDPOINT',
        'AWS_URL',
        'AWS_ENDPOINT',
        'MEMCACHED_HOST',
        'REDIS_HOST',
        'REDIS_PORT',
    ],

    /* All keys in this array will not be copyied to .env.example */

    'ignore' => [],

];

To use this you need to publish the config file:

php artisan vendor:publish --tag=env-example

Updating the .env.example file then is as simple as:

php artisan make:env.example

2024-11-24T00:22:09+00:00

This blog was born from my idea to create a straightforward markdown-based blog using Laravel. While searching online, I often came across pre-built packages that were either overloaded with unnecessary features or didn’t meet my specific needs.

That’s when I started wondering if it was possible to build something much simpler.

I stumbled upon a blog post on codingwithstef.com, which provided a great starting point, as the author aimed to create a basic model using the filesystem, but I decided to ditch the filesystem approach and instead use the Sushi Model Driver for handling the Posts, since the Filesystem approach would not be easily paginating through all of my posts and felt slow.

For this project, I used spatie/yaml-front-matter to parse the Markdown files and spatie/laravel-markdown to render the content.

With that foundation, here’s how I developed a simple Blog model:

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Support\Facades\File;
use Spatie\LaravelMarkdown\MarkdownRenderer;
use Spatie\YamlFrontMatter\YamlFrontMatter;

class Blog extends Model
{
    use \Sushi\Sushi;

    public $incrementing = false;

    protected $primaryKey = 'slug';

    protected $keyType = 'string';

    protected function sushiShouldCache()
    {
        return true;
    }

    protected $casts = [
        'meta' => 'array',
    ];

    public function getRows()
    {
        $rows = [];
        foreach (File::files(storage_path(env('BLOG'))) as $file) {

            $markdown = new MarkdownRenderer;
            $yaml = YamlFrontMatter::parse(File::get($file->getRealPath()));

            $row['meta'] = json_encode($yaml->matter());
            $row['slug'] = str_replace('.md', '', $file->getBaseName());
            $row['body'] = $markdown->disableAnchors()
                ->highlightTheme('github-dark')
                ->toHtml($yaml->body());

            $rows[] = $row;
        }

        return $rows;

    }
}

How you design your views is entirely up to you. You can create a custom template or choose a default one from the web—whatever suits your needs.

I then further decided to add a SEO Package to add the necessary SEO tags.

namespace App\Http\Controllers;

use App\Helpers\Tools;
use App\Models\Blog;
use Illuminate\Http\Request;

class BlogController extends Controller
{
    public function index(Request $request)
    {

        seo()
            ->title('B65')
            ->description('a nerdy dev blog')
            ->twitter();

        return view('blog.index', ['posts' => Blog::orderBy('slug', 'DESC')->simplePaginate(5)]);
    }

    public function post(Request $request, $slug)
    {
 
        $post = Blog::where('slug', $slug)->firstOrFail();

        seo()
            ->title($post->meta['title'])
            ->description($post->meta['excerpt'])
            ->image($post->meta['image'] ?? '')
            ->twitter();

        return view('blog.post', ['post' => $post]);
    }
}

Finally you also will be needing the Routes for your Blog Controller:

Route::get('/', [BlogController::class, 'index']);
Route::get('/{slug}.html', [BlogController::class, 'post']);

I hope this article was helpful. If you have any questions or suggestions please let me know in the comments section below.

2024-11-24T00:22:09+00:00

Computer forensist Schröder can't believe his luck! First, he gets hold of this old East German computer, and then he finds a mysterious address on it too. The IT expert decides on the spot to visit the place...

48 hours later, his girlfriend Harriet lies bleeding on the floor of a secret military facility.

After "The Object", "00:01", and "System Crash", the fourth novel about the quirky computer forensist Schröder.

Buy the Ebook@Amazon

2024-11-24T00:22:09+00:00

I know, I know—criticizing WordPress feels like walking into a room and telling everyone their favorite show is overrated. But the reality is, we need to have an honest conversation about the platform and whether it's really the best solution for your website, especially if you fall into the majority who use WordPress to display fewer than 10 content pages with rare or no updates.

The Problem with Over-Engineering Simplicity

WordPress started as a blogging platform and evolved into a content management system (CMS) used by millions of websites worldwide. Its flexibility and user-friendly interface are undeniably appealing. However, the problem arises when people use WordPress for small, static websites that don’t require its vast array of features. These sites might have 5-10 pages, rarely updated, and serve a simple purpose—yet they’re powered by an infrastructure designed for much more complex use cases.

The result? Over-engineering. When you use WordPress for something as simple as a small business website or a personal portfolio, you're employing a solution designed for much larger needs. You’re maintaining a system that involves databases, frequent updates, plugins, and security measures—all for a static site that doesn’t require any of that complexity. It’s like using a Swiss Army knife to open a letter: yes, it works, but it’s far from the most efficient tool.

Performance Issues and Security Risks

One of the major drawbacks of using WordPress unnecessarily is performance. Every WordPress page load triggers numerous database queries, which can slow down your site, especially when not optimized correctly. For a static site, this is completely unnecessary, and can result in sluggish performance that affects user experience and search engine rankings.

Additionally, security is a growing concern. WordPress sites, particularly those that aren’t regularly updated, are prime targets for hackers. An outdated plugin or an unpatched vulnerability can make your website an easy entry point for malicious actors. For a static site, this risk is avoidable by using simpler, more secure alternatives.

Alternatives: Static Site Generators to the rescue!

If you’re running a small website that doesn’t need dynamic content or frequent updates, there are more efficient alternatives than WordPress. Static site generators (SSGs) like Jekyll, Hugo, or 11ty allow you to create fast, secure websites that don’t rely on databases or complex infrastructures. These tools generate simple HTML, CSS, and JavaScript files, which can be hosted almost anywhere with little to no maintenance. Since there are no backend processes to manage, they also reduce security risks and performance issues.

The Hidden Costs of WordPress Maintenance

Many people choose WordPress because it’s free, but "free" is a bit of a misnomer. Maintaining a WordPress site involves regular updates, plugin management, backups, and security measures. If you’re not tech-savvy, you’ll likely need to hire someone to manage these aspects, turning your "free" website into a recurring cost center.

By moving to a simpler solution, you can reduce the need for ongoing maintenance and cut down on expenses, while still having a website that serves its purpose.

Final Thoughts: Simplicity Is Key

WordPress is a powerful tool, but it’s not always the right one for the job. If you’re managing a small, static website with little need for dynamic features, consider switching to a simpler, more efficient solution. You’ll save yourself time, money, and headaches in the long run.

At the end of the day, it’s not about hating WordPress—it’s about using the right tool for the job. And sometimes, less is more. Do you agree? Let me now in the comments below!

2024-11-24T00:22:09+00:00

For developers and tech-savvy commuters who rely on public transit, finding efficient ways to plan and navigate trips is crucial. Enter EFA-CLI, an open-source command-line interface (CLI) designed to help users access public transport data from EFA (Elektronische Fahrplanauskunft), a system widely used in Germany, Austria, and other European countries.

The EFA-CLI repository offers a streamlined way to interact with public transit schedules, stop locations, and route information—all from your terminal. It simplifies the process of retrieving transit data without needing to open a web browser or use third-party apps.

Key Features of EFA-CLI

Route Planning: With EFA-CLI, you can easily plan your public transport journeys by entering your departure and destination points. The tool retrieves route options, travel times, and transfers, helping you make informed decisions quickly.
Location Queries: The CLI allows users to search for stop locations, giving you real-time data about nearby stations and bus stops. This feature is especially helpful when you're in an unfamiliar area or when navigating large transit networks.
Customization: The tool provides several customization options, such as specifying different transit authorities, and modes of transport, or filtering results based on personal preferences. This flexibility makes EFA-CLI a powerful utility for commuters with specific needs.

Why Use EFA-CLI?

If you're a developer or tech enthusiast who prefers the command line for day-to-day tasks, EFA-CLI is a great fit. It brings efficiency to transit planning, reducing the need for third-party apps while offering complete control over your transit data queries.

To get started, check out the EFA-CLI repository on GitHub. It’s well-documented and easy to install, making it a great tool for enhancing your transit navigation experience.

Installation

wget https://github.com/simonjenny/efa-cli/blob/master/builds/efa?raw=true -O efa
chmod a+x efa && sudo mv efa /usr/local/bin

Use with Docker

docker run -it simonjenny/efa OPTIONS ARGUMENTS

2024-11-24T00:22:09+00:00

Argos is a simple, flexible extension for GNOME Shell that allows users to display dynamic information in the top bar by writing small scripts. Created by Peter Waller, it transforms shell scripts into custom drop-down menus, making it a powerful tool for developers and power users. By providing real-time updates on various system metrics, API data, or any information your script can handle, Argos enables easy monitoring and interaction right from the desktop environment.

To add a simple command to Argos, you need to create a shell script that outputs the information in a specific format. The output is then displayed as a menu item in the top bar.

In this post, I will show you how to integrate the efa-cli with Argos Gnome Extension.

Install Efa

First, install efa-cli. You can do this by running the following command in your terminal:

wget https://github.com/simonjenny/efa-cli/blob/master/builds/efa?raw=true -O efa
chmod a+x efa && sudo mv efa /usr/local/bin

Create Argos Script

Create a new file in your Argos Config Directory ~/.config/argos and name it departures.r.60s.sh. The file name declares a reload of every 60 seconds. (More information about Filename format is available on the repositories README)

Open the file with your favorite text editor and add the following code:

#!/usr/bin/env bash
r=$(efa departures "YOUR STOP NAME" --limit=1 --json | jq '.[].realtime')
echo " $r' "

Replacing YOUR STOP NAME with your desired stop name.

The Script will be added to the Menubar with the output of the realtime departure information in Minutes of the next transport at your chosen stop.

If you want a more precise output, you can use the GID to limit the output, for example, in a specific direction and spice up the output with some emojis:

#!/usr/bin/env bash
r=$(efa departures ch:23004:6192:1:1 --gid --limit=1 --json | jq '.[].realtime')
if [ $r -gt 2 ];then
  echo " 🚏 $r' "
else 
  echo " 🚌💨 "
fi

The GID of a stop can be found by using the "efa stopinfo" command.

2024-11-24T00:22:09+00:00

If you are like me and you like to have your icons in the dash neatly organized having a separator between the different categories of icons helps a lot.

This is how you do it:

Create a Separator Icon

You can use any PNG image as a separator. The image should be a square i opted for a 512x512 pixel size. You can find an example in the ZIP below.

Add the Separator to the Dash

Create a file named separator.desktop with the following content:

[Desktop Entry]
Type=Application
Icon=FULL PATH TO WHEREVER YOU KEEP THE SEPERATOR IMAGE.png
Exec=/bin/true
Name=Separator

If you like to create multiple seperators store this file somewhere eg. in your .config directory or wherever you like.

To add a seperator you simply then copy the seperator.desktop to /usr/share/applications

sudo cp separator.desktop /usr/share/applications/s1.desktop

If you have multiple separators just change the name of the file of the .desktop file.

sudo cp separator.desktop /usr/share/applications/s1.desktop
sudo cp separator.desktop /usr/share/applications/s2.desktop
sudo cp separator.desktop /usr/share/applications/s3.desktop
...

She separator icons will then appear in the dash and you can simply drag them to wherever you want them to be.

If you like you can download my separator files here: separator.zip

2024-11-24T00:22:09+00:00

Laravel is known for its robust features, but getting a project off the ground often requires configuring essential elements like routing, environment settings, and Docker support. My Laravel Skeleton repository addresses these challenges by offering a pre-configured setup tailored for quick and efficient Laravel development. It provides a foundation for my projects, allowing me to bypass repetitive setup tasks and jump straight into building core features.

One of the key advantages of this skeleton is its integration with FrankenPHP, a hybrid server technology designed for Laravel applications, utilizing Caddy for efficient routing and proxying. This ensures developers have a containerized environment ready to go, without needing to spend additional time on Docker configuration. Moreover, it trims unnecessary bloat by adjusting routing defaults, such as the removal of built-in health check routes, making the structure more streamlined and production-ready.

Additionally, the repository simplifies package management by refining the composer.json and .gitignore files. These adjustments ensure that project dependencies and file exclusions are optimized for modern development workflows. Overall, Laravel Skeleton is ideal for developers seeking a ready-made solution that enhances productivity while maintaining the flexibility of Laravel’s core framework.

To start your next Laravel Projekt with my skeleton just use:

composer create-project simonjenny/laravel-skeleton <project-name>

If you whant to revisit the changes I made first simply take a look at the repository : https://github.com/simonjenny/laravel-skeleton

2024-11-24T00:22:09+00:00

If you want to create a simple SSH Server Login Menu for your shell with all your configured Servers in your .ssh/config file, you can use this little script:

#!/bin/bash
DIALOG=${DIALOG=dialog}
tempfile=`tempfile 2>/dev/null` || tempfile=/tmp/test$$
trap "rm -f $tempfile" 0 1 2 5 15
ar=()
for i in `cat  ~/.ssh/config |grep -w  Host| sed -e "s/Host //g" | grep -Ei '[a-z]'`
do
  ar+=($i "")
done
$DIALOG --title "SSH Servers" --menu "Please choose a Server:" 30 45 10 "${ar[@]}" 2> $tempfile
retval=$?
choice=`cat $tempfile`
case $retval in
  0)
    clear
    echo "connecting $choice"
    echo ""
    ssh $choice
    server;;
  1)
    clear;;
  255)
    echo "Bye!";;
esac

This script will read your .ssh/config file and create a dialog menu with all the servers you have configured. If you select one of them, it will connect to that server via ssh.

The script uses the dialog utility which is part of most Linux distributions. You can install it on macOS using brew:

brew install dialog

or on Ubuntu/Debian:

sudo apt install dialog