Currently the Serverless framework only offers lifecycle events that are bound to commands and also are very coarse. Each core plugin only exposes the events that are defined by the framework. This is suboptimal for plugin authors as they want to hook special events within the deployment process.
The PR adds fine grained lifecycles to the AWS deployment process (see below for the current implementation process) and makes the package/deploy plugin implementation non-breaking.
| #!/bin/bash | |
| # | |
| # Extracts tracks from stems files and puts them in folders | |
| # named after the stem filenames. | |
| # | |
| for stem in *.mp4 | |
| do | |
| name=${stem%\.*} |
#Understanding closures, callbacks and promises
For a code newbie like myself, callbacks, closures and promises are scary JavaScript concepts.
10 months into my full-time dev career, and I would struggle to explain these words to a peer.
So I decided it was time to face my fears, and try to get my head around each concept.
Here are the notes from my initial reading. I'll continue to refine them as my understanding improves.
| /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024 | |
| /sbin/mkswap /var/swap.1 | |
| /sbin/swapon /var/swap.1 | |
| #To enable it at the boot time, add the following entry into /etc/fstab: | |
| /swapfile swap swap defaults 0 0 |
| #! /usr/bin/env bash | |
| ### | |
| # | |
| # install_mysql.sh | |
| # | |
| # This script assumes your Vagrantfile has been configured to map the root of | |
| # your application to /vagrant and that your web root is the "public" folder | |
| # (Laravel standard). Standard and error output is sent to | |
| # /vagrant/vm_build.log during provisioning. |
