A skeleton application using the Zend Framework MVC

Overview

ZendSkeletonApplication

Repository abandoned 2019-12-31

This repository has moved to laminas/laminas-skeleton-installer.

Introduction

This is a skeleton application using the Zend Framework MVC layer and module systems. This application is meant to be used as a starting place for those looking to get their feet wet with Zend Framework.

Installation using Composer

The easiest way to create a new Zend Framework project is to use Composer. If you don't have it already installed, then please install as per the documentation.

To create your new Zend Framework project:

$ composer create-project -sdev zendframework/skeleton-application path/to/install

Once installed, you can test it out immediately using PHP's built-in web server:

$ cd path/to/install
$ php -S 0.0.0.0:8080 -t public
# OR use the composer alias:
$ composer run --timeout 0 serve

This will start the cli-server on port 8080, and bind it to all network interfaces. You can then visit the site at http://localhost:8080/

  • which will bring up Zend Framework welcome page.

Note: The built-in CLI server is for development only.

Development mode

The skeleton ships with zf-development-mode by default, and provides three aliases for consuming the script it ships with:

$ composer development-enable  # enable development mode
$ composer development-disable # disable development mode
$ composer development-status  # whether or not development mode is enabled

You may provide development-only modules and bootstrap-level configuration in config/development.config.php.dist, and development-only application configuration in config/autoload/development.local.php.dist. Enabling development mode will copy these files to versions removing the .dist suffix, while disabling development mode will remove those copies.

Development mode is automatically enabled as part of the skeleton installation process. After making changes to one of the above-mentioned .dist configuration files you will either need to disable then enable development mode for the changes to take effect, or manually make matching updates to the .dist-less copies of those files.

Running Unit Tests

To run the supplied skeleton unit tests, you need to do one of the following:

  • During initial project creation, select to install the MVC testing support.

  • After initial project creation, install zend-test:

    $ composer require --dev zendframework/zend-test

Once testing support is present, you can run the tests using:

$ ./vendor/bin/phpunit

If you need to make local modifications for the PHPUnit test setup, copy phpunit.xml.dist to phpunit.xml and edit the new file; the latter has precedence over the former when running tests, and is ignored by version control. (If you want to make the modifications permanent, edit the phpunit.xml.dist file.)

Using Vagrant

This skeleton includes a Vagrantfile based on ubuntu 16.04 (bento box) with configured Apache2 and PHP 7.0. Start it up using:

$ vagrant up

Once built, you can also run composer within the box. For example, the following will install dependencies:

$ vagrant ssh -c 'composer install'

While this will update them:

$ vagrant ssh -c 'composer update'

While running, Vagrant maps your host port 8080 to port 80 on the virtual machine; you can visit the site at http://localhost:8080/

Vagrant and VirtualBox

The vagrant image is based on ubuntu/xenial64. If you are using VirtualBox as a provider, you will need:

  • Vagrant 1.8.5 or later
  • VirtualBox 5.0.26 or later

For vagrant documentation, please refer to vagrantup.com

Using docker-compose

This skeleton provides a docker-compose.yml for use with docker-compose; it uses the Dockerfile provided as its base. Build and start the image using:

$ docker-compose up -d --build

At this point, you can visit http://localhost:8080 to see the site running.

You can also run composer from the image. The container environment is named "zf", so you will pass that value to docker-compose run:

$ docker-compose run zf composer install

Web server setup

Apache setup

To setup apache, setup a virtual host to point to the public/ directory of the project and you should be ready to go! It should look something like below:

<VirtualHost *:80>
    ServerName zfapp.localhost
    DocumentRoot /path/to/zfapp/public
    <Directory /path/to/zfapp/public>
        DirectoryIndex index.php
        AllowOverride All
        Order allow,deny
        Allow from all
        <IfModule mod_authz_core.c>
        Require all granted
        IfModule>
    Directory>
VirtualHost>

Nginx setup

To setup nginx, open your /path/to/nginx/nginx.conf and add an include directive below into http block if it does not already exist:

