eclipsephp/core

Core package for the Eclipse platform

dev-main 2025-04-18 08:59 UTC

Requires

• php: ^8.3
• bezhansalleh/filament-language-switch: ^3.1
• bezhansalleh/filament-shield: ^3.3
• datalinx/php-utils: ^2.5
• dutchcodingcompany/filament-developer-logins: ^1.6
• eclipsephp/world-plugin: dev-main
• filament/filament: ^3.3
• filament/spatie-laravel-media-library-plugin: ^3.2
• filament/spatie-laravel-translatable-plugin: ^3.2
• laravel/framework: ^11.0
• laravel/horizon: ^5.31
• laravel/telescope: ^5.5
• laravel/tinker: ^2.10
• pxlrbt/filament-environment-indicator: ^2.1
• spatie/laravel-package-tools: ^1.18
• spatie/laravel-translatable: ^6.11
• tangodev-it/filament-emoji-picker: ^1.0

Requires (Dev)

• laravel/pint: ^1.21
• orchestra/testbench: ^9.10
• pestphp/pest: ^3.7
• pestphp/pest-plugin-livewire: ^3.0

MIT

• DataLinx

• laravel
• Eclipse
• filament

README

About

This is the core package for Eclipse, a PHP app built with Filament and the TALL stack.

It's an opinionated package, containing all the core resources and other code, including our selection of Filament plugins as dependencies. It's included in all our Eclipse projects and it's purpose is to have as much code as possible, thus keeping the skeleton/app package as slim as possible to make maintenance of apps easy.

Non-opinionated code will be separated into own Filament plugins or other support packages.

Out-of-the-box features

• User management
• Roles and permissions
• Domain based multi-tenancy
• Multi-language
• Compatible with standard Laravel and Filament packages

Documentation

Read the documentation here.

Contributing

If you have some suggestions how to make this package better, please open an issue or even better, submit a pull request.

Should you want to contribute, please see the development guidelines in the DataLinx PHP package template.

Changelog

All notable changes to this project are automatically documented in the CHANGELOG.md file using the release workflow, based on the release-please GitHub action.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

For all this to work, commit messages must follow the Conventional commits specification, which is also enforced by a Git hook.