This document discusses continuous integration and deployment using Laravel and Azure Web Apps. It defines Laravel as a PHP web framework and Azure Web Apps as a platform for hosting web apps that can scale. It then explains that continuous integration merges code changes frequently, while continuous deployment aims to automate deployments so new changes can be released quickly and safely. When using Azure Web Apps, automated deployments can be set up using third-party services connected to the local Git repository to deploy code to staging slots for testing before promotion to production.
5. Laravel
▶ Laravel is a prominent member of a new
generation of web frameworks. It is a free,
open-source PHP web framework, created by
Taylor Otwell back in 2011 and intended for the
development of web applications following the
MVC model.
6. Features
▶ Modular packaging system with a dedicated dependency
manager
▶ Different ways for accessing relational databases though
Routing
▶ Utilities that aid in application deployment and
maintenance
▶ Orientation toward syntactic sugar
▶ Easy authentication by providing a simple & easy to use
interface and many more.
7. Pros & Cons
Pros
▶ Packages and resource availability
▶ Standardised Development:
▶ Works on PHP 7: YES! It works on PHP7!!
▶ Eloquent Integrations
▶ Product development cycle
▶ Integrations were faster!
▶ Massive community support!
▶ A feeling "Nothing is impossible" while following Laracasts
▶ A great happiness to see team write standardised and artistic
code
▶ Migrations and seeds being managed properly
▶ The tools available like debugbar for Laravel are great asset and
there is a huge community supporting development of vendor
packages for composer and you can use them along with Laravel
easily
Cons
▶ Development process requires you to work with standards and
should have real understanding of programming
▶ Doesn't work for shared hosting
▶ Does query a lot on your databases
▶ You need to know about Blade templating , Gulp, NPM, Bower,
Composer, Eloquent and Laravel. That's a lot for someone who
was developing with Framework like CI2 or any simpler
framework, but I assure you it has benefits!
9. Azure App Service Family
Web Apps
Web apps that scale with
your business
Mobile Apps
Build mobile apps for any
device
Logic Apps
Automate business
processes across SaaS and
on-premises
API Apps
Build and consume APIs in
the cloud
10. Azure Web Apps
•Support a variety of languages and platforms
• .NET, Java, Node.js, PHP, Python, and more
•Support scaling (manual or auto) and load balancing
•Support slots for staged deployments and A/B testing
•Support continuous integration
Global Scale
Scale up and down as
needed, manually or
automatically
Enterprise Grade
ISO-, SOC2-, and
PCO-compliant with
enterprise-level SLAs
Familiar and Fast
Leverage existing skills, plus
languages, frameworks, and
tools you're familiar with
13. CI / CD ?
▶ Continuous integration focuses on blending the work products of individual
developers together into a repository. Often, this is done several times each
day, and the primary purpose is to enable early detection of integration bugs,
which should eventually result in tighter cohesion and more development
collaboration. The aim of continuous delivery is to minimize the friction
points that are inherent in the deployment or release processes. Typically,
the implementation involves automating each of the steps for build
deployments such that a safe code release can be done—ideally—at any
moment in time. Continuous deployment is a higher degree of automation,
in which a build/deployment occurs automatically whenever a major change
is made to the code.
14. In Web Apps
•Web apps can be deployed manually via FTP or WebDeploy
•Automate deployment using 3rd
party source-control providers
•Can also use a local Git repository from Azure Portal
DropBo
x
BitBucke
t
GitHu
b
CodePle
x
Visual Studio
Team
Services
Gi
t
