jdecode

Laravel developer roadmap

[knowledge portfolio]

Highly opinionated, for F&L

Tech stack

1. Docker

2. Read Dockerfile

jdecode

Multiple commit attributes [using "aliases"]

https://github.com/orgs/community/discussions/24419

File names

query = """
        {
 repository(owner: \""""+ownerVal+"""\", name: \""""+repoVal+"""\") {

jdecode

What is the challenge?

The challenge is to fail.
The challenge is to fail repeatedly.
In this world full of opportunities and options, the biggest challenge is to fail.

You absolutely, positively, cannot fail.
You have to put in delibrate effort to fail.
You have to put in delibrate effort, repeatedly, to fail every time.

jdecode

Notes about Ubuntu

1. I use Ubuntu (22.x LTS) - as of Mid 2023
2. I am using Ubuntu since 2005 (back when they used to send a CD in the mail)
3. I have had "ZERO" problems while setting up Docker on my Ubuntu machine
4. If you are a developer using Windows, please stop and change your career.
   1. Unless you are using WSL2 (Windows Subsystem for Linux)
   2. In which case, why not just use Ubuntu directly?
5. If you are a developer using Mac, please stop and change your career.
   1. Unless you know how to solve your Docker issues
6. I have had way too many people with Docker issues on Mac

jdecode

Question

Full stack development in Laravel : What to pick and how? [opinionated, highly]

Answer

It depends on the skill set of the developer.

Developer traits #1

1. Highly competent and experienced in PHP, and have been writing APIs in Laravel for a significant amount of time
2. Has some experience in writing HTML, CSS and JavaScript, and can use the HTML helpers provided by design team (or from Tailwind components, or some other framework) to create Blade templates

jdecode

In Docker

1. Install xdebug in docker
2. discover_client_host to be set to false/0
3. client_host to be set to docker.host.internal, using extra_hosts as host.docker.internal:host-gateway

In PhpStorm

1. Start listening
2. PHP > Debug : Clear Break at first line in PHP scripts, Debug port = 9000,9003 [check Can accept external connections]
3. PHP > Servers : + : Host/Port of docker, map public/index.php of host and server

jdecode

Sample commands to:

1. Create a new delivery pipeline:

gcloud deploy apply --file=clouddeploy.yaml --region=asia-southeast1 --project=jdecode

1. Create a new release:

gcloud deploy releases create test-release-001 \
--project=jdecode \
--region=asia-southeast1 \

jdecode

Note : Choice of OS is not a "preference", it's a result of the work you do

1. If you are into web-dev, using Java, Python, PHP, React, Vue, TailwindCSS, Alpinejs, Docker etc - then use any popular Linux distro, say, "Ubuntu" [or Fedora / Debian / CentOS etc]
2. If you create mobile apps that need to be deployed to App Store (Apple), using Swift, Kotlin, React Native etc - then use "Mac OS"
3. If you create applications (desktop/web) that require DLL-files/MS-libraries using, say, C#,.Net core etc - then use "Windows"

Opinion:
If you are into non-window-binding and non-mac-os-binding web-dev, and incline toward using Windows or Mac OS, then change your career or the OS

jdecode

Env vars

• APP_NAME Techathon 2.0 | 2022
• APP_ENV production
• DB_CONNECTION pgsql
• APP_DEBUG false
• APP_KEY base64:BASE_64_ENCODED_APP_KEY
• DB_DATABASE postgres
• DB_USERNAME postgres
• DB_PASSWORD random-password-goes-here
• DB_PORT 5432

jdecode

I have been doing a lot of "pros-and-cons" stuff from a little over 2 years now - about using Laravel.

I made it a big deal (and I believe I regret it in a certain capacity).

It should not have been a big deal.

It is a just another framework.

Finally, I have caught up with my senses and I strongly believe that I was too arrogant or stupid to not go down the Laravel path.