jdecode

200 simultaneous request should start to be heavy for your server, making 5K requests in total

ab -c 200 -n 5000 -r https://website.com/

jdecode

#duh! Pick the base image (this is latest as of May 2020)
FROM php:7.4.5-apache

# Install composer
RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer

#duh!
RUN apt-get update

jdecode

sudo apt-get install --reinstall gnome-control-center

jdecode

As a developer

• I read [books, documentation, blogs...]
• I write [code, documentation...]
• I communicate [with colleagues, project-teams, bosses/managers...]
• I learn [from books, w3schools, stackoverflow, youtube, tutorials, video-courses, in-office training, meetups, online-sessions...]

As a developer if someone does all of the above 4 points then that person is "at the very least" a competent developer.

When you read, write communicate and learn - you grow.

jdecode

YouTube link of the talk - https://www.youtube.com/watch?v=BSaAMQVq01E Robert C. Martin aka Uncle Bob

1. We Will Not Ship Shit
   Do a good job.
   Do not be lazy.
   Do not be lousy.

jdecode

Edit: The original title of this gist was "Vue from scratch" but soon (actually from the very initial stage) it took the road of "CakePHP and Vue as monorepo". This still contains almost all the Vue specific items as listed below (the 18-point list is not changed, although some of the items are skipped or have notes added in comments). This is a fairly large piece of text + screenshots (to read and see) but not really time consuming to implement (that's what I tell myself, anyway). Happy reading.... caking and vueing... cakueing perhaps!

Thanks to github.com/pankajvashisht-ucreate for the list

Following is the original 18-point list shared by Pankaj Vashisht for someone who is starting in Vue.js from scratch

1. Node installation
2. Initialization of package.json file
3. Basic understanding of script key in package.json file

jdecode

The more I watch Rick's sessions from 2017, 2018 and 2019, more confused I get - so I guess I'd write it down.

There are 3 core steps (some have more, I want to stick to 3) to create a decent model that works well:

1. Understand the usecase + create ERD(list entities and relations)
2. Identify the access patterns - R/W workloads, query dimensions and aggregations
3. Data modeling - avoid relational patterns, use 1 table(if there aren't any "documents", 1 should be fine)
4. R.R.R = Review > Repeat > Review (go on till it makes sense)

jdecode

Following is the CORS configuration that goes under Bucket > Permissions

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>*</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>POST</AllowedMethod>
    <AllowedHeader>*</AllowedHeader>

jdecode

This gist is to take notes for a "note-taking-app" so that a full fledged production-ready app could be created.

Server(or "back-end") = Part of the application that "serves"

Client(or "front-end") = Part of the application that "requests"

Best possible thought process applied to all sections with as much options to be included as possible:

1. Database - MySQL, Postgres, DynamoDB, Firebase
2. Code - PHP, Node.js, CakePHP, Laravel, SlimPHP, nest.js, adonis.js

jdecode

Setup of Noter in CakePHP, MySQL and Docker (and other tools) - notes, commands, snippets go here.

Direct branch-URL - https://github.com/konnector-dev/noter/tree/cakephp-mysql

Repo URL - https://github.com/konnector-dev/noter

Branch - cakephp-mysql