Skip to main content

Acquia BLT setup With Lando

 Install the latest version of Lando.

navigate to directory & create a project directory.

1 - mkdir lando-d8 & cd lando-d8

2 - lando init (choose anything later we will change the config)

One lando.yml file will be create in the directory change the config as below,


name: lando-lightning
recipe: drupal8
config:
  webroot: lightning/docroot

tooling:
  blt:
    service: appserver
    cmd: /usr/bin/blt

Can change the name,

lando start


lando composer create-project --no-interaction acquia/blt-project lightning

cd lightning

Follow the Document : 
https://thinktandem.io/blog/2017/12/09/lando-blt-acquia/
After the drupal install & can login in drupal:

Now the Basic Processudre is to deployment in git & acquia,

Before you can either connect to your Git code repository or use SSH to sign in to your web server, you must have an SSH private/public key pairGenerate keys in system by following URL:
https://docs.acquia.com/cloud-platform/manage/ssh/generate/

If you use Git, you may want to host your Git repository at GitHub or on Bitbucket to take advantage of their excellent Git support, pull requests with integrated code review, and use other features. The following methods are available to keep your application’s code in GitHub or Bitbucket while still hosting it on Cloud Platform:

Manually creating two remotes for your local repository clone: one at GitHub or Bitbucket, and one at Cloud Platform.
1 - github.com repository, And commit all changes to this repository.

Repository architecture With BLT:

Consequently, there are some aspects of a project’s architecture and workflow that may be unfamiliar to you:

  • Drupal core, contributed (contrib) modules, themes, and third-party libraries are not committed to the repository. Contrib module directories that are ignored with .gitignore are populated during build artifact generation.
  • The repository is never pushed directly to the cloud. Instead, changes to the repository on GitHub trigger tests to be run using Continuous integration. Changes that pass testing will cause a build artifact to be created and then deployed to the cloud.
  • Common project tasks are executed using a build tool (such as Robo) allowing them to execute exactly the same in all circumstances.

Current Running BLT setup in Local:
/var/www/html/lando/lando-acquia

Comments

Post a Comment

Popular posts from this blog

How to span column of custom table in Drupal

If you want to span the column of custom drupal table like below image, Follow the below code to make the header of the table , <?php $header = array('S.N','District', array('data' => '<div class ="house">Household </div><br><span>Rural</span> <p>Urban</p>','colspan' => 2), array('data' => '<div class ="house">Members</div> <br><span>Rural</span> <p>Urban</p>','colspan' => 2), 'Duplicate/Failed Registration', array('data' => '<div class ="house">Pending De duplication </div><br><span>Rural</span> <p>Urban</p>','colspan' => 2), 'Non Un-organised Workers', 'SSID Generated', 'No. of Card Personlised', ); $rows[] = arra...
1 comment
Read more

Drupal 8 : Link actions,Link menus,Link Tasks,Routings

Drupal 8 : Link actions,Link menus,Link Tasks,Routings Link actions Local actions have also been moved out of the hook_menu() system in Drupal 8 .Use actions to define local operations such as adding new items to an administrative list (menus, contact categories, etc). Local actions are defined in a YAML format, named after the module they are defined by. Such as menu_ui.links.action.yml for this example from menu_ui module: menu_ui.link_add:   route_name: menu_ui.link_add   title: 'Add link'   appears_on:     - menu_ui.menu_edit Here, menu_ui.link_add: It is the Unique name of the link action Most likely start with module name, route_name : Name of the route it means when click the link it redirect to this route, appears_on :  An array of route names for this action to be display on. Now how to know the Route name of any internal/external admin pages like below, By through the drupal console we achieve it, drupal debug:router...
Post a Comment
Read more

Cache In Drupal

Drupal 8 core caching modules: The Internal Page Cache module: this caches pages for anonymous users in the database. Pages requested by anonymous users are stored the first time they are requested and then are reused for future visitors. The Internal Dynamic Page Cache module: This is a key feature that Drupal 7 did not have. Unlike the Internal Page module, the Dynamic Page module aims to speed up the site for both anonymous and logged-in users. How Cache Works in Drupal: There are two modules available in the drupal core 1 - Internal page cache: The Internal Page Cache module caches pages for anonymous users in the database. Pages requested by anonymous users are stored the first time they are requested and then are reused. Configuring the internal page cache :   From the performance page we can set the maximum time how long browsers and proxies may cache pages based on the Cache-Control header. 2 - Internal dynamic page cache: Drupal 8 provides the Dynamic Page Cache m...
Post a Comment
Read more