-
Commit all your changes
-
Remove everything from the repository cache. Go to your repo directory and run this command.
git rm -r --cached .
It will only clear the cache. Your files and git history will stay.
| # stop script on error signal | |
| set -e | |
| SITE="your-site-original-folder-name.com" | |
| DEPL="/home/forge/deployments/${SITE}" | |
| # create directory and any intermediate directories if don't exist | |
| mkdir -p ${DEPL} | |
| CUR="/home/forge/${SITE}" |
The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.
The correct way of creating a private frok by duplicating the repo is documented here.
For this assignment the commands are:
git clone --bare [email protected]:usi-systems/easytrace.git
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.