Download the PHP package liquidstack/core without Composer

On this page you can find all versions of the php package liquidstack/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 core

Liquid Stack Core

liquidstack/core es el paquete comun para proyectos Liquid Stack. Centraliza:

Como sincroniza en proyectos cliente

Al ejecutar composer install o composer update en un proyecto que consume este paquete:

  1. Se copian stubs backend desde stubs/ al proyecto.
  2. Se copian recursos frontend:
    • resources/js -> src/js/resources (y copia en vendor/liquidstack/core/resources/js).
    • resources/scss -> src/scss/resources (y copia en vendor/liquidstack/core/resources/scss).
    • resources/img -> public/assets/img.
  3. Se fusionan dependencias de package.core.json en el package.json del proyecto consumidor.

Scripts disponibles:

Alias legado soportado:

Variables de entorno soportadas:

Checklist: traer un recurso nuevo desde liquidstack_base

Usa esta lista cada vez que subas un recurso nuevo al core.

1) Frontend del recurso

Nota de estructura de imagenes

Esa estructura se conserva en destino. Ejemplo:

2) Registro del recurso en plantillas base del core

Importante sobre src/scss/_config.scss, src/scss/_global.scss y src/js/_global.js

Esos archivos no se sincronizan automaticamente a proyectos cliente en el instalador actual. Solo se sincronizan de src/:

Por tanto:

3) Backend/stubs del recurso

4) Dependencias NPM del recurso

Si el recurso necesita librerias nuevas (ejemplo three):

Reglas de fusion en proyecto cliente:

Guia de trabajo local (localhost:1309)

Este repositorio no trae una app completa para renderizar por si solo. La forma recomendada es trabajar con un proyecto laboratorio basado en liquidstack_base usando este core local enlazado.

Paso 1) Preparar proyecto laboratorio

En el composer.json del proyecto laboratorio, usar repositorio path hacia este core local:

Luego:

Con symlink: true, los cambios que hagas en este repo se reflejan en el proyecto laboratorio.

Paso 2) Instalar frontend del laboratorio

Paso 3) Levantar Vite en puerto 1309

Si el script dev del laboratorio ya fija host/port, basta con npm run dev.

Paso 4) Refrescar sincronizaciones cuando toque

Si cambias recursos en resources/:

Si cambias dependencias en package.core.json:

Si cambias stubs o src/js/templates.js / src/scss/templates.scss, ejecuta:

Publicacion de cambios del core

  1. Subir cambios al repo de liquidstack/core.
  2. Etiquetar version SemVer.
  3. En cada proyecto cliente: composer update liquidstack/core.
  4. Ejecutar instalacion frontend del proyecto (npm install, pnpm install o yarn install) si se anadieron dependencias.

All versions of core with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer-plugin-api Version ^2.0
vlucas/phpdotenv Version ^5.6
phpmailer/phpmailer Version ^6.9
symfony/filesystem Version ^6.4
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 liquidstack/core contains the following files

Loading the files please wait ...