http {
    # ...
    include sites-enabled/*.conf;
}

Create a virtual host configuration file for your project under /path/to/nginx/sites-enabled/zfapp.localhost.conf it should look something like below:

server {
    listen       80;
    server_name  zfapp.localhost;
    root         /path/to/zfapp/public;

    location / {
        index index.php;
        try_files $uri $uri/ @php;
    }

    location @php {
        # Pass the PHP requests to FastCGI server (php-fpm) on 127.0.0.1:9000
        fastcgi_pass   127.0.0.1:9000;
        fastcgi_param  SCRIPT_FILENAME /path/to/zfapp/public/index.php;
        include fastcgi_params;
    }
}

Restart the nginx, now you should be ready to go!

QA Tools

The skeleton does not come with any QA tooling by default, but does ship with configuration for each of:

Additionally, it comes with some basic tests for the shipped Application\Controller\IndexController.

If you want to add these QA tools, execute the following:

$ composer require --dev phpunit/phpunit squizlabs/php_codesniffer zendframework/zend-test

We provide aliases for each of these tools in the Composer configuration:

# Run CS checks:
$ composer cs-check
# Fix CS errors:
$ composer cs-fix
# Run PHPUnit tests:
$ composer test
Comments
  • Prepare for zend-mvc v3

    Prepare for zend-mvc v3

    For the v3 release, we will be pulling in a smaller set of components out-of-the-box. These are primarily defined by zend-mvc, but also include:

    • ~~zend-config (used by the zend-modulemanager ConfigListener by default)~~ (zend-modulemanager now defines the zend-config requirement)
    • zend-skeleton-installer for prompting for optional packages/capabilities.
    • zend-component-installer, to automate registration of components as modules.

    Additionally, we plan to leverage Composer for all autoloading, which means:

    • we can register a PSR-4 entry for the Application module, and remove one directory level;
    • the Application module no longer needs to setup autoloading.

    For a minimal application, we do not want or need internationalization. As such, this patch also removes all translations and calls to translate strings in templates. We can explore re-adding them later, or offering an alternative skeleton application with more default features (including i18n, forms, databases, etc.).

    At the time of submission, this patch provides a working skeleton with the current zend-mvc develop branch.

    Testing

    If you wish to test:

    • Clone the repository locally
    • Enter the cloned repository
    • Switch to the develop branch: git checkout -b develop origin/develop
    • Apply the changes: wget https://patch-diff.githubusercontent.com/raw/zendframework/ZendSkeletonApplication/pull/329.patch && git am 329.patch (or, if you use the hub command: git merge https://github.com/zendframework/ZendSkeletonApplication/pull/329)
    • Execute composer install

    If you want to use vagrant:

    • Start it: vagrant up
    • Run composer within it: vagrant ssh -c 'cd /var/www ; composer install'
    • Start testing

    If you want to use docker:

    • Build and run it: docker-compose up -d --build
    • Run composer within it: docker-compose run zf composer install
    • Start testing.

    Please report any issues you notice or provide constructive feedback via comments to this pull request, or issue a pull request against my branch.

    TODO

    Installer

    • [x] Prompt for caching
      • will install zend-cache
    • [x] Prompt for console
      • prompt should indicate users should migrate to zf-console
      • will install zend-mvc-console
    • [x] Prompt for database
      • will install zend-db
    • [x] Prompt for forms
      • will install zend-form
    • [x] Prompt for i18n
      • will install zend-mvc-i18n
    • [x] Prompt for JSON
      • will install zend-json
    • [x] Prompt for logging
      • will install zend-log
    • [x] Prompt for PSR-7 middleware dispatcher
      • will install zend-psr7bridge
    • [x] Prompt for sessions
      • will install zend-session
    • [x] Prompt for testing facilities
      • will install zend-test as dev requirement
    • [x] Prompt for plugins
      • will install zend-mvc-plugin-*
    • [x] Prompt for zend-di integration
      • will install zend-servicemanager-di

    In each case, this should register the module(s) with the application, so that the user does not need to be prompted twice.

    Documentation

    • ModuleRouteListener is removed from the skeleton. This won't affect existing users, but will affect experienced users who originally relied on it being active in new skeleton projects.
    • The /[:controller][/:action]] route was removed from the skeleton. Again, it will not affect existing users, but will affect experienced users who originally relied on it being active in new skeleton projects.

    These items have been added to the maintainers wiki.

    Updates

    • 2016-05-17: added TODO list tracking installer and documentation tasks remaining.

    Close #293

    opened by weierophinney 32
  • Documentation not complete

    Documentation not complete

    Hi Guys I am very angry with you, because I love this framework but there is no way , no examples, no documentation one can start to use it properly, making developers loose a lot of time in search and docs.

    Please add documentation, examples, refactor the community.... do not make devs switch to Lavarel..

    opened by albanx 27
  • Wrong order of config/autoload

    Wrong order of config/autoload

    Configuration must load in that order:

    • global.php
    • *.global.php
    • local.php
    • *.local.php

    But in fact, it is not. I am create gist, to prove it https://gist.github.com/ftdebugger/5934533. Here the result:

    Array
    (
        [0] => config/autoload/global.php
        [1] => config/autoload/local.php
        [2] => config/autoload/some.global.php
        [3] => config/autoload/some.local.php
    )
    

    Loading configuration in two steps guaranteed needed order

    opened by ftdebugger 20
  • Deprecation warnings while installing Zend framework skeleton app 3.1.0

    Deprecation warnings while installing Zend framework skeleton app 3.1.0

    Hello , I was trying to install Zend framework skeleton application (version 3.1.0) , downloaded from here https://github.com/zendframework/ZendSkeletonApplication/releases/. However when i try to install it via composer i.e( php composer.phar install) i get the following deprecation warnings :

    • Installing zendframework/zend-component-installer (0.3.0) Loading from cache Deprecation Notice: The callback Zend\ComponentInstaller\ComponentInstaller::onPostPackageInstall declared at {PATH}/{TO}vendor/zendframework/zend-component-installer/src/ComponentInstaller.php accepts a Composer\Script\PackageEvent but post-package-install events use a Composer\Installer\PackageEvent instance. Please adjust your type hint accordingly, see https://getcomposer.org/doc/articles/scripts.md#event-classes in phar://{PATH}/{TO}composer.phar/src/Composer/EventDispatcher/EventDispatcher.php:317
    • Installing zendframework/zend-stdlib (3.0.1) Loading from cache Deprecation Notice: The callback Zend\ComponentInstaller\ComponentInstaller::onPostPackageInstall declared at {PATH}/{TO}vendor/zendframework/zend-component-installer/src/ComponentInstaller.php accepts a Composer\Script\PackageEvent but post-package-install events use a Composer\Installer\PackageEvent instance. Please adjust your type hint accordingly, see https://getcomposer.org/doc/articles/scripts.md#event-classes in phar://{PATH}/{TO}composer.phar/src/Composer/EventDispatcher/EventDispatcher.php:317.

    What could be the issue?.For your kind information i am using php 5.6.Are these warnings critical ?

    opened by prbt2016 19
  • Composer changes

    Composer changes

    Add composer.lock and remove composer.phar per this discussion: https://github.com/zfcampus/zf-apigility-skeleton/pull/92#issuecomment-109941631 (Moving the Vagrant addition to its own PR)

    opened by jeremiahsmall 19
  • Local configuration of `modules` and `module_listener` ignored.

    Local configuration of `modules` and `module_listener` ignored.

    The following comment block suggests we can use local configuration that would change the behavior of module_listener, but that is not the case. Trying to enable or disable config_cache_enabled will not work.

    /**
     * Local Configuration Override
     *
     * This configuration override file is for overriding environment-specific and
     * security-sensitive configuration information. Copy this file without the
     * .dist extension at the end and populate values as needed.
     *
     * @NOTE: This file is ignored from Git by default with the .gitignore included
     * in ZendSkeletonApplication. This is a good practice, as it prevents sensitive
     * credentials from accidentally being committed into version control.
     */
    
    return array(
        // Whether or not to enable a configuration cache.
        // If enabled, the merged configuration will be cached and used in
        // subsequent requests.
        //'config_cache_enabled' => false,
        // The key used to create the configuration cache file name.
        //'config_cache_key' => 'module_config_cache',
        // The path in which to cache merged configuration.
        //'cache_dir' =>  './data/cache',
        // ...
    );
    

    It's also impossible to add or remove modules using local (i.e. development) config files.

    For example

    // config/autoload/enable.zdt.local.php
    return array(
        'modules' => array(
            'ZendDeveloperTools',
        )
    );
    

    This will not work as expected - it will not add ZDT module to the application (even though the file is merged by globbing and array merger operation would result in the item added onto the original modules array).

    opened by Thinkscape 16
  • Remove composer.phar

    Remove composer.phar

    Please do not distribute composer.phar along with the app, because that means people don't run system checks and then we get support requests for stuff that would have been avoided if they ran the installer from http://getcomposer.org/download/ /cc @SpiffyJr

    opened by Seldaek 16
  • remove ZF2 submodule

    remove ZF2 submodule

    Zend Framework is being installed both by Composer and git submodule. It makes confusion with two ZF's (/vendor/ZF2 and /vendor/zendframework).

    As Composer is recommended way to deploy skeleton, let's remove the submodule.

    Even if developer does not run Composer to install skeleton, he may want to install another libraries with it. Those libaries (e.g. Doctrine) are dependant on zendframework/zendframework package, so it will result in two ZF's anyways.

    opened by ghost 14
  • Compatibility issues with php 7.3?

    Compatibility issues with php 7.3?

    The MVC skeleton-application is generating the following warning and notices after installation:

    Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /var/www/html/test_app/vendor/zendframework/zend-stdlib/src/ArrayObject.php on line 428
    
    Notice: compact(): Undefined variable: extras in /var/www/html/test_app/vendor/zendframework/zend-view/src/Helper/HeadLink.php on line 404
    
    Notice: compact(): Undefined variable: extras in /var/www/html/test_app/vendor/zendframework/zend-view/src/Helper/HeadLink.php on line 404
    
    Notice: compact(): Undefined variable: extras in /var/www/html/test_app/vendor/zendframework/zend-view/src/Helper/HeadLink.php on line 404
    

    Happens both with and without -s dev.

    Not sure if it's related, but I saw a tweet from the devel account about the release of zend-component-installer 2.1.2, which supports php 7.3, while the skeleton-applicaton installs the version 0.7.0 of the same component.

    I even tried clearing composer's cache and running it again. Same results.

    opened by galvao 13
  • Improvements and fixes

    Improvements and fixes

    • fix image alt to use version from Application\Module instead of fixed 2 version
    • changes short echo notation to normal echo (consistency with all other places in skeleton)
    • updated bootstrap to latest version 3.3.6
    • removed redundant/outdated JS assets

    suggestion: maybe will be better to use CSS from cdn server instead including it into project?

    enhancement 
    opened by michalbundyra 13
  • zf2 package for skeleton-application

    zf2 package for skeleton-application

    hi!

    I noticed that there is no 2.4.x package for the skeleton-application (https://github.com/zendframework/ZendSkeletonApplication) on https://packages.zendframework.com/

    Is this planned in the near future?

    Thanks in advance

    opened by DonCarlosGraz 12
  • getting error with new while enable cache

    getting error with new while enable cache

    Fatal error: Uncaught TypeError: Argument 1 passed to Zend\ModuleManager\Listener\ConfigListener::setMergedConfig() must be of the type array, integer given, called in /var/www/html/hello/vendor/zendframework/zend-modulemanager/src/Listener/ConfigListener.php on line 70 and defined in /var/www/html/hello/vendor/zendframework/zend-modulemanager/src/Listener/ConfigListener.php on line 208

    TypeError: Argument 1 passed to Zend\ModuleManager\Listener\ConfigListener::setMergedConfig() must be of the type array, integer given, called in /var/www/html/hello/vendor/zendframework/zend-modulemanager/src/Listener/ConfigListener.php on line 70 in /var/www/html/hello/vendor/zendframework/zend-modulemanager/src/Listener/ConfigListener.php on line 208

    For time temporarily i had disable cache from application.config.php by comment these line // Whether or not to enable a configuration cache. // If enabled, the merged configuration will be cached and used in // subsequent requests. // 'config_cache_enabled' => true,

    // The key used to create the configuration cache file name.
    //'config_cache_key' => 'application.config.cache',
    
    // Whether or not to enable a module class map cache.
    

    // 'module_map_cache_enabled' => true,

    // The key used to create the class map cache file name.
    //'module_map_cache_key' => 'application.module.cache',
    
    // The path in which to cache merged configuration.
    

    // 'cache_dir' => 'data/cache/',

    // 'check_dependencies' => true, After disable my error omitted, If i want to use cache , than what is solution ???

    Write

    My composer.json

    { "name": "zendframework/skeleton-application", "description": "Skeleton Application for Zend Framework zend-mvc applications", "type": "project", "license": "BSD-3-Clause", "keywords": [ "framework", "mvc", "zf" ], "homepage": "http://framework.zend.com/", "minimum-stability": "dev", "prefer-stable": true, "require": { "php": "^5.6 || ^7.0", "zendframework/zend-component-installer": "^1.0 || ^0.7 || ^1.0.0-dev@dev", "zendframework/zend-mvc": "^3.0.1", "zfcampus/zf-development-mode": "^3.0", "zendframework/zend-cache": "^2.7.1", "zendframework/zend-db": "^2.8.1", "zendframework/zend-mvc-form": "^1.0", "zendframework/zend-json": "^3.0", "zendframework/zend-log": "^2.9", "zendframework/zend-mvc-console": "^1.1.10", "zendframework/zend-mvc-i18n": "^1.0", "zendframework/zend-mvc-plugins": "^1.0.1", "zendframework/zend-psr7bridge": "^0.2.2", "zendframework/zend-session": "^2.7.1", "zendframework/zend-servicemanager-di": "^1.0", "monolog/monolog": "^1.23", "doctrine/orm": "^2.5", "doctrine/doctrine-orm-module": "^1.1" }, "autoload": { "psr-4": { "Application\": "module/Application/src/" } }, "autoload-dev": { "psr-4": { "ApplicationTest\": "module/Application/test/" } }, "extra": [], "scripts": { "cs-check": "phpcs", "cs-fix": "phpcbf", "development-disable": "zf-development-mode disable", "development-enable": "zf-development-mode enable", "development-status": "zf-development-mode status", "post-create-project-cmd": [ "@development-enable" ], "serve": "php -S 0.0.0.0:8080 -t public public/index.php", "test": "phpunit" }, "require-dev": { "zendframework/zend-developer-tools": "^1.1.0", "zendframework/zend-test": "^3.0.1" } }

    opened by vishalmati-sharma 1
  • Installer option wording

    Installer option wording

    When running through the installer options, sometimes it's not self-evident why I may want to choose or not choose a particular option. I think this boils down, essentially, to documentation more than actually altering the wording of the prompts in the installer. Perhaps a link to an official installer doc could be displayed by the installer at the start.

    In any case, the prompt that seems the most ambiguous is the mvc-console one

    Would you like to install MVC-based console support? (We recommend migrating to zf-console, symfony/console, or Aura.CLI)
    

    Here we get a y/N option for a module which seems like is not recommended. Perhaps the other options could be offered too in the same prompt. For example:

      Would you like to install console support?
      [0] No console
      [1] MVC-based console
      [2] zf-console
      [3] symfony/console
      [4] Aura.CLI
      Make your selection (default is 0):
    

    See https://gist.github.com/jeremiahsmall/d5c54f283dddf2f4ba3e11d0cd39fa11#file-zendframework_skeleton_installer_output-txt-L30

    enhancement awaiting author updates 
    opened by jeremiahsmall 2
Releases(release-3.1.3)
  • release-3.1.3(Nov 27, 2019)

    Added

    • Nothing.

    Changed

    • Nothing.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #452 provides a truly cross-platform approach to removing the composer.lock entry from the .gitignore file. The skeleton now provides a script for doing so that it invokes as part of its post-create-project-cmd event; the script removes itself on completion.
    Source code(tar.gz)
    Source code(zip)
  • release-3.1.2(Nov 21, 2019)

    Added

    • Nothing.

    Changed

    • Nothing.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #451 provides compatibility on Windows for the script re-instating the composer.lock in the created project.
    Source code(tar.gz)
    Source code(zip)
  • release-3.1.1(Nov 15, 2019)

  • release-3.1.0(Nov 15, 2019)

    Added

    • Nothing.

    Changed

    • #431 updates the skeleton to use Bootstrap 4.

    • #428 changes the default module_listener_options in the config/application.config.php file to remove the module_paths and set use_zend_loader to false.

    • #448 removes the composer.lock to ensure users creating a new project receive the latest versions of all dependencies as supported by their current PHP version. Additionally, it adds an entry to the post-create-project-cmd Composer hook to remove the composer.lock entry from the .gitignore file, to promote checking in a composer.lock in user projects.

    • #448 bumps the version constraints of all optional packages to the latest versions supported by all PHP versions the skeleton supports.

    • #448 bumps the minimum supported version of zf-development-mode to 3.2

    • #448 bumps the minimum supported version of zend-mvc to 3.1.1.

    • #448 bumps the allowed versions of zend-component-installer to the 1.0 and 2.0 series.

    • #448 bumps the minimum supported version of zend-skeleton-installer to 0.1.7.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #430 updates the serve command to work cross-platform, and across all supported PHP versions.
    Source code(tar.gz)
    Source code(zip)
  • release-3.0.3(Oct 31, 2017)

    Added

    • Nothing.

    Changed

    • #386 updates the Vagrant box to be based on bento/ubuntu-16.04.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #395 fixes an issue with environment expansion when creating the default vhost in the Vagrant box.

    • #406 updates the composer serve script to work on Windows.

    Source code(tar.gz)
    Source code(zip)
  • release-3.0.2(Mar 11, 2017)

  • release-2.4.11(Jan 4, 2017)

  • release-3.0.1(Aug 16, 2016)

    Added

    • #375 adds support for Ubuntu 16.04 in the shipped vagrant configuration.
    • #377 adds composer scripts for running CS checks and unit tests.
    • #380 adds the file public/web.config file for usage with IIS, with rules matching those in public/.htaccess.

    Deprecated

    • Nothing.

    Removed

    • Nothing.

    Fixed

    • #376 updates the shipped Bootstrap version to 3.3.7.
    • #376 updates the shipped jQuery version to 3.1.0.
    • #381 updates the skeleton to enable development mode on initial project installation, via a Composer hook.
    Source code(tar.gz)
    Source code(zip)
  • release-3.0.0(Jun 28, 2016)

    This release updates the skeleton application to zend-mvc v3.0, with the following additional changes:

    • No more dependency on the zendframework package; instead, it only defines dependencies on the minimum set of components needed to execute a zend-mvc application.
    • Adds dependencies on zend-component-installer and zend-skeleton-installer; the latter prompts for additional packages to install, and the former auto-registers them with the MVC.
    • Adds a dependency on zf-development-mode, allowing users to toggle development mode settings.
    • Adds unit testing scaffolding for the application.
    • Adds docker-compose and vagrant configuration, to provide workable, default development environments out-of-the-box.
    Source code(tar.gz)
    Source code(zip)
Owner
Zend Framework
Zend Framework
Slim Framework 4 Skeleton Application

Slim Framework 4 Skeleton Application Use this skeleton application to quickly setup and start working on a new Slim Framework 4 application. This app

Cleonildo Soares Guimaraes Junior 5 Nov 21, 2021
This repository is pre-configured, clean and empty skeleton for creating a new projects using Kraken Framework.

Kraken Application Skeleton Note: This repository contains pre-configured application skeleton for fast creation of new projects with Kraken Framework

Kraken 79 Aug 6, 2022
CodeIgniter 4-based application skeleton

Bonfire 2 Just getting started. More details at Patreon What is Bonfire? Bonfire will be a robust application skeleton for CodeIgniter 4-based applica

Lonnie Ezell 79 Dec 25, 2022
This is a skeleton to quickly set up a new Slim 4 application.

Slim 4 Skeleton This is a skeleton to quickly set up a new Slim 4 application. Requirements PHP 7.4+ or 8.0+ MySQL 5.7+ or MariaDB Recommended Apache

Daniel Opitz 376 Jan 2, 2023
Reverse proxy skeleton built for docker with traefik, showcasing a Symfony + React application

Decoupled Backend(Symfony) + Frontend(React ts) built with Traefik & Docker Reverse proxy skeleton built for docker with traefik, showcasing a decoupl

Sergiu 1 Dec 13, 2021
Simple skeleton for the PHP Slim framework

Simple skeleton for the PHP Slim framework

Andrew S Erwin 2 Nov 13, 2021
SPA Skeleton with Mithril.js and Slim Framework

A single-page application (SPA) skeleton based on Mithril.js and Slim Framework 4 trying to use good practices

tebe 5 Oct 23, 2022
A skeleton for creating applications with CakePHP 4.x.

CakePHP Application Skeleton A skeleton for creating applications with CakePHP 4.x. The framework source code can be found here: cakephp/cakephp. Inst

Fabiano Araujo 1 Oct 13, 2021
A skeleton for build your Kata with Docker

A skeleton for build your Kata with Docker

Raúl Coloma Bonifacio 1 Nov 12, 2021
Project skeleton generator for Laravel & Lumen projects

Skeletor Skeletor is a PHP based CLI tool that has been built to take away the pain of setting up a base project skeleton for Laravel & Lumen projects

Wouter 39 Oct 4, 2022
A skeleton WordPress project to be used as a base for new WordPress projects.

BoxUK WordPress Project Skeleton A base WordPress project from Box UK to get you up and running quickly. Installation Create a new project with compos

Box UK 33 Dec 14, 2022
⚡️ This package provides a wonderful PHP skeleton to start building your next package idea.

This package provides a wonderful PHP Skeleton to start building your next package idea. Requires PHP 8.0+ ⚡️ Create your package using Composer: comp

Nuno Maduro 383 Dec 20, 2022
This is Slim 3 API skeleton project for Composer

Slim 3 API skeleton This is Slim 3 API skeleton project for Composer. Project uses Zend Table Gateway and Phinx for database operations, Monolog for l

Mika Tuupola 304 Dec 28, 2022
👔 Enterprise Web application starter kit or template using Laravel

Laravel Enterprise Starter Kit (LESK) Description LESK, is a template project based on the Laravel LTS, combining a set of features that can kick star

Sebastien Routier 1 Dec 31, 2020
Laravel Framework 5 Bootstrap 3 Starter Site is a basic application with news, photo and video galeries.

Laravel Framework 5.1 Bootstrap 3 Starter Site Starter Site based on on Laravel 5.1 and Boostrap 3 Features Requirements How to install Application St

null 900 Dec 22, 2022
A simple starter kit for using TypedCMS with the Laravel framework.

TypedCMS Starter Kit for Laravel Our stater kits are tailored solutions for each platform, unlike the simple API wrappers offered by other vendors. Th

TypedCMS 1 Nov 20, 2021
⬆️ ⬇️ User vote system for Laravel Application.

Laravel Vote ⬆️ ⬇️ User vote system for Laravel Application. Installing $ composer require overtrue/laravel-vote -vvv Configuration This step is optio

安正超 79 Dec 21, 2022
Syntax-aware proofreading for your Laravel application.

Laravel Prose Linter Syntax-aware proofreading for your Laravel application. The Laravel Prose Linter helps you to polish the texts of your Laravel ap

Beyond Code 97 Dec 18, 2022
Creating a simple weather web application with Laravel rest API.

Weather Channel Creating a website for weather status, with Laravel restAPI. See the Website Weather.Channel-1.mov Features REST API Invoake Controlle

AmirH.Najafizadeh 3 Jul 31, 2022