wpwwhimself/shipyard

A starting piece for WPWW's website, with many useful things to accelerate building new things

v2.23.0 2026-04-01 11:58 UTC

Requires

• andcarpi/laravel-popper: ^0.9.4
• illuminate/console: ^12.7
• illuminate/support: ^12.7
• laravel/sanctum: ^4.0
• owen-it/laravel-auditing: ^14.0
• postare/blade-mdi: ^1.1
• spatie/laravel-backup: ^9.1
• wildside/userstamps: ^3.1

Requires (Dev)

• barryvdh/laravel-debugbar: ^3.16

MIT

• Wojciech Przybyła

• framework
• laravel
• shipyard
• wpwwhimself
• starter-pack

README

This project is a framework for my own web apps.

Concepts

This template aims to create a starting point (and a joint upgrade environment, IYKWIM) for all projects made usually for environments without luxury of npm – like on a shared hosting. That's why it covers a specific scenario:

• no NPM reliance
  • no asset bundling (Vite)
  • no big frontend frameworks (React, Vue)

How to start?

Shipyard requires Laravel installation.

1. Add Composer settings:

{
    ...
    // refresh Shipyard after updates
    "scripts": {
        ...
        "post-update-cmd": [
            ...
            "@php artisan shipyard:install"
        ],
    },
    ...
}

1. Fill out important fields in .env, mainly:

   • DB_?? - required for migrations,
   • MAIL_FROM_ADDRESS - required for archmage user migration,

2. Install package:

composer require wpwwhimself/shipyard

Dev mode - load Shipyard from a directory next door

1. In a joint folder, clone this repository into shipyard subfolder
2. Install Laravel app in a app subfolder
3. Add Composer settings:

{
    ...
    // appends Shipyard repository
    "repositories": {
        "shipyard": {
            "type": "path",
            "url": "../shipyard",
            "options": {
                "symlink": true
            }
        }
    },
    ...
}

1. Add Composer env variables to load shipyard locally and install package:

composer require wpwwhimself/shipyard:dev-main