Download the PHP package cornell-custom-dev/laravel-starter-kit without Composer

On this page you can find all versions of the php package cornell-custom-dev/laravel-starter-kit. 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?

Example code of cornell-custom-dev/laravel-starter-kit

Informations about the package laravel-starter-kit

Laravel Starter Kit

A Cornell University CIT Custom Development starter kit and library for Laravel.

Goals

Usage

The Starter Kit can be used as a starter kit for a new site or as a library for an existing site.

As a Starter Kit for a New Site

Used as a starter kit, this package deploys the cwd_framework_lite infrastructure and standard configuration files. The steps below get from a fresh Laravel install to a working site.

  1. Follow standard Laravel project creation, namely

    This is done with the --no-dev option, because we will be committing the vendor dir and don't need that extra baggage.

    NOTE: If you have GitHub CLI installed, you can immediately add this to GitHub as a repo with the following commands (be sure to replace the "your-app-name" references with your project info):

  2. Composer require the LaravelStarterKit

    Similar to the create-project option, the --update-no-dev keeps us from adding baggage to the vendor dir.

  3. Install the Starter Kit

    The starterkit:install command prompts for a set of install options:

    • publish configured project files to the base directory and update the composer.json file to match
    • publish HTML/CSS/JS theme assets from cwd_framework_lite
    • publish a set of view components that can be used to begin a layout
    • publish example blade files to see usage of the layout

      NOTE: The "project files" option updates .gitignore so that the vendor directory is no longer excluded. The next commit will be large because it includes everything in the vendor directory.

  4. Testing the site
    You can confirm the site is working with Lando, since the Starter Kit install process adds a .lando.yml file.

    Then visit https://your-app-name.lndo.site and you should see the default Laravel page. To see the Laravel Starter Kit example page, edit /resources/views/welcome.blade.php to be:

As a Library for an Existing Site

For an existing Laravel site, this package can be composer-required to provide the library of classes and optionally install some components.

  1. Composer require the LaravelStarterKit

  2. Install the Starter Kit

    Note: When using as a library or updating an installation, you will not want to install the project files. You may still want to install the theme assets, view components, and possibly example files. Be aware that these will overwrite existing files.

Libraries

The libraries included in the Starter Kit are documented in their respective README files:

Deploying a site

Once a Media3 site has been created, you have confirmed you can reach the default site via a web browser, and you have access to the site login by command line, the code can be deployed.

You will likely need to map the php command to the correct version by editing ~/.bashrc to include this alias (for this to take effect, run source ~/.bashrc or just log in again):

Since www/your-site/public will already exist, you need to do a little moving things around to git clone your site repo from GitHub:

At this point you can configure the www/your-site/.env file:

Be sure to set your APP_* values to appropriate values, based on whether it is production:

If you visit your site now, you should see the Laravel site working.

Contributing

Anyone on the Custom Development team should be welcome and able to contribute. See CONTRIBUTING for details on how be involved and provide quality contributions.

All versions of laravel-starter-kit with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
livewire/livewire Version ^3.3
spatie/laravel-package-tools Version ^1.16
cubear/cwd_framework_lite Version ^3.0
propaganistas/laravel-phone Version ^5.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 cornell-custom-dev/laravel-starter-kit contains the following files

Loading the files please wait ....