Pre-requisites

• You have done everything I said in the paragraph above.

Steps to enable SSL in your lightsail hosted website

1. Signup a free account at Cloudflare.com, if you have no prior accounts there.
2. Login at Cloudflare.
3. Add a site into your Cloudflare dashboard and enter the site name: example.com
4. Free Plan is the plan you’d select, and click Get started. The free plan option can be anywhere in the Select a plan page. So, please be curious enough to find it.
   • Then, Cloudflare would perform a quick scan to show you current DNS records of your domain. Make a note of the summary, as you will have to come back to re-configure this at a later step.
   • Hit the Continue button.
5. Cloudflare will offer you few steps to change your nameservers. For instance,
   • Determine your registrar via WHOIS
   • Login to Godaddy (in my case it was the registrar)
   • Remove the existing nameservers (i.e., the ones you got from AWS lightsail)
   • Add the Cloudflare provided nameservers.
   • Save your changes and wait (couple of minutes; atmost 24 hours). Check the WHOIS lookup again to see if the nameserver updates are completed or not.
6. Once Cloudflare determines that your domain’s nameservers are updated accordingly, you’ll receive a Status active email, and also see the expected changes in the WHOIS lookup.
7. At the Cloudflare dashboard do the following:
   • DNS pane:
     • Remove existing DNS records.
     • Add record: {type:A, Name:*, IPv4 address:1.2.3.4}
       • This specific A record is to enable domain name mapping for services like ssh, or ping etc.
     • Add record: {type:A, Name:@, IPv4 address:1.2.3.4}
     • Add record: {type:CNAME, Name:www, IPv4 address:1.2.3.4}
   • SSL/TSL pane:
     • At the Overview sub-pane: choose the option Full (strict)
     • At the Origin Servers sub-pane: create a certificate.
       • Choose option Generate private key and CSR with Cloudflare. Select RSA (2048) as the private key type. Make sure the hostnames are selected as: *.example.com, example.com. You have option choose even 15 years as the validity period for the generated SSL certificate. Then, hit the Create button.
       • Copy the content of Origin certificate content into a file named, example.com.pem
       • Copy the content of Private key content into a file named, example.com.key
   • Edge Certificates pane:
     • Configure status of the generated SSL certificate. Don’t worry about the expiry date as it’s going to be auto-renewed every 3 months for 15 years (if you chose that option in the previous step).
     • Always Use HTTPS: Turn this option to ON position.
     • Automatic HTTPS Rewrites: Turn this option to ON position.
   • Overview pane:
     • (Temporarily) turn on the Development mode to disable the caching.
8. At the Lightsail console:
   • Instance > Networking tab: at the IPv4 Firewall section add a new rule for the HTTPS: {Application:HTTPS, Protocol:TCP, Port or range: 443}
   • Copy the example.com.pem and example.com.key files into /etc/ssl/ directory.
   • Assuming example.com.conf is available at the /etc/apache2/sites-available/ directory. If not, make sure the following is configured in the /etc/apache2/sites-available/example.com.conf:

<VirtualHost *:80>
    ServerName example.com
    ServerAlias www.exammple.com
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/example.com
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

• Now, create the example.com-ssl.conf file with SSL configuration:

<VirtualHost *:443>
    ServerName example.com
    ServerAlias www.example.com
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/example.com
    SSLEngine on
    SSLCertificateFile /etc/ssl/example.com.pem
    SSLCertificateKeyFile /etc/ssl/example.com.key
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

• Tell ubuntu system to use it by:
  • sudo a2ensite example.com.conf
  • sudo a2ensite example.com-ssl.conf
  • You may need to remmove the default ones, depending on your use case.
  • sudo a2enmod ssl
  • Reboot the apache2 service: sudo systemctl restart apache2

Testing if the SSL/HTTPS is active for your site

• Open a browser and go example.com
  • It should automatically go to https://example.com, and you’d see the lock icon at the browser’s address bar noting the connection is secure. You can inspect the certificate to review the details.

Possible Hiccups while going through the steps above

