- Update HISTORY.md
 - Commit the changes:
 
git add HISTORY.md
git commit -m "Changelog for upcoming release 0.1.1."
- Update version number (can also be minor or major)
 
bumpversion patch
| (defun dotspacemacs/layers () | |
| "Configuration Layers declaration." | |
| (setq-default | |
| ;; ... | |
| ;; List of additional packages that will be installed wihout being | |
| ;; wrapped in a layer. If you need some configuration for these | |
| ;; packages then consider to create a layer, you can also put the | |
| ;; configuration in `dotspacemacs/config'. | |
| dotspacemacs-additional-packages '(cuda-mode) | |
| ;; ... | 
| def index(conn, %{"event" => "true"}) do | |
| conn = conn | |
| |> put_resp_content_type("text/event-stream") | |
| |> send_chunked(200) | |
| {:ok, conn} = chunk(conn, ["data: ", JSON.encode!(Thermostat.Data.get()), "\n\n"]) | |
| Phoenix.Topic.subscribe self, "data" | |
| data_updated(conn) | |
| end | |
| defp data_updated(conn) do | 
| ffmpeg -i intro.mov -vf "boxblur=5:1" intro-blur.mov | 
| $ ls | |
| other_thing.exs | |
| thing.exs | |
| $ elixir thing.exs | |
| calling other | |
| other thing! | |
| hooray! | 
git add HISTORY.md
git commit -m "Changelog for upcoming release 0.1.1."
bumpversion patch
| """ | |
| Usage: python remove_output.py notebook.ipynb [ > without_output.ipynb ] | |
| Modified from remove_output by Minrk | |
| """ | |
| import sys | |
| import io | |
| import os | |
| from IPython.nbformat.current import read, write | 
Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).
Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)
Alter the port the script talks to from 8000 to 80:
}).listen(80);