Once upon a time I was the serverless guy at a startup company building lambda functions. My function went into production at 128mb of memory and a timeout of 3 seconds. Because of game had "live races" we would see big spikes in traffic at certain times of the day, and unfortunately I would also see big spikes in the number of errors in the CloudWatch metrics charts... My boss even opened the website during the high volume event and noticed requests to the lambda returning 400 error. In the cloudwatch logs I could norrow down the logs to just the high volume time and see many timeout errors happening during this period. Needless to say, this is not a good look, and you don't want it to happen to you (especially you, future Jim)!
If you are new to Docker or want a refresher on the key concepts of Docker, Jake Wright has a great video on youtube going over the topic called "Learn Docker in 12 Minutes".
This is an interesting problem that I just solved yesterday- creating a CNAME file from a Travis CI server.
I stumbled across this answer while looking at this stack overflow post. I thought it was such a great solution to my problem that I decided to write a blog post about it to help me not forget it.
I personal like the control you have when using git from the command line, and a nice thing to be able to do is see the changes I've made (duh hehe). I really didn't know the proper name for this so I am calling it the "git commit lifecycle", but basically these are shell scripts you can run to see your changes before you add the changes, after you add them but before committing, and after committing. Enjoy!
The posts on this site are written and maintained by Jim Lynch. About Jim...