Larasoft's SOPs
  • Larasoft's Transparent SOPs
  • Laravel SOPs
    • Getting Started
    • How to read this guide
    • Environment
    • Configuration
    • Naming Conventions
    • Database Conventions
    • Design Patterns
    • Testing
    • Frontend Development
    • Resources and Links
  • Internal SOPs
    • Internal SOPs
Powered by GitBook
On this page

Was this helpful?

  1. Laravel SOPs

Getting Started

Laravel Specific Standard Operating Procedures that keep us true to the Community Standards

PreviousLarasoft's Transparent SOPsNextHow to read this guide

Last updated 4 years ago

Was this helpful?

The Ecosystem

At the very minimum, you need to know how to use and . Though not required, it is better that you have an account on as it is where all the code and its dependencies are hosted.

You MUST be comfortable in using , specially Unix Shells (sh, ksh, csh, tcsh, bash etc) as it is heavily used for common tasks in working with Laravel.

For local development, you’ll need to have at least and installed. This is used by (a special vagrant box made for running Laravel apps). Although you can use the traditional WAMP/MAMP/XAMPP stack, those are not officially supported, thus you might have hard time down the road.

Pure “Laravel-way” frontend development might be a daunting one as it got has a long chain of technologies. You can either use which is server-side templating or do client-side (browser), which at the very top of the chain is , a wrapper for . Webpack has its dependencies managed through , all of which are packages of .

CSS is managed either through or , while JavaScript can be done through Plain JavaScript, and the more common frontend framework used with Laravel: .

For the backend stack, at the very least, you need a web server like , a php interpreter like and a database like . Other optional stack components are , and .

While you are not required to understand them all at once, it is advantagous that you are at least familiar with these and do some reading about what they are and where they are being used. This will save you tons of confusion when reading the documentation and references in the future.

Git
Composer
GitHub.com
Command Line Interface (CLI)
Vagrant
VirtualBox
Homestead
Laravel Blade
Mix
Webpack
npm
NodeJS
Sass
LESS
ReactJS
VueJS
Nginx
PHP-FPM
MySQL
Memcached
Redis
Beanstalkd