• Issue 1: 522 timeout received with the website host not responding.
  • Solution: Either apache2 is not configured properly to serve any https requests, or your lightsail instance’s ipv4 firewall is blocking any 443 port requests which is essential for https.
• Issue 2: website not loaded / recursive forward error.
  • Solution: Please do not add any additional page forwarding rules to switch from http to https as at Cloudflare dashboard we have already configured options like always use https, etc.

Setup

• Make sure you have jupyter and nbconvert installed in your activated python virtual environment. You can install nbconvert by just this command: pip install nbconvert

Converting a notebook into PDF

jupyter nbconvert --to pdf yourNotebook.ipynb

• This generates a PDF via your system’s latex (or more specifically xelatex) command. So, make sure you have these installed in your system otherwise the nbconvert will fail.

Converting a notebook into HTML

jupyter nbconvert --to html yourNotebook.ipynb

• This exports a html version of the jupyter notebook.

Converting a notebook into WebPDF

jupyter nbconvert --to webpdf yourNotebook.ipynb

• This generates a PDF by first rendering to HTMMLM, and rendering the HTML chromium headless, and exporting to PDF. The exporter supports the same template as --to html. The webpdf exporter requires the playwright Chromium automation library, which can be installed via pip install nbconvert[webpdf] command.

Step 1: Create Personal Access Tokens

• You can use a personal access token in place of a password when authenticating to GitHub in the command line or with the API.
• Warning: Treat your access tokens like passwords.
• Go to Settings > Developer Settings > Personal access tokens > click Tokens (classic).
• Select Generate new token, then click Generate new token (classic).
• In the “Note” field, give your token a descriptive name.
• To give your token an expiration, select Expiration, then choose a default option or click Custom to enter a date. You must give expiry date. Warning: do not choose Never.
• Select the scopes you’d like to grant this token. To use your token to access repositories from the command line, select repo. A token with no assigned scopes can only access public information
• Click Generate token.
• Write down (or copy) the generated token as it can’t be seen again in this page.
• That’s it. You now have a personal access token to be used for github authentication through command line.

Step 2: Install Github CLI: gh to use/store authentication tokens

• type -p curl >/dev/null || (sudo apt update && sudo apt install curl -y)
• curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpg
• sudo chmod go+r /usr/share/keyrings/githubcli-archive-keyring.gpg
• echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null
• sudo apt update
• sudo apt install gh
• Check if gh is installed by running gh --version

gh version 2.40.1 (2023-12-13)
https://github.com/cli/cli/releases/tag/v2.40.1

Step 3: login at the command line with the gh tool

• gh auth login

? What account do you want to log into? **GitHub.com**
? What is your preferred protocol for Git operations on this host? **HTTPS**
? Authenticate Git with your GitHub credentials? **Yes**
? How would you like to authenticate GitHub CLI? **Paste an authentication token**
Tip: you can generate a Personal Access Token here https://github.com/settings/tokens
The minimum required scopes are 'repo', 'read:org', 'workflow'.
? Paste your authentication token: ****************************************
- gh config set -h github.com git_protocol https
✓ Configured git protocol
! Authentication credentials saved in plain text
✓ Logged in as `xxx`

Step 4: You are ready

• you can now invoke git commands on your specified repository. It won’t ask for password/access token again (or until the expiry date of the token passes).
• git clone https://github.com/xxx/xyz-mnop-rstuv.git ```

References

• Managing your personal access tokens

Frequently used git commands

List of git commands

Clone a repository

• In your local computer, change current working directory to the directory where you want to clone a github repository. Say, cd _myGITs/
• git clone https://github.com/xxx/my-repo.git
  • The git clone command copies your repository from the Github into your local directory.
• cd my-repo
  • And, inspect ls -a, and you will find .git, .gitignore files besides the repository contents.

Make changes to your repository

• Anything you’d like with editors you have in your local system. You can add/edit/remove files as you go.

Track and add changes to the local git repo

• git status
  • This will display a list of modifications made.
