Kasun Peiris peiris

Next.js client-only SPA example

Made this example to show how to use Next.js router for a 100% SPA (no JS server) app.

You use Next.js router like normally, but don't define getStaticProps and such. Instead you do client-only fetching with swr, react-query, or similar methods.

You can generate HTML fallback for the page if there's something meaningful to show before you "know" the params. (Remember, HTML is static, so it can't respond to dynamic query. But it can be different per route.)

Building

React.js software engineer practical test

In this practical test, we build a simple CRUD application called 🍔 The Fridge. We use this application to see what we have in our fridge at a glance and when do they expire.

Please read the instructions properly before you proceed.

⚙️ Tech Stack to be used

React.js (Latest)
TailwindCSS

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

First install Brew on your MAC

Setup Brew: ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew update
brew tap homebrew/dupes
brew tap homebrew/php
Install PHP 7.0.+ brew install php70
Install mcrypt: brew install mcrypt php70-mcrypt
Finally, install composer: brew install composer

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

	1. Update .htaccess file

	php_value upload_max_filesize 128M
	php_value post_max_size 128M
	php_value memory_limit 256M
	php_value max_execution_time 300
	php_value max_input_time 300

	OR

	- Open your terminal.
	- Browse to your master project directory or the top level of where you have a bunch of projects stored.
	- Run the command: ``find . -name "node_modules" -type d -prune -exec rm -rf '{}' +``

	####How it works

	``find .`` Instructs the find program to search for files in the current directory ..
	``-name "node_modules"`` Instructs the find program to search for files named “node_modules”.
	``-type d`` Instructs the find program to only look for file directories named “node_modules”.
	``-prune`` Instructs the find program to not descend into the current file/directory for it to exclude child “node_modules” directories. On Mac, since -d was specified, -prune has no effect on the find program’s lookup results (per the man pages). However, on Linux, -prune still instructs the find program to not descend into the current file/directory.

	// Add on element with overflow
	-webkit-mask-image: -webkit-radial-gradient(white, black);

	git fetch --all
	git reset --hard origin/master
	git pull origin master