Download the PHP package abollinger/partez without Composer

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


A simple & fast PHP starter kit for web app.

πŸ› Report Bug | See on Packagist πŸ“¦οΈ

Total Downloads Latest Stable Version License

partez is a PHP starter kit designed to help developers quickly set up and manage a PHP web application. It includes robust backend support with streamlined front-end automation via bricolo, a JS package that compiles assets, serves your app, and provides live reloading for a smooth development workflow.

  1. Getting Started
    • Requirements
    • Installation and Setup
  2. How It Works
    • Configuration
    • The Router
    • The Pages
    • The Public Folder
    • The API
  3. Bricolo JS Automation
    • Configuration
    • Usage
  4. Built With
  5. Contributing
  6. Contact

Getting started

Requirements

Installation and Setup

  1. Project Setup: Create a new folder for your project and open a terminal in it.

  2. Install the PHP Framework: Run this command to install partez and its dependencies:

  3. Create a .env File: If not automatically created, create a .env file at the project root. You can use .env.example as a reference.

  4. Automatic Front-End Setup with bricolo: bricolo is automatically installed via npm as part of the post-create command in composer.json. This includes asset compilation and live reloading. If you run the create-project command with --no-script options, you should run npm install to make sure that bricolo will be available.

  5. Run the Development Server: Start the server with the command below to view the app in your browser at localhost:1234 (the port may change according to the other ports already in use on your machine. Please check the log in the console):

How it works

Configuration

  1. HTML Customization: Modify the HTML layout in src/views/Layout.twig to adjust the document head.

  2. Routing: Routes are automatically derived from controllers in src/Controllers using specific annotations (see below).

The Router

Define routes in src/Controllers files using PHP annotations:

The Pages

Controllers in src/Controllers extend the main controller (Abstract/Controller.php). The init() method call renderPage("Page.twig") to render the Twig template. Each page extends the main layout in src/views/Layout.twig.

The Public Folder

The public directory houses index.php, as well as js, css and images folders, which can be customized freely.

The API

A basic API is available in api/ and runs on a MySQL database.

Bricolo JS Automation

The Partez PHP framework includes bricolo as an automation tool for front-end tasks, so you can focus on development without needing to handle asset compilation or live reloading setup yourself. bricolo is installed automatically during setup, and it's already configured with a bricoloconfig.json file that defines custom settings to integrate with this project.

You can find more information on the npm of the bricolo (js) package.

Bricolo JS Configuration

bricolo is automatically installed within the project and configured with the file bricoloconfig.json:

Configuration Overview

Usage

After creating the project, you can simply start the bricolo automation and server:

Or, if you prefer, use the command directly:

This command will:

  1. Start the PHP server on port 8080.
  2. Compile and watch for changes in JavaScript and Sass files.
  3. Automatically reload the browser at localhost:1234 whenever changes are detected in watched files.

Build with

The basic structure is:

Contributing

We welcome contributions! Here’s how to contribute:

Contact

If you have any questions, feel free to reach out:

Antoine Bollinger - LinkedIn - [email protected]

You can talk to me in πŸ‡«πŸ‡·, πŸ‡§πŸ‡· or πŸ‡¬πŸ‡§.


All versions of partez with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
twig/twig Version ^3.8
twig/html-extra Version ^3.8
twig/intl-extra Version ^3.8
vlucas/phpdotenv Version ^5.6
abollinger/helpers Version ^1.2
abollinger/bricolo Version ^1.6
abollinger/session Version ^1.1
abollinger/router Version ^1.0
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 abollinger/partez contains the following files

Loading the files please wait ....