• git add README.md a_file.txt
• This will add one or more files which are listed changes into the staging area
• You may use git add --all, but it is strongly discouraged as you may accidentally add things like credential files. If you really want to do it regardless, move sensitive data out of the repository.
• git commit -m "a message meaningful enough for the people you work with
  • It takes everything from the staging area and makes a permanent snapshot of the current state of the repository that is associated with a unique id.
  • First attemt of git commit command may ask you to set the user.email and user.name values:
    • git config --global user.email "myemail@domain.com"
    • git config --global user.email "my name is xxx"

Push changes to Github (i.e., push to remote)

• So far we have only modified our local (revised) copy of the repository we were working in.
• To add the changes to your remote git repo, you need to git push them to Github.
• You can push your changes to Github with git push
  • You will then be prompted for Github authentication (if not set already with gh auth login, or the stored access token not having correct privileges to make those changes).

Undoing unstaged changes (i.e., prior to calling git add)

• If a file has been changed, but the changes have not yet been staged with git add, then the changes can be undone using git checkout -- myFile.txt
  • This will discard the changes made on the myFile.txt. The command git checkout -- will revert back to the last committed version.
  • Check the status with git status to see if the undoing was successful.

Undoing staged changes (i.e., after changes are added with git add)

• Once you add a set of changes to git using git add, the file is then staged.
• If a file has been changed and then staged via git add, then use git reset to pull the most recently committed version of the file and undo the changes that you’ve made.
  • git reset HEAD myFile.txt
    • This command unstages our changes. The HEAD refers to the most recently committed version of the file myFile.txt. You can also revert to an older version with HEAD-1, HEAD-2, etc.
• When you use git reset, your changes still exist in the file, but the file has been unstaged, that is the changes are not added to git, yet.
  • You can confirm this with git status suggesting you to use git checkout to discard the changes in working directory.
    • git checkout -- myFile.txt

Undoing a commit

• If you have modified, added and committed changes to a file, and want to undo the changes, then you can use git reset HEAD~ to undo your commit.
  • Confirm the status with git status . You’d notice that your file is no longer being tracked.
  • If you inspect the output of git log, you will notice that your previous commit is no longer part of the repo history.
  • Similar to previous example, when you use git reset the modifications will be unstaged. You need to git checkout -- to discard the changes.

Ignore sentitive files

• If you do have sensitive files in a repo directory that you never want to track with git, you can add those file names to a file called .gitignore.

References

• Earth Data Analytics Online Certificate – Lesson 1. Version control intro and setup Intro version control git Workshop

Step 1: Share the folder in Windows 10

• Right click on D:\my_box_folder\, click Properties. Then, on the Sharing tab, click Share button.

Step 2: (Admin only) Access the folder from Ubuntu 22.04 terminal

• Make sure you have the cifs-utils package installed. Or, install it by sudo apt install cifs-utils.
  • Please note: CIFS stands for Common Internet File System. Also note, CIFS is now obsolete. It’s replaced with SAMBA.
• Mount the shared folder into /mnt/cifs-my-box-folder. If the folder is not there, create it.
  • sudo mount -t cifs //10.11.12.13/my_box_folder/ /mnt/cifs-my_box_folder -o username=XXX
    • Here, replace XXX with Windows 10 username. Also, change the IP of the Windows 10 system.
    • It will definitely you ask you for the password for the user XXX
• That’s it. If successful, you can get access to the D:\my_box_folder from your ubuntu system..

References

• How to mount a SMB share in Ubuntu by Howard Young Link

You may wonder why would you want to change the box sync directory location. Okay, that’s a fair question: consider my situation. I have a very limited hard disk budget for a Windows10 operating system’s boot partition, but I have an extensive storage that I want all kinds of data to be stored. Did you get my issue using Box?

Here is a temporary fix (hoping someday Box will add options in their application):

1. Exit the Box application from the system tray.
2. Check if where the box default cache path is. Most likely it is sitting in your C:\Users\XXX\AppData\Local\Box\Box\cache, where replace XXX with your username in your system.
3. You can take a backup of this directory for now, or want to do fresh start of the sync. Simply delete the cache directory.
4. Assuming, you would want D:\my_box_directory\cache to be your new sync path. You need to create this path first.
5. Create a directory synbolic link (in Windows it’s called junction) with this command: mklink /J "C:\Users\XXX\AppData\Local\Box\Box\cache" "D:\my_box_directory\cache"
6. Start the box application.

References

• Box drive change location of cache folder (Windows 10) by Dimitris Moutsatsos at Medium Link

• Download few dependencies (if not present in your system):
  • sudo apt-get install pandoc texlive-latex-base texlive-fonts-recommended texlive-extra-utils texlive-latex-extra
• Now convert using:
  • pandoc my-markdown-file.md -o my-markdown-file.pdf
  • pandoc my-markdown-file.txt -o my-markdown-file.pdf

• You can add your ASCII art /custom text –
  • either in /etc/motd file,
  • or add a script in /etc/update-motd.d/ directory. For instance, 00-header file containing your text.
• You may need to reboot (!)
• It is just a normal text file, but it accepts a good number of escape sequences:

| Escape character | Description | | :- | :- | | \b | Baud rate (the rate at which information is transferred in a communication channel) of the current line | | \d| Current date| | \s | System name, the name of the operating system | | \l | Name of the current tty line | | \m | Architecture identifier of the machine, eg. i486 | | \n | Node name of the machine, also known as the hostname | | \o | Domain name of the machine | | \r | Release number of the OS, eg. 1.1.9 | | \t | Current time | | \u | Number of current users logged in | | \U | The string 1 user or x users where x is the number of current users logged in | | \v | Version of the OS, eg. the build-date etc. |

• You can also add command like banner " gpux4 to create something like this:

                                                        #
                          ####   #####   #    #  #    # #    #
                         #    #  #    #  #    #   #  #  #    #
                         #       #    #  #    #    ##   #######
                         #  ###  #####   #    #    ##        #
                         #    #  #       #    #   #  #       #
                          ####   #        ####   #    #      #

• Finally, this was the content from my server at /etc/update-motd.d/00-header:

echo "##########################################################################"; 
banner "   gpux4   "
echo "##########################################################################"; 

[ -r /etc/lsb-release ] && . /etc/lsb-release

if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
        # Fall back to using the very slow lsb_release utility
        DISTRIB_DESCRIPTION=$(lsb_release -s -d)
fi

printf "Welcome to %s (%s %s %s)\n" "$DISTRIB_DESCRIPTION" "$(uname -o)" "$(uname -r)" "$(uname -m)"

• Removed the following columns:
  • IMU_ATTI(0):Longitude
  • IMU_ATTI(0):Latitude
  • IMU_ATTI(0):distanceHP
  • IMU_ATTI(0):distanceTravelled
  • IMU_ATTI(1):Longitude
  • IMU_ATTI(1):Latitude
  • IMU_ATTI(1):distanceHP
  • IMU_ATTI(1):distanceTravelled
  • eventLog
  • GPS(0):Long
  • GPS(0):Lat
  • IMUEX(0):rtk_Longitude
  • IMUEX(0):rtk_Latitude
  • IMUEX(1):rtk_Longitude
  • IMUEX(1):rtk_Latitude
• I have added a column Operating_Phase :
  • Possible values of this column are {‘Resting’, ‘Taking-Off’, ‘Hovering’, ‘Climbing’, ‘Landing’}
• PDF was generated with pandoc 2.14.2
• Please note: not all signals could be cataloged nor properly described here, but nor should you ignore them for these reasons.
• Alright, the catalog of V3 .CSV columns goes here:

References (as of 9/6/2023)

• DatCon 3.6.1 (7/30/2018) V3 .CSV column format

Prerequisites

• Assuming, you have PHP and VSCode installed in your system.

Setting up Laravel

Setting up Composer

• Get and install composer from https://getcomposer.org/download/ by following the instructions.

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === 'e21205b207c3ff031906575712edab6f13eb0b361f2085f1f1237b7126d785e826a450292b6cfd1d64d92e6563bbde02') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"

• This installer script will simply check some php.ini settings, warn you if they are set incorrectly, and then download the latest composer.phar in the current directory. The 4 lines above will, in order:
  • Download the installer to the current directory
  • Verify the installer SHA-384, which you can also cross-check here
  • Run the installer
  • Remove the installer
• Most likely, you want to put the composer.phar into a directory on your PATH, so you can simply call composer from any directory (Global install), using for example:
  • mkdir /Users/ashis/_Applications
  • mv composer.phar _Applications
  • ln -s /Users/ashis/_Applications/composer.phar /Users/ashis/_Applications/composer
  • vi ~/.zshrc
    • export PATH="/Users/ashis/_Applications/:$PATH"
    • source ~/.zshrc
  • Test if composer command works from the command line.

Setting up Node.js and NPM

• Node.js has installer for all OS at this site https://nodejs.org/en. It also installs npm, a package manager for javascript.
  • Follow the step by running the installer and make a note on the install path. In my case it was installed at:

This package has installed:
	•	Node.js v18.17.1 to /usr/local/bin/node
	•	npm v9.6.7 to /usr/local/bin/npm

• Check the installation of node.js and npm by typing the following:

ashis@Ashiss-MacBook-Pro ~ % node -v
v18.17.1
ashis@Ashiss-MacBook-Pro ~ % npm -v
9.6.7

• Upgrade npm with sudo npm install -g npm@10.0.0
• Also run npm install

Now, install and configure Laravel

• Install Laravel with composer:

ashis@Ashiss-MacBook-Pro ~ % composer global require laravel/installer

• Add the laravel executable in PATH:
  • in MacOS: export PATH="$HOME/.composer/vendor/bin/:$PATH"
  • in Ubuntu: export PATH="$HOME/.config/composer/vendor/bin/:$PATH"
• Check laravel installation with

ashis@Ashiss-MacBook-Pro ~ % laravel   
Laravel Installer 5.1.0

Usage:
  command [options] [arguments]

Options:
  -h, --help            Display help for the given command. When no command is given display help for the list command
  -q, --quiet           Do not output any message
  -V, --version         Display this application version
      --ansi|--no-ansi  Force (or disable --no-ansi) ANSI output
  -n, --no-interaction  Do not ask any interactive question
  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Available commands:
  completion  Dump the shell completion script
  help        Display help for a command
  list        List commands
  new         Create a new Laravel application

Create new laravel project

• laravel new mlcompetition
  • It may ask for 3 options: i) No starter kit, ii) Laravel breeze, iii) Laravel jetstream. Details can be found here. Please use either of breeze or jetstream template to integrate the authentication/login/register template/options.

┌ Would you like to install a starter kit? ────────────────────┐
 │ Laravel Breeze                                               │
 └──────────────────────────────────────────────────────────────┘

 ┌ Which Breeze stack would you like to install? ───────────────┐
 │ Blade                                                        │
 └──────────────────────────────────────────────────────────────┘

 ┌ Would you like dark mode support? ───────────────────────────┐
 │ Yes                                                          │
 └──────────────────────────────────────────────────────────────┘

 ┌ Which testing framework do you prefer? ──────────────────────┐
 │ PHPUnit                                                      │
 └──────────────────────────────────────────────────────────────┘

 ┌ Would you like to initialize a Git repository? ──────────────┐
 │ Yes                                                          │
 └──────────────────────────────────────────────────────────────┘

┌ Which database will your application use? ───────────────────┐
 │ MySQL                                                        │
 └──────────────────────────────────────────────────────────────┘

• Open the project folder with VSCode.
  • ./composer.json : contains the project’s assets.
  • ./resources/views/welcome.blade.php is the default welcome page. blade is a rendering template.
  • ./resources/views/dashboard.blade.php is a view file that gets loaded when a user successfully logs in.
• Type php artisan to see all different options/commands. Get familiar with all the available commands.
• Serve the project into built-in web server: php artisan serve

Connecting a MySQL Database with the Laravel Project

• Setting the Connection configurations: Make sure you edit the 2 following files:
  • .env file: Check the DB_ entries.
  • config/database.php file: check the mysql connection entries.
• Create a view:
  • resources/views/dbconn.blade.php

<?php
if(DB::connection()->getPdo()){
	echo "Successful connection to the database named ".DB::connection()->getDatabaseName();
}else{
	echo "Unsuccessful connection to the database named ".DB::connection()->getDatabaseName();
}
?>

• Then, add a route in the routes/web.php file:

Route::get('/dbconn', function(){
    return view('dbconn');
});

• Now, go check if localhost:8000/dbconn is successful or not.

  Front-end

• In the project directory run: npm run build. Here are the explanations for this command:
  • npm: One could say that it is a command native to the system, for calling Node Package Manager program.
  • run: It is a command native to npm. Keep in mind this is an alias to the original command run-script.
  • dev/build and prod: They’re user defined.
    • dev/build: Used for running the specific commands for serving the project, to any server, to live development. In the case of a web page, you’ll see your web page in the browser, and any change you make to the HTML code, for example, will be reflected immediately in the page you see in your browser.
    • prod: Compiles all the necessary files for production. Final product. In the case of a web page, for example, the HTML, CSS, and JS files you’ll handle to the client. The result of running this command, it is expected to be one single folder with all the afore mentioned content.
  • It creates the following files in ./public directory:

ashis@Ashiss-MacBook-Pro mlcompetition % tree public 
public
├── build
│   ├── assets
│   │   ├── app-6e0eadfb.js
│   │   └── app-e3a33e56.css
│   └── manifest.json
├── favicon.ico
├── index.php
└── robots.txt

2 directories, 6 files

• You will not be directly editing any of these files, instead you may edit ./resources/css/app.css and ./resources/js/app.js files.

Databases with Migrations

• Migrations are like version control for your database, allowing your team to define and share the application’s database schema definition. If you have ever had to tell a teammate to manually add a column to their local database schema after pulling in your changes from source control, you’ve faced the problem that Laravel’s database migrations solve.
• The Laravel Schema facade provides database agnostic support for creating and manipulating tables across all of Laravel’s supported database systems. Typically, migrations will use this facade to create and modify database tables and columns
• Before you do anything, edit the following entries in .env file at the project root directory:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=xxxx
DB_USERNAME=xxxx
DB_PASSWORD=xxxx

• Also, go to ./config/database.php and update the following as needed:

'mysql' => [
            'driver' => 'mysql',
            'url' => env('DATABASE_URL'),
            'host' => env('DB_HOST', '127.0.0.1'),
            'port' => env('DB_PORT', '3306'),
            'database' => env('DB_DATABASE', 'xxxxx'),
            'username' => env('DB_USERNAME', 'xxxxx'),
            'password' => env('DB_PASSWORD', 'xxxxx'),
            'unix_socket' => env('DB_SOCKET', ''),
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'prefix_indexes' => true,
            'strict' => true,
            'engine' => null,
            'options' => extension_loaded('pdo_mysql') ? array_filter([
                PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
            ]) : [],
        ],

• Migrate
  • Do it first time: php artisan migrate
    • This will create few tables in the chosen database:
      • users – all user info will be recorded here.
      • password_reset_tokens – will store tokens if someone forgets their password
      • password_access_tokens,
      • failed_jobs,
      • migrations.
  • Right after migration, go hit the Register button in the website (e.g., http://127.0.0.1:8000/).
    • Provide information to register an account. The site will then log you into the account.
    • Once logged in, the route shown would be: http://127.0.0.1:8000/dashboard
    • You can check that dashboard view when routed would be inaccessible if logged out.

ashis@Ashiss-MacBook-Pro lara2site % php artisan migrate

   INFO  Preparing database.  

  Creating migration table ..................................................................................................... 16ms DONE

   INFO  Running migrations.  

  2014_10_12_000000_create_users_table ......................................................................................... 20ms DONE
  2014_10_12_100000_create_password_reset_tokens_table ......................................................................... 14ms DONE
  2019_08_19_000000_create_failed_jobs_table ................................................................................... 12ms DONE
  2019_12_14_000001_create_personal_access_tokens_table ........................................................................ 16ms DONE

Working on the views

• Edit resources/views/layouts/app.blade.php to change the design.
• Add figures for the site in public/. Let’s create figs/ folder inside it which will contain all figures for the site. You may use the files in figs/ considering public/ as the site root directory.
  • The public site never has access outside the public/ directory.
• Generating migrations
  • You may use the make:migration Artisan command to generate a database migration. The new migration will be placed in your database/migrations directory. Each migration filename contains a timestamp that allows Laravel to determine the order of the migrations: php artisan make:migration create_flights_table.

ashis@Ashiss-MacBook-Pro mlcompetition % php artisan make:migration create_flights_table

   INFO  Migration [database/migrations/2023_09_13_180750_create_flights_table.php] created successfully.

• Content of that file would be something like below:

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    /**
     * The database connection that should be used by the migration.
     *
     * @var string
     */
    protected $connection = 'mysql';

    /**
     * Run the migrations.
     */
    public function up(): void
    {
        Schema::create('flights', function (Blueprint $table) {
            $table->id();
            $table->string('name');
            $table->string('airline');
            $table->timestamps();
        });
    }

    /**
     * Reverse the migrations.
     */
    public function down(): void
    {
        Schema::dropIfExists('flights');
    }
};

• Laravel will use the name of the migration to attempt to guess the name of the table and whether or not the migration will be creating a new table. If Laravel is able to determine the table name from the migration name, Laravel will pre-fill the generated migration file with the specified table. Otherwise, you may simply specify the table in the migration file manually.
• Squashing migrations
  • As you build your application, you may accumulate more and more migrations over time. This can lead to your database/migrations directory becoming bloated with potentially hundreds of migrations. If you would like, you may squash your migrations into a single SQL file. To get started, execute the schema:dump command:

php artisan schema:dump
 
# Dump the current database schema and prune all existing migrations...
php artisan schema:dump --prune

• When you execute this command, Laravel will write a “schema” file to your application’s database/schema directory. The schema file’s name will correspond to the database connection. Now, when you attempt to migrate your database and no other migrations have been executed, Laravel will first execute the SQL statements in the schema file of the database connection you are using. After executing the schema file’s SQL statements, Laravel will execute any remaining migrations that were not part of the schema dump.
• Migration squashing is only available for the MySQL, PostgreSQL, and SQLite databases and utilizes the database’s command-line client. Schema dumps may not be restored to in-memory SQLite databases.
• Migration Structure
  • A migration class contains two methods: up and down.
    • The up method is used to add new tables, columns, or indexes to your database,
    • The down method should reverse the operations performed by the up method.
  • Within both of these methods, you may use the Laravel schema builder to expressively create and modify tables.
• Setting The Migration Connection
  • If your migration will be interacting with a database connection other than your application’s default database connection, you should set the $connection property of your migration in the migration files: protected $connection = 'mysql';
• Running Migrations
  • To run all of your outstanding migrations, execute the migrate Artisan command: php artisan migrate
  • If you would like to see which migrations have run thus far, you may use the migrate:status Artisan command: php artisan migrate:status
  • If you would like to see the SQL statements that will be executed by the migrations without actually running them, you may provide the --pretend flag to the migrate command: php artisan migrate --pretend
• Rolling back migrations
  • To roll back the latest migration operation, you may use the rollback Artisan command. This command rolls back the last “batch” of migrations, which may include multiple migration files: php artisan migrate:rollback
  • If you would like to see the SQL statements that will be executed by the migrations without actually running them, you may provide the --pretend flag to the migrate:rollback command: php artisan migrate:rollback --pretend
  • The migrate:reset command will roll back all of your application’s migrations: php artisan migrate:reset
• Rollback and Migrate using a single command
  • The migrate:refresh command will roll back all of your migrations and then execute the migrate command. This command effectively re-creates your entire database:
  • php artisan migrate:refresh
• Drop all tables and Migrate
  • The migrate:fresh command will drop all tables from the database and then execute the migrate command: php artisan migrate:fresh
    • The migrate:fresh command will drop all database tables regardless of their prefix. This command should be used with caution when developing on a database that is shared with other applications.

      References (as of 9/6/2023)