essen

[{h1,<<"cowboy_req:method(3)">>},
 {h2,<<"Name">>},
 {p,[<<"cowboy_req:method - HTTP method">>]},
 {h2,<<"Description">>},
 {listing,#{language => <<"erlang">>},
          <<"method(Req :: cowboy_req:req()) -> Method :: binary()">>},
 {p,[<<"Return the request's HTTP method.">>]},
 {p,[<<"The method can also be obtained using pattern matching:">>]},
 {listing,#{language => <<"erlang">>},<<"#{method := Method} = Req.">>},
 {h2,<<"Arguments">>},

essen

cowboy_req(3)             Cowboy Function Reference             cowboy_req(3)

NAME
       cowboy_req - HTTP request and response

DESCRIPTION
       The  module  cowboy_req  provides  functions to access, manipulate and
       respond to requests.

       There are four types of functions in this module. They can be  differ‐

essen

COWBOY:START_CLEAR(3)                                   COWBOY:START_CLEAR(3)

NAME
       cowboy:start_clear - Listen for connections using plain TCP

DESCRIPTION
           start_clear(Name          :: ranch:ref(),
                       NumAcceptors  :: non_neg_integer(),
                       TransportOpts :: ranch_tcp:opts(),
                       ProtocolOpts  :: opts())

essen

-module(fw_resource).

-type resource() :: module().
-type uri() :: string().
-type relation() :: index | self | ...
-type action() :: fetch | stream | create | replace | append | process | delete | patch | atom().
-type media_type() :: atom().
-type internal_representation() :: any().
-type request() :: ...

essen

include erlang.mk

ifdef SKIP_DEPS
deps::
	$(verbose) for dep in $(ALL_APPS_DIRS) ; do \
		mkdir -p $$dep/ebin; \
	done
	$(verbose) for dep in $(ALL_APPS_DIRS) ; do \
		$(MAKE) -C $$dep IS_APP=1 || exit $$?; \
	done

essen

A common concern with REST APIs is how do you version them? The answer is often something like put the version in the beginning of the URI path. But that’s a terrible advice. This prevents you to make small updates to your API, because you need to duplicate everything every time you increase the version.

A good way to version an API is to not do it. Instead, you can version the media types.

essen

-module(map_req).
-export([init/2]).

init(#{method := <<"GET">>} = Req, State) ->
	cowboy_req:reply(204, Req),
	{ok, Req, State}.

essen

== .erl .core

module.erl: header.hrl behavior.erl parse_transform.erl
module.core:

ebin/$(PROJECT).app:: $(ERL_FILES) $(CORE_FILES)
    erlc ... $?

== .xrl .yrl

essen

PROJECT = ttt
DEPS = stuff
dep_stuff = git https://github.com/essen/stuff master

include erlang.mk
-include $(DEPS_DIR)/stuff/dist.mk

$(DEPS_DIR)/stuff/dist.mk: $(DEPS_DIR)/stuff ;

essen

You need a schedule, man

Overview

Have three kinds of projects/work:

• money making (gotta buy bread)

• first class (generally involves a large number of users and/or me having a lot of fun)

• second class (satellite and toy projects)