Download the PHP package wg-vn/lunar-core without Composer

On this page you can find all versions of the php package wg-vn/lunar-core. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package lunar-core

wg-vn/lunar-core

Lunar's e-commerce core for Laravel, forked from the 2.x line of lunarphp/lunar to run on the current majors of the Spatie and Scout packages a host app is likely to use already. Not affiliated with LunarPHP Ltd.

This repository is a copy of the upstream monorepo. Only packages/core is published, as wg-vn/lunar-core, and it replaces lunarphp/core, so Lunar add-ons that require lunarphp/core install on top of it. The PHP namespace stays Lunar\Core\. For everything Lunar itself does, see the Lunar documentation.

How it differs from upstream

Upstream lunarphp/core 2.x wg-vn/lunar-core
spatie/laravel-activitylog ^4.10 ^5.1
laravel/scout ^10.13 ^11.7
spatie/laravel-permission ^6.12 ^8.3
activity_log and permission-table migrations shipped in core not shipped; the host app owns these tables
Staff roles and permissions seeded after migrate always behind lunar.staff.seed_roles_and_permissions (default true)
Causer of core's own activity entries auth()->user(), set explicitly activitylog's CauserResolver (the signed-in user unless the app overrides it)
media table migration always runs behind lunar.database.create_media_table (default true)
Route parameter for every model ({tag}, {customer}...) always bound behind lunar.routing.bind_models (default true)

Core's own migrations for the activity_log and permission tables skipped tables that already existed on the way up, but dropped them on the way down. Rolling back Lunar's migrations in an app that owns those tables deleted its audit log and every role and permission.

Installation

The host app must create the activity_log table and the permission tables from spatie/laravel-activitylog 5 and spatie/laravel-permission 8 (publish their migrations).

An app that runs no Lunar staff panel and keeps its own roles in the permission tables should publish Lunar's config and set:

An app that creates spatie/laravel-medialibrary's media table in its own migration should set:

Core binds a route parameter named after every model, app-wide. An app with a route that uses one of those names for something else ({tag}, {customer}, {order}, or another package's route such as Horizon's /monitoring/{tag}) should set the switch below and bind the models it needs itself:

Keeping up with upstream

Conflicts land in the files this fork owns: composer.json, .gitattributes, .github/workflows, README.md, CHANGELOG.md, phpstan.neon.dist, plus any core file changed above. Keep the fork's side of each. A new upstream dependency in packages/core/composer.json goes into the root composer.json too, since the root file is the one Packagist publishes.

Then run the checks CI runs:

Releasing

Versions follow upstream's with one more segment: the first release built on upstream 2.0.0-alpha.6 is v2.0.0-alpha.6.1, the next one v2.0.0-alpha.6.2, and the first after merging upstream 2.0.0-alpha.7 is v2.0.0-alpha.7.1.

  1. Add a ## [x.y.z...] section to CHANGELOG.md.
  2. Tag and push that tag only: git tag v2.0.0-alpha.6.1 && git push origin v2.0.0-alpha.6.1. Never git push --tags: the local clone may hold upstream's tags.
  3. The Publish to Packagist workflow asks Packagist to re-read the repository and creates a GitHub Release from the changelog section.

The workflow updates an existing Packagist package. The first time, submit https://github.com/wg-vn/lunar once at https://packagist.org/packages/submit.

License

MIT. Lunar is copyright LunarPHP Ltd; see LICENSE.md.


All versions of lunar-core with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
ext-bcmath Version *
ext-exif Version *
ext-intl Version *
laravel/framework Version ^12.0|^13.0
laravel/scout Version ^11.7
lukascivil/treewalker Version 0.9.1
lunarphp/nestedset Version ^1.0
spatie/laravel-activitylog Version ^5.1
spatie/laravel-blink Version ^1.7.1
spatie/laravel-medialibrary Version ^11.12.7
spatie/laravel-model-states Version ^2.11
spatie/laravel-permission Version ^8.3
spatie/php-structure-discoverer Version ^2.3.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wg-vn/lunar-core contains the following files

Loading the files please wait ...