From c807880f7ac73f813b2660ea81a00f7712a4e793 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 29 Aug 2016 12:39:49 +0200 Subject: Add old mailing list archives --- .../static/archives/extend/2014-March/000340.html | 105 ++++++++++ .../static/archives/extend/2014-March/000341.html | 81 ++++++++ .../static/archives/extend/2014-March/000342.html | 129 ++++++++++++ .../static/archives/extend/2014-March/000343.html | 121 +++++++++++ .../static/archives/extend/2014-March/000344.html | 134 +++++++++++++ .../static/archives/extend/2014-March/000345.html | 148 ++++++++++++++ .../static/archives/extend/2014-March/000346.html | 149 ++++++++++++++ .../static/archives/extend/2014-March/000347.html | 221 +++++++++++++++++++++ .../static/archives/extend/2014-March/000348.html | 70 +++++++ .../static/archives/extend/2014-March/000349.html | 87 ++++++++ .../static/archives/extend/2014-March/000350.html | 115 +++++++++++ .../static/archives/extend/2014-March/000351.html | 131 ++++++++++++ .../static/archives/extend/2014-March/000352.html | 157 +++++++++++++++ .../static/archives/extend/2014-March/000353.html | 159 +++++++++++++++ .../static/archives/extend/2014-March/000354.html | 180 +++++++++++++++++ .../static/archives/extend/2014-March/000355.html | 186 +++++++++++++++++ .../static/archives/extend/2014-March/000356.html | 96 +++++++++ .../static/archives/extend/2014-March/000357.html | 125 ++++++++++++ .../static/archives/extend/2014-March/000358.html | 78 ++++++++ .../static/archives/extend/2014-March/000359.html | 76 +++++++ .../static/archives/extend/2014-March/000360.html | 80 ++++++++ .../static/archives/extend/2014-March/000361.html | 95 +++++++++ .../static/archives/extend/2014-March/000362.html | 106 ++++++++++ .../static/archives/extend/2014-March/000363.html | 116 +++++++++++ .../static/archives/extend/2014-March/author.html | 167 ++++++++++++++++ _build/static/archives/extend/2014-March/date.html | 167 ++++++++++++++++ .../static/archives/extend/2014-March/index.html | 1 + .../static/archives/extend/2014-March/subject.html | 167 ++++++++++++++++ .../static/archives/extend/2014-March/thread.html | 219 ++++++++++++++++++++ 29 files changed, 3666 insertions(+) create mode 100644 _build/static/archives/extend/2014-March/000340.html create mode 100644 _build/static/archives/extend/2014-March/000341.html create mode 100644 _build/static/archives/extend/2014-March/000342.html create mode 100644 _build/static/archives/extend/2014-March/000343.html create mode 100644 _build/static/archives/extend/2014-March/000344.html create mode 100644 _build/static/archives/extend/2014-March/000345.html create mode 100644 _build/static/archives/extend/2014-March/000346.html create mode 100644 _build/static/archives/extend/2014-March/000347.html create mode 100644 _build/static/archives/extend/2014-March/000348.html create mode 100644 _build/static/archives/extend/2014-March/000349.html create mode 100644 _build/static/archives/extend/2014-March/000350.html create mode 100644 _build/static/archives/extend/2014-March/000351.html create mode 100644 _build/static/archives/extend/2014-March/000352.html create mode 100644 _build/static/archives/extend/2014-March/000353.html create mode 100644 _build/static/archives/extend/2014-March/000354.html create mode 100644 _build/static/archives/extend/2014-March/000355.html create mode 100644 _build/static/archives/extend/2014-March/000356.html create mode 100644 _build/static/archives/extend/2014-March/000357.html create mode 100644 _build/static/archives/extend/2014-March/000358.html create mode 100644 _build/static/archives/extend/2014-March/000359.html create mode 100644 _build/static/archives/extend/2014-March/000360.html create mode 100644 _build/static/archives/extend/2014-March/000361.html create mode 100644 _build/static/archives/extend/2014-March/000362.html create mode 100644 _build/static/archives/extend/2014-March/000363.html create mode 100644 _build/static/archives/extend/2014-March/author.html create mode 100644 _build/static/archives/extend/2014-March/date.html create mode 120000 _build/static/archives/extend/2014-March/index.html create mode 100644 _build/static/archives/extend/2014-March/subject.html create mode 100644 _build/static/archives/extend/2014-March/thread.html (limited to '_build/static/archives/extend/2014-March') diff --git a/_build/static/archives/extend/2014-March/000340.html b/_build/static/archives/extend/2014-March/000340.html new file mode 100644 index 00000000..228ab579 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000340.html @@ -0,0 +1,105 @@ + + + + [99s-extend] usage of make_* command + + + + + + + + + + +

[99s-extend] usage of make_* command

+ Anton Koval' + psihonavt at gmail.com +
+ Mon Mar 3 21:49:33 CET 2014 +

+
+ +
Hello,
+
+I have next structure of my project:
+.
+├── deps
+│   ├── cowboy
+│   ├── cowlib
+│   ├── erlang_iconv
+│   ├── erlydtl
+│   ├── mochiweb_xpath
+│   └── ranch
+├── ebin
+│   ├── fetchers.beam
+│   ├── parsers.beam
+│   └── wasearch_sup.beam
+├── erlang.mk
+├── Makefile
+├── _rel
+│   └── ....
+├── relx
+├── relx.config
+├── src
+│   ├── fetchers.erl
+│   ├── main_handler.erl
+│   ├── parsers.erl
+│   ├── tests
+│   │   ├── parsers_SUITE_data
+│   │   ├── parsers_SUITE.erl
+│   │   ├── ....
+│   ├── wasearch_app.erl
+│   ├── wasearch.app.src
+│   └── wasearch_sup.erl
+└── templates
+    └── index.dtl
+
+I would prefer to store tests not in `src` directory but rather in `tests`
+subdirectory.
+Erlang.mk README says: You can run an individual test suite by using the
+special test_* targets. For example if you have a common_test suite named
+spdy and you want to run only this suite and not the others, you can use
+the make test_spdy command.
+And of course `make test_parsers`  returns `no rule to make target` error.
+Is there a way to run suites from custom directory with
+`make_<mod_name_with_suite>` command?
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20140303/52007acc/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000341.html b/_build/static/archives/extend/2014-March/000341.html new file mode 100644 index 00000000..4ae144b9 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000341.html @@ -0,0 +1,81 @@ + + + + [99s-extend] Cowboy pre request filter + + + + + + + + + + +

[99s-extend] Cowboy pre request filter

+ Mark Nijhof + mark.nijhof at cre8ivethought.com +
+ Thu Mar 6 00:47:08 CET 2014 +

+
+ +
Hi,
+
+I want to create a module that basically sits between the incoming request
+and the http handler for that request to ensure a request is authenticated
+(using a cookie), if the request is not authenticated then I like to
+redirect to a specific login page (which should not be filtered).
+
+Is this possible with Cowboy? Should I use the onrequest hook (not sure if
+I can force redirects from there) for that or is there a better way?
+
+Cheers,
+
+-Mark
+
+-- 
+Mark Nijhof
+t:   @MarkNijhof <https://twitter.com/MarkNijhof>
+s:  marknijhof
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20140306/a517215b/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000342.html b/_build/static/archives/extend/2014-March/000342.html new file mode 100644 index 00000000..b2779a5d --- /dev/null +++ b/_build/static/archives/extend/2014-March/000342.html @@ -0,0 +1,129 @@ + + + + [99s-extend] Cowboy pre request filter + + + + + + + + + + +

[99s-extend] Cowboy pre request filter

+ Mark Nijhof + mark.nijhof at cre8ivethought.com +
+ Thu Mar 6 10:52:01 CET 2014 +

+
+ +
I also found the answer to my own question: custom middleware
+
+I just created:
+
+   1 -module(authentication_middleware).
+   2
+   3 -behaviour(cowboy_middleware).
+   4
+   5 -export([execute/2]).
+   6
+   7 execute(Req, Env) ->
+   8
+   9     {Path, Req1} = cowboy_req:path(Req),
+  10
+  11     case Path of
+  12         <<"/login.html">> ->
+  13             {ok, Req1, Env};
+  14         <<"/do_login">> ->
+  15             {ok, Req1, Env};
+  16         _ ->
+  17             case id3as_security:is_request_authenticated(Req1) of
+  18                 {error, eauth, Req2} ->
+  19                     {ok, Req4} = cowboy_req:reply(303,
+[{<<"Location">>, <<"/login.html">>}], "", Req2),
+  20                     {halt, Req4};
+  21                 {authenticated, _Id, Req2} ->
+  22                    {ok, Req2, Env}
+  23             end
+  24     end.
+
+And put this between the cowboy_router and cowboy_handler and life is all
+good.
+
+-Mark
+
+
+
+On Thu, Mar 6, 2014 at 12:47 AM, Mark Nijhof <mark.nijhof at cre8ivethought.com
+> wrote:
+
+> Hi,
+>
+> I want to create a module that basically sits between the incoming request
+> and the http handler for that request to ensure a request is authenticated
+> (using a cookie), if the request is not authenticated then I like to
+> redirect to a specific login page (which should not be filtered).
+>
+> Is this possible with Cowboy? Should I use the onrequest hook (not sure if
+> I can force redirects from there) for that or is there a better way?
+>
+> Cheers,
+>
+> -Mark
+>
+> --
+> Mark Nijhof
+> t:   @MarkNijhof <https://twitter.com/MarkNijhof>
+> s:  marknijhof
+>
+>
+
+
+-- 
+Mark Nijhof
+t:   @MarkNijhof <https://twitter.com/MarkNijhof>
+s:  marknijhof
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20140306/24422ef2/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000343.html b/_build/static/archives/extend/2014-March/000343.html new file mode 100644 index 00000000..b027aebb --- /dev/null +++ b/_build/static/archives/extend/2014-March/000343.html @@ -0,0 +1,121 @@ + + + + [99s-extend] usage of make_* command + + + + + + + + + + +

[99s-extend] usage of make_* command

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Mar 6 15:40:59 CET 2014 +

+
+ +
Tests should be in ./tests, not ./src/tests.
+
+If you put them in ./tests everything you mentioned will work.
+
+On 03/03/2014 09:49 PM, Anton Koval' wrote:
+> Hello,
+>
+> I have next structure of my project:
+> .
+> ├── deps
+> │   ├── cowboy
+> │   ├── cowlib
+> │   ├── erlang_iconv
+> │   ├── erlydtl
+> │   ├── mochiweb_xpath
+> │   └── ranch
+> ├── ebin
+> │   ├── fetchers.beam
+> │   ├── parsers.beam
+> │   └── wasearch_sup.beam
+> ├── erlang.mk <http://erlang.mk>
+> ├── Makefile
+> ├── _rel
+> │   └── ....
+> ├── relx
+> ├── relx.config
+> ├── src
+> │   ├── fetchers.erl
+> │   ├── main_handler.erl
+> │   ├── parsers.erl
+> │   ├── tests
+> │   │   ├── parsers_SUITE_data
+> │   │   ├── parsers_SUITE.erl
+> │   │   ├── ....
+> │   ├── wasearch_app.erl
+> │   ├── wasearch.app.src
+> │   └── wasearch_sup.erl
+> └── templates
+>      └── index.dtl
+>
+> I would prefer to store tests not in `src` directory but rather in
+> `tests` subdirectory.
+> Erlang.mk README says: You can run an individual test suite by using the
+> special |test_*| targets. For example if you have a common_test suite
+> named |spdy| and you want to run only this suite and not the others, you
+> can use the |make test_spdy| command.
+> And of course `make test_parsers`  returns `no rule to make target` error.
+> Is there a way to run suites from custom directory with
+> `make_<mod_name_with_suite>` command?
+>
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> https://lists.ninenines.eu/listinfo/extend
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000344.html b/_build/static/archives/extend/2014-March/000344.html new file mode 100644 index 00000000..d6d3e174 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000344.html @@ -0,0 +1,134 @@ + + + + [99s-extend] usage of make_* command + + + + + + + + + + +

[99s-extend] usage of make_* command

+ Anton Koval' + psihonavt at gmail.com +
+ Thu Mar 6 15:50:01 CET 2014 +

+
+ +
Thank you for answer.
+Is it common way (for OTP-based application) to store tests in `tests`
+subdirectory rather then in `src/tests/`?
+
+
+On Thu, Mar 6, 2014 at 4:40 PM, Loïc Hoguin <essen at ninenines.eu> wrote:
+
+> Tests should be in ./tests, not ./src/tests.
+>
+> If you put them in ./tests everything you mentioned will work.
+>
+>
+> On 03/03/2014 09:49 PM, Anton Koval' wrote:
+>
+>> Hello,
+>>
+>> I have next structure of my project:
+>> .
+>> ├── deps
+>> │   ├── cowboy
+>> │   ├── cowlib
+>> │   ├── erlang_iconv
+>> │   ├── erlydtl
+>> │   ├── mochiweb_xpath
+>> │   └── ranch
+>> ├── ebin
+>> │   ├── fetchers.beam
+>> │   ├── parsers.beam
+>> │   └── wasearch_sup.beam
+>> ├── erlang.mk <http://erlang.mk>
+>>
+>> ├── Makefile
+>> ├── _rel
+>> │   └── ....
+>> ├── relx
+>> ├── relx.config
+>> ├── src
+>> │   ├── fetchers.erl
+>> │   ├── main_handler.erl
+>> │   ├── parsers.erl
+>> │   ├── tests
+>> │   │   ├── parsers_SUITE_data
+>> │   │   ├── parsers_SUITE.erl
+>> │   │   ├── ....
+>> │   ├── wasearch_app.erl
+>> │   ├── wasearch.app.src
+>> │   └── wasearch_sup.erl
+>> └── templates
+>>      └── index.dtl
+>>
+>> I would prefer to store tests not in `src` directory but rather in
+>> `tests` subdirectory.
+>> Erlang.mk README says: You can run an individual test suite by using the
+>> special |test_*| targets. For example if you have a common_test suite
+>> named |spdy| and you want to run only this suite and not the others, you
+>> can use the |make test_spdy| command.
+>> And of course `make test_parsers`  returns `no rule to make target` error.
+>> Is there a way to run suites from custom directory with
+>> `make_<mod_name_with_suite>` command?
+>>
+>>
+>> _______________________________________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> https://lists.ninenines.eu/listinfo/extend
+>>
+>>
+> --
+> Loïc Hoguin
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20140306/6fa8fe3b/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000345.html b/_build/static/archives/extend/2014-March/000345.html new file mode 100644 index 00000000..1da559eb --- /dev/null +++ b/_build/static/archives/extend/2014-March/000345.html @@ -0,0 +1,148 @@ + + + + [99s-extend] usage of make_* command + + + + + + + + + + +

[99s-extend] usage of make_* command

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Mar 6 15:51:58 CET 2014 +

+
+ +
Sorry I meant ./test/ not ./tests/
+
+But yes. That's how OTP does it.
+
+On 03/06/2014 03:50 PM, Anton Koval' wrote:
+> Thank you for answer.
+> Is it common way (for OTP-based application) to store tests in `tests`
+> subdirectory rather then in `src/tests/`?
+>
+>
+> On Thu, Mar 6, 2014 at 4:40 PM, Loïc Hoguin <essen at ninenines.eu
+> <mailto:essen at ninenines.eu>> wrote:
+>
+>     Tests should be in ./tests, not ./src/tests.
+>
+>     If you put them in ./tests everything you mentioned will work.
+>
+>
+>     On 03/03/2014 09:49 PM, Anton Koval' wrote:
+>
+>         Hello,
+>
+>         I have next structure of my project:
+>         .
+>         ├── deps
+>         │   ├── cowboy
+>         │   ├── cowlib
+>         │   ├── erlang_iconv
+>         │   ├── erlydtl
+>         │   ├── mochiweb_xpath
+>         │   └── ranch
+>         ├── ebin
+>         │   ├── fetchers.beam
+>         │   ├── parsers.beam
+>         │   └── wasearch_sup.beam
+>         ├── erlang.mk <http://erlang.mk> <http://erlang.mk>
+>
+>         ├── Makefile
+>         ├── _rel
+>         │   └── ....
+>         ├── relx
+>         ├── relx.config
+>         ├── src
+>         │   ├── fetchers.erl
+>         │   ├── main_handler.erl
+>         │   ├── parsers.erl
+>         │   ├── tests
+>         │   │   ├── parsers_SUITE_data
+>         │   │   ├── parsers_SUITE.erl
+>         │   │   ├── ....
+>         │   ├── wasearch_app.erl
+>         │   ├── wasearch.app.src
+>         │   └── wasearch_sup.erl
+>         └── templates
+>               └── index.dtl
+>
+>         I would prefer to store tests not in `src` directory but rather in
+>         `tests` subdirectory.
+>         Erlang.mk README says: You can run an individual test suite by
+>         using the
+>         special |test_*| targets. For example if you have a common_test
+>         suite
+>         named |spdy| and you want to run only this suite and not the
+>         others, you
+>         can use the |make test_spdy| command.
+>         And of course `make test_parsers`  returns `no rule to make
+>         target` error.
+>         Is there a way to run suites from custom directory with
+>         `make_<mod_name_with_suite>` command?
+>
+>
+>         _________________________________________________
+>         Extend mailing list
+>         Extend at lists.ninenines.eu <mailto:Extend at lists.ninenines.eu>
+>         https://lists.ninenines.eu/__listinfo/extend
+>         <https://lists.ninenines.eu/listinfo/extend>
+>
+>
+>     --
+>     Loïc Hoguin
+>     http://ninenines.eu
+>
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000346.html b/_build/static/archives/extend/2014-March/000346.html new file mode 100644 index 00000000..c5372244 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000346.html @@ -0,0 +1,149 @@ + + + + [99s-extend] Trying to grok erlang.mk + + + + + + + + + + +

[99s-extend] Trying to grok erlang.mk

+ lloyd at writersglen.com + lloyd at writersglen.com +
+ Thu Mar 6 21:29:59 CET 2014 +

+
+ +
Hello,
+
+To secure my understanding of erlang.mk, I've been trying to create the simplest possible example I can imagine. Which gives me this:
+
+min
+   erlang.mk
+   Makefile
+   src
+      min.app.src
+      min.erl
+
+*** Where Makefile is:
+
+PROJECT = min
+
+include erlang.mk
+
+*** min.app.src is:
+
+{application, min,
+         [{description,[]},
+          {vsn,"0.1.0"},
+          {registered,[]},
+          {applications,[kernel,stdlib]},
+          {env,[]},
+          {modules,[]}]}.
+
+*** and min.erl is:
+
+-module(min).
+
+-export([hello/0]).
+
+hello() ->
+   io:format("Hello min!~n~n").
+
+*** But when I call make, I get this:
+
+/min$ make
+ ERLC   min.erl
+ APP    min .app.src
+cat: src/min: No such file or directory
+cat: .app.src: No such file or directory
+sed: can't read .app: No such file or directory
+make: *** [app] Error 2
+
+*** Observations
+
+min.erl compiles just  fine
+min.app.src breaks the compile
+
+*** Questions: 
+
+1) How can I correct this?
+2) How can I structure directories and make files for a project that involves several applications?
+
+Many thanks,
+
+LRP
+
+
+*********************************************
+My books:
+
+THE GOSPEL OF ASHES
+http://thegospelofashes.com
+
+Strength is not enough. Do they have the courage 
+and the cunning? Can they survive long enough to 
+save the lives of millions?  
+
+FREEIN' PANCHO
+http://freeinpancho.com
+
+A community of misfits help a troubled boy find his way 
+
+AYA TAKEO
+http://ayatakeo.com
+
+Star-crossed love, war and power in an alternative 
+universe
+
+Available through Amazon or by request from your 
+favorite bookstore
+
+
+**********************************************
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000347.html b/_build/static/archives/extend/2014-March/000347.html new file mode 100644 index 00000000..b8e2990a --- /dev/null +++ b/_build/static/archives/extend/2014-March/000347.html @@ -0,0 +1,221 @@ + + + + [99s-extend] Trying to grok erlang.mk + + + + + + + + + + +

[99s-extend] Trying to grok erlang.mk

+ Ivan Uemlianin + ivan at llaisdy.com +
+ Fri Mar 7 13:37:27 CET 2014 +

+
+ +
Dear Lloyd
+
+I've just tried this with file layout and contents copied from your 
+email, and make works fine here I'm afraid.
+
+One odd thing I noticed in your make output ...
+
+ > /min$ make
+ >   ERLC   min.erl
+ >   APP    min .app.src
+ > cat: src/min: No such file or directory
+ > cat: .app.src: No such file or directory
+ > sed: can't read .app: No such file or directory
+ > make: *** [app] Error 2
+
+... is that in the APP line, the filename min.app.src has a space in it, 
+and it looks (in the cat lines) like it's broken down into src/min and 
+.app.src (ie ./.app.src).  I can't imagine why that's happening, but 
+that's what's causing the problem I should think.
+
+ > 2) How can I structure directories and make files for a project
+ >    that involves several applications?
+
+I don't know if it's the "correct" way with erlang.mk but, as a refugee 
+from rebar, I have apps set out rebar-style and use old-school recursive 
+make. e.g.:
+
+max/
+   erlang.mk
+   Makefile
+   apps/
+     app1/
+       Makefile
+       src/
+     app2/
+       Makefile
+       src/
+
+Top level Makefile doesn't need to include erlang.mk, and has lines like:
+
+all:
+	$(MAKE) -C apps/app1
+	$(MAKE) -C apps/app2
+
+Lower level Makefiles include erlang.mk.
+
+Best wishes
+
+Ivan
+
+
+On 06/03/2014 20:29, lloyd at writersglen.com wrote:
+> Hello,
+>
+> To secure my understanding of erlang.mk, I've been trying to create the simplest possible example I can imagine. Which gives me this:
+>
+> min
+>     erlang.mk
+>     Makefile
+>     src
+>        min.app.src
+>        min.erl
+>
+> *** Where Makefile is:
+>
+> PROJECT = min
+>
+> include erlang.mk
+>
+> *** min.app.src is:
+>
+> {application, min,
+>           [{description,[]},
+>            {vsn,"0.1.0"},
+>            {registered,[]},
+>            {applications,[kernel,stdlib]},
+>            {env,[]},
+>            {modules,[]}]}.
+>
+> *** and min.erl is:
+>
+> -module(min).
+>
+> -export([hello/0]).
+>
+> hello() ->
+>     io:format("Hello min!~n~n").
+>
+> *** But when I call make, I get this:
+>
+> /min$ make
+>   ERLC   min.erl
+>   APP    min .app.src
+> cat: src/min: No such file or directory
+> cat: .app.src: No such file or directory
+> sed: can't read .app: No such file or directory
+> make: *** [app] Error 2
+>
+> *** Observations
+>
+> min.erl compiles just  fine
+> min.app.src breaks the compile
+>
+> *** Questions:
+>
+> 1) How can I correct this?
+> 2) How can I structure directories and make files for a project that involves several applications?
+>
+> Many thanks,
+>
+> LRP
+>
+>
+> *********************************************
+> My books:
+>
+> THE GOSPEL OF ASHES
+> http://thegospelofashes.com
+>
+> Strength is not enough. Do they have the courage
+> and the cunning? Can they survive long enough to
+> save the lives of millions?
+>
+> FREEIN' PANCHO
+> http://freeinpancho.com
+>
+> A community of misfits help a troubled boy find his way
+>
+> AYA TAKEO
+> http://ayatakeo.com
+>
+> Star-crossed love, war and power in an alternative
+> universe
+>
+> Available through Amazon or by request from your
+> favorite bookstore
+>
+>
+> **********************************************
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> https://lists.ninenines.eu/listinfo/extend
+>
+
+-- 
+============================================================
+Ivan A. Uemlianin PhD
+Llaisdy
+Speech Technology Research and Development
+
+                     ivan at llaisdy.com
+                      www.llaisdy.com
+                          llaisdy.wordpress.com
+               github.com/llaisdy
+                      www.linkedin.com/in/ivanuemlianin
+
+                         festina lente
+============================================================
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000348.html b/_build/static/archives/extend/2014-March/000348.html new file mode 100644 index 00000000..e7140ade --- /dev/null +++ b/_build/static/archives/extend/2014-March/000348.html @@ -0,0 +1,70 @@ + + + + [99s-extend] Trying to grok erlang.mk + + + + + + + + + + +

[99s-extend] Trying to grok erlang.mk

+ Loïc Hoguin + essen at ninenines.eu +
+ Fri Mar 7 17:56:01 CET 2014 +

+
+ +
On 03/06/2014 09:29 PM, lloyd at writersglen.com wrote:
+> PROJECT = min
+
+You probably have an extra space at the end here, and erlang.mk doesn't 
+trim them I guess. Please open a ticket!
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000349.html b/_build/static/archives/extend/2014-March/000349.html new file mode 100644 index 00000000..37895e1d --- /dev/null +++ b/_build/static/archives/extend/2014-March/000349.html @@ -0,0 +1,87 @@ + + + + [99s-extend] Trying to grok erlang.mk + + + + + + + + + + +

[99s-extend] Trying to grok erlang.mk

+ Ivan Uemlianin + ivan at llaisdy.com +
+ Fri Mar 7 17:58:40 CET 2014 +

+
+ +
Yes, that's it!  I've just tried it.
+
+Good old make :)
+
+On 07/03/2014 16:56, Loïc Hoguin wrote:
+> On 03/06/2014 09:29 PM, lloyd at writersglen.com wrote:
+>> PROJECT = min
+>
+> You probably have an extra space at the end here, and erlang.mk doesn't
+> trim them I guess. Please open a ticket!
+>
+
+-- 
+============================================================
+Ivan A. Uemlianin PhD
+Llaisdy
+Speech Technology Research and Development
+
+                     ivan at llaisdy.com
+                      www.llaisdy.com
+                          llaisdy.wordpress.com
+               github.com/llaisdy
+                      www.linkedin.com/in/ivanuemlianin
+
+                         festina lente
+============================================================
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000350.html b/_build/static/archives/extend/2014-March/000350.html new file mode 100644 index 00000000..d257a7e8 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000350.html @@ -0,0 +1,115 @@ + + + + [99s-extend] Getting started error: behaviour cowboy_http_handler undefined + + + + + + + + + + +

[99s-extend] Getting started error: behaviour cowboy_http_handler undefined

+ lloyd at writersglen.com + lloyd at writersglen.com +
+ Mon Mar 10 20:44:27 CET 2014 +

+
+ +
Hello,
+
+I've slavishly emulated the "Getting started" example in the guide: 
+
+http://ninenines.eu/docs/en/cowboy/HEAD/guide/getting_started/
+
+But, when I compile I get this error:
+
+yada yada
+ ERLC   hello_erlang_app.erl hello_handler.erl hello_erlang_sup.erl
+compile: warnings being treated as errors
+src/hello_handler.erl:2: behaviour cowboy_http_handler undefined
+make: *** [ebin/hello_erlang.app] Error 1
+
+Cowboy seems to be correctly loaded and compiled as a dependency. I can see .../cowboy/ebin/cowboy_http_handler.beam
+
+However, when I remove the line -behavior(cowboy_http_handler) from hello_handler.erl, system compiles and creates release just fine.
+
+% -behavior(cowboy_http_handler).
+
+Could this be a bug in Getting started or some dunder-headed thing on my end?
+
+Thanks,
+
+LRP
+
+
+*********************************************
+My books:
+
+THE GOSPEL OF ASHES
+http://thegospelofashes.com
+
+Strength is not enough. Do they have the courage 
+and the cunning? Can they survive long enough to 
+save the lives of millions?  
+
+FREEIN' PANCHO
+http://freeinpancho.com
+
+A community of misfits help a troubled boy find his way 
+
+AYA TAKEO
+http://ayatakeo.com
+
+Star-crossed love, war and power in an alternative 
+universe
+
+Available through Amazon or by request from your 
+favorite bookstore
+
+
+**********************************************
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000351.html b/_build/static/archives/extend/2014-March/000351.html new file mode 100644 index 00000000..ef1f4457 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000351.html @@ -0,0 +1,131 @@ + + + + [99s-extend] Getting started error: behaviour cowboy_http_handler undefined + + + + + + + + + + +

[99s-extend] Getting started error: behaviour cowboy_http_handler undefined

+ Loïc Hoguin + essen at ninenines.eu +
+ Mon Mar 10 21:36:22 CET 2014 +

+
+ +
Try updating Erlang or Cowboy, this isn't the first time this happens 
+and I fixed something at some point.
+
+Also see if you have ERL_LIBS already defined, in which case there might 
+be a bug in Cowboy.
+
+On 03/10/2014 08:44 PM, lloyd at writersglen.com wrote:
+> Hello,
+>
+> I've slavishly emulated the "Getting started" example in the guide:
+>
+> http://ninenines.eu/docs/en/cowboy/HEAD/guide/getting_started/
+>
+> But, when I compile I get this error:
+>
+> yada yada
+>   ERLC   hello_erlang_app.erl hello_handler.erl hello_erlang_sup.erl
+> compile: warnings being treated as errors
+> src/hello_handler.erl:2: behaviour cowboy_http_handler undefined
+> make: *** [ebin/hello_erlang.app] Error 1
+>
+> Cowboy seems to be correctly loaded and compiled as a dependency. I can see .../cowboy/ebin/cowboy_http_handler.beam
+>
+> However, when I remove the line -behavior(cowboy_http_handler) from hello_handler.erl, system compiles and creates release just fine.
+>
+> % -behavior(cowboy_http_handler).
+>
+> Could this be a bug in Getting started or some dunder-headed thing on my end?
+>
+> Thanks,
+>
+> LRP
+>
+>
+> *********************************************
+> My books:
+>
+> THE GOSPEL OF ASHES
+> http://thegospelofashes.com
+>
+> Strength is not enough. Do they have the courage
+> and the cunning? Can they survive long enough to
+> save the lives of millions?
+>
+> FREEIN' PANCHO
+> http://freeinpancho.com
+>
+> A community of misfits help a troubled boy find his way
+>
+> AYA TAKEO
+> http://ayatakeo.com
+>
+> Star-crossed love, war and power in an alternative
+> universe
+>
+> Available through Amazon or by request from your
+> favorite bookstore
+>
+>
+> **********************************************
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> https://lists.ninenines.eu/listinfo/extend
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000352.html b/_build/static/archives/extend/2014-March/000352.html new file mode 100644 index 00000000..bacc9c24 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000352.html @@ -0,0 +1,157 @@ + + + + [99s-extend] Getting started error: behaviour cowboy_http_handler undefined + + + + + + + + + + +

[99s-extend] Getting started error: behaviour cowboy_http_handler undefined

+ lloyd at writersglen.com + lloyd at writersglen.com +
+ Wed Mar 12 23:51:04 CET 2014 +

+
+ +
Hi Loïc,
+
+Thanks for help.
+
+I'm running cowboy master from GitHub and Erlang R16B02.
+
+$ echo $ERL_LIBS
+
+...gives me a directory that no longer exists; don't know how it got there, what it should be, or how to change it.
+
+E.g.: /home/lloyd/Programming/Erlang/zippity/apps
+
+I've looked in .erlang and tried $ export ERL_LIBS=<my path to hello_erlang/ebin>.
+
+Thanks again,
+
+LRP
+
+-----Original Message-----
+From: "Loïc Hoguin" <essen at ninenines.eu>
+Sent: Monday, March 10, 2014 4:36pm
+To: lloyd at writersglen.com, extend at lists.ninenines.eu
+Subject: Re: [99s-extend] Getting started error: behaviour cowboy_http_handler undefined
+
+Try updating Erlang or Cowboy, this isn't the first time this happens 
+and I fixed something at some point.
+
+Also see if you have ERL_LIBS already defined, in which case there might 
+be a bug in Cowboy.
+
+On 03/10/2014 08:44 PM, lloyd at writersglen.com wrote:
+> Hello,
+>
+> I've slavishly emulated the "Getting started" example in the guide:
+>
+> http://ninenines.eu/docs/en/cowboy/HEAD/guide/getting_started/
+>
+> But, when I compile I get this error:
+>
+> yada yada
+>   ERLC   hello_erlang_app.erl hello_handler.erl hello_erlang_sup.erl
+> compile: warnings being treated as errors
+> src/hello_handler.erl:2: behaviour cowboy_http_handler undefined
+> make: *** [ebin/hello_erlang.app] Error 1
+>
+> Cowboy seems to be correctly loaded and compiled as a dependency. I can see .../cowboy/ebin/cowboy_http_handler.beam
+>
+> However, when I remove the line -behavior(cowboy_http_handler) from hello_handler.erl, system compiles and creates release just fine.
+>
+> % -behavior(cowboy_http_handler).
+>
+> Could this be a bug in Getting started or some dunder-headed thing on my end?
+>
+> Thanks,
+>
+> LRP
+>
+>
+> *********************************************
+> My books:
+>
+> THE GOSPEL OF ASHES
+> http://thegospelofashes.com
+>
+> Strength is not enough. Do they have the courage
+> and the cunning? Can they survive long enough to
+> save the lives of millions?
+>
+> FREEIN' PANCHO
+> http://freeinpancho.com
+>
+> A community of misfits help a troubled boy find his way
+>
+> AYA TAKEO
+> http://ayatakeo.com
+>
+> Star-crossed love, war and power in an alternative
+> universe
+>
+> Available through Amazon or by request from your
+> favorite bookstore
+>
+>
+> **********************************************
+>
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> https://lists.ninenines.eu/listinfo/extend
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000353.html b/_build/static/archives/extend/2014-March/000353.html new file mode 100644 index 00000000..da6966ee --- /dev/null +++ b/_build/static/archives/extend/2014-March/000353.html @@ -0,0 +1,159 @@ + + + + [99s-extend] Getting started error: behaviour cowboy_http_handler undefined + + + + + + + + + + +

[99s-extend] Getting started error: behaviour cowboy_http_handler undefined

+ Loïc Hoguin + essen at ninenines.eu +
+ Wed Mar 12 23:57:16 CET 2014 +

+
+ +
Can you try again after running "unset ERL_LIBS"?
+
+On 03/12/2014 11:51 PM, lloyd at writersglen.com wrote:
+> Hi Loïc,
+>
+> Thanks for help.
+>
+> I'm running cowboy master from GitHub and Erlang R16B02.
+>
+> $ echo $ERL_LIBS
+>
+> ...gives me a directory that no longer exists; don't know how it got there, what it should be, or how to change it.
+>
+> E.g.: /home/lloyd/Programming/Erlang/zippity/apps
+>
+> I've looked in .erlang and tried $ export ERL_LIBS=<my path to hello_erlang/ebin>.
+>
+> Thanks again,
+>
+> LRP
+>
+> -----Original Message-----
+> From: "Loïc Hoguin" <essen at ninenines.eu>
+> Sent: Monday, March 10, 2014 4:36pm
+> To: lloyd at writersglen.com, extend at lists.ninenines.eu
+> Subject: Re: [99s-extend] Getting started error: behaviour cowboy_http_handler undefined
+>
+> Try updating Erlang or Cowboy, this isn't the first time this happens
+> and I fixed something at some point.
+>
+> Also see if you have ERL_LIBS already defined, in which case there might
+> be a bug in Cowboy.
+>
+> On 03/10/2014 08:44 PM, lloyd at writersglen.com wrote:
+>> Hello,
+>>
+>> I've slavishly emulated the "Getting started" example in the guide:
+>>
+>> http://ninenines.eu/docs/en/cowboy/HEAD/guide/getting_started/
+>>
+>> But, when I compile I get this error:
+>>
+>> yada yada
+>>    ERLC   hello_erlang_app.erl hello_handler.erl hello_erlang_sup.erl
+>> compile: warnings being treated as errors
+>> src/hello_handler.erl:2: behaviour cowboy_http_handler undefined
+>> make: *** [ebin/hello_erlang.app] Error 1
+>>
+>> Cowboy seems to be correctly loaded and compiled as a dependency. I can see .../cowboy/ebin/cowboy_http_handler.beam
+>>
+>> However, when I remove the line -behavior(cowboy_http_handler) from hello_handler.erl, system compiles and creates release just fine.
+>>
+>> % -behavior(cowboy_http_handler).
+>>
+>> Could this be a bug in Getting started or some dunder-headed thing on my end?
+>>
+>> Thanks,
+>>
+>> LRP
+>>
+>>
+>> *********************************************
+>> My books:
+>>
+>> THE GOSPEL OF ASHES
+>> http://thegospelofashes.com
+>>
+>> Strength is not enough. Do they have the courage
+>> and the cunning? Can they survive long enough to
+>> save the lives of millions?
+>>
+>> FREEIN' PANCHO
+>> http://freeinpancho.com
+>>
+>> A community of misfits help a troubled boy find his way
+>>
+>> AYA TAKEO
+>> http://ayatakeo.com
+>>
+>> Star-crossed love, war and power in an alternative
+>> universe
+>>
+>> Available through Amazon or by request from your
+>> favorite bookstore
+>>
+>>
+>> **********************************************
+>>
+>> _______________________________________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> https://lists.ninenines.eu/listinfo/extend
+>>
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000354.html b/_build/static/archives/extend/2014-March/000354.html new file mode 100644 index 00000000..fad782d1 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000354.html @@ -0,0 +1,180 @@ + + + + [99s-extend] Getting started error: behaviour cowboy_http_handler undefined + + + + + + + + + + +

[99s-extend] Getting started error: behaviour cowboy_http_handler undefined

+ lloyd at writersglen.com + lloyd at writersglen.com +
+ Thu Mar 13 00:43:16 CET 2014 +

+
+ +
Hi,
+
+That fixed it!
+
+But where can I go to understand why and prevent it in future? 
+
+I've googled ERL_LIBS, but not found much enlightenment. Should there possibly be a note in Cowboy docs? Or is this something idiosyncratic to my system?
+
+Many thanks!
+
+Lloyd
+
+-----Original Message-----
+From: "Loïc Hoguin" <essen at ninenines.eu>
+Sent: Wednesday, March 12, 2014 6:57pm
+To: lloyd at writersglen.com
+Cc: extend at lists.ninenines.eu
+Subject: Re: [99s-extend] Getting started error: behaviour cowboy_http_handler undefined
+
+Can you try again after running "unset ERL_LIBS"?
+
+On 03/12/2014 11:51 PM, lloyd at writersglen.com wrote:
+> Hi Loïc,
+>
+> Thanks for help.
+>
+> I'm running cowboy master from GitHub and Erlang R16B02.
+>
+> $ echo $ERL_LIBS
+>
+> ...gives me a directory that no longer exists; don't know how it got there, what it should be, or how to change it.
+>
+> E.g.: /home/lloyd/Programming/Erlang/zippity/apps
+>
+> I've looked in .erlang and tried $ export ERL_LIBS=<my path to hello_erlang/ebin>.
+>
+> Thanks again,
+>
+> LRP
+>
+> -----Original Message-----
+> From: "Loïc Hoguin" <essen at ninenines.eu>
+> Sent: Monday, March 10, 2014 4:36pm
+> To: lloyd at writersglen.com, extend at lists.ninenines.eu
+> Subject: Re: [99s-extend] Getting started error: behaviour cowboy_http_handler undefined
+>
+> Try updating Erlang or Cowboy, this isn't the first time this happens
+> and I fixed something at some point.
+>
+> Also see if you have ERL_LIBS already defined, in which case there might
+> be a bug in Cowboy.
+>
+> On 03/10/2014 08:44 PM, lloyd at writersglen.com wrote:
+>> Hello,
+>>
+>> I've slavishly emulated the "Getting started" example in the guide:
+>>
+>> http://ninenines.eu/docs/en/cowboy/HEAD/guide/getting_started/
+>>
+>> But, when I compile I get this error:
+>>
+>> yada yada
+>>    ERLC   hello_erlang_app.erl hello_handler.erl hello_erlang_sup.erl
+>> compile: warnings being treated as errors
+>> src/hello_handler.erl:2: behaviour cowboy_http_handler undefined
+>> make: *** [ebin/hello_erlang.app] Error 1
+>>
+>> Cowboy seems to be correctly loaded and compiled as a dependency. I can see .../cowboy/ebin/cowboy_http_handler.beam
+>>
+>> However, when I remove the line -behavior(cowboy_http_handler) from hello_handler.erl, system compiles and creates release just fine.
+>>
+>> % -behavior(cowboy_http_handler).
+>>
+>> Could this be a bug in Getting started or some dunder-headed thing on my end?
+>>
+>> Thanks,
+>>
+>> LRP
+>>
+>>
+>> *********************************************
+>> My books:
+>>
+>> THE GOSPEL OF ASHES
+>> http://thegospelofashes.com
+>>
+>> Strength is not enough. Do they have the courage
+>> and the cunning? Can they survive long enough to
+>> save the lives of millions?
+>>
+>> FREEIN' PANCHO
+>> http://freeinpancho.com
+>>
+>> A community of misfits help a troubled boy find his way
+>>
+>> AYA TAKEO
+>> http://ayatakeo.com
+>>
+>> Star-crossed love, war and power in an alternative
+>> universe
+>>
+>> Available through Amazon or by request from your
+>> favorite bookstore
+>>
+>>
+>> **********************************************
+>>
+>> _______________________________________________
+>> Extend mailing list
+>> Extend at lists.ninenines.eu
+>> https://lists.ninenines.eu/listinfo/extend
+>>
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000355.html b/_build/static/archives/extend/2014-March/000355.html new file mode 100644 index 00000000..819e76e1 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000355.html @@ -0,0 +1,186 @@ + + + + [99s-extend] Getting started error: behaviour cowboy_http_handler undefined + + + + + + + + + + +

[99s-extend] Getting started error: behaviour cowboy_http_handler undefined

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Mar 13 00:46:57 CET 2014 +

+
+ +
It's explained here: http://www.erlang.org/doc/man/code.html
+
+I am not sure why it caused issues on your system, possibly Erlang 
+ignored it because there was an invalid folder in there. I don't really 
+know.
+
+On 03/13/2014 12:43 AM, lloyd at writersglen.com wrote:
+> Hi,
+>
+> That fixed it!
+>
+> But where can I go to understand why and prevent it in future?
+>
+> I've googled ERL_LIBS, but not found much enlightenment. Should there possibly be a note in Cowboy docs? Or is this something idiosyncratic to my system?
+>
+> Many thanks!
+>
+> Lloyd
+>
+> -----Original Message-----
+> From: "Loïc Hoguin" <essen at ninenines.eu>
+> Sent: Wednesday, March 12, 2014 6:57pm
+> To: lloyd at writersglen.com
+> Cc: extend at lists.ninenines.eu
+> Subject: Re: [99s-extend] Getting started error: behaviour cowboy_http_handler undefined
+>
+> Can you try again after running "unset ERL_LIBS"?
+>
+> On 03/12/2014 11:51 PM, lloyd at writersglen.com wrote:
+>> Hi Loïc,
+>>
+>> Thanks for help.
+>>
+>> I'm running cowboy master from GitHub and Erlang R16B02.
+>>
+>> $ echo $ERL_LIBS
+>>
+>> ...gives me a directory that no longer exists; don't know how it got there, what it should be, or how to change it.
+>>
+>> E.g.: /home/lloyd/Programming/Erlang/zippity/apps
+>>
+>> I've looked in .erlang and tried $ export ERL_LIBS=<my path to hello_erlang/ebin>.
+>>
+>> Thanks again,
+>>
+>> LRP
+>>
+>> -----Original Message-----
+>> From: "Loïc Hoguin" <essen at ninenines.eu>
+>> Sent: Monday, March 10, 2014 4:36pm
+>> To: lloyd at writersglen.com, extend at lists.ninenines.eu
+>> Subject: Re: [99s-extend] Getting started error: behaviour cowboy_http_handler undefined
+>>
+>> Try updating Erlang or Cowboy, this isn't the first time this happens
+>> and I fixed something at some point.
+>>
+>> Also see if you have ERL_LIBS already defined, in which case there might
+>> be a bug in Cowboy.
+>>
+>> On 03/10/2014 08:44 PM, lloyd at writersglen.com wrote:
+>>> Hello,
+>>>
+>>> I've slavishly emulated the "Getting started" example in the guide:
+>>>
+>>> http://ninenines.eu/docs/en/cowboy/HEAD/guide/getting_started/
+>>>
+>>> But, when I compile I get this error:
+>>>
+>>> yada yada
+>>>     ERLC   hello_erlang_app.erl hello_handler.erl hello_erlang_sup.erl
+>>> compile: warnings being treated as errors
+>>> src/hello_handler.erl:2: behaviour cowboy_http_handler undefined
+>>> make: *** [ebin/hello_erlang.app] Error 1
+>>>
+>>> Cowboy seems to be correctly loaded and compiled as a dependency. I can see .../cowboy/ebin/cowboy_http_handler.beam
+>>>
+>>> However, when I remove the line -behavior(cowboy_http_handler) from hello_handler.erl, system compiles and creates release just fine.
+>>>
+>>> % -behavior(cowboy_http_handler).
+>>>
+>>> Could this be a bug in Getting started or some dunder-headed thing on my end?
+>>>
+>>> Thanks,
+>>>
+>>> LRP
+>>>
+>>>
+>>> *********************************************
+>>> My books:
+>>>
+>>> THE GOSPEL OF ASHES
+>>> http://thegospelofashes.com
+>>>
+>>> Strength is not enough. Do they have the courage
+>>> and the cunning? Can they survive long enough to
+>>> save the lives of millions?
+>>>
+>>> FREEIN' PANCHO
+>>> http://freeinpancho.com
+>>>
+>>> A community of misfits help a troubled boy find his way
+>>>
+>>> AYA TAKEO
+>>> http://ayatakeo.com
+>>>
+>>> Star-crossed love, war and power in an alternative
+>>> universe
+>>>
+>>> Available through Amazon or by request from your
+>>> favorite bookstore
+>>>
+>>>
+>>> **********************************************
+>>>
+>>> _______________________________________________
+>>> Extend mailing list
+>>> Extend at lists.ninenines.eu
+>>> https://lists.ninenines.eu/listinfo/extend
+>>>
+>>
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000356.html b/_build/static/archives/extend/2014-March/000356.html new file mode 100644 index 00000000..a1742223 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000356.html @@ -0,0 +1,96 @@ + + + + [99s-extend] Updating Cowboy applications + + + + + + + + + + +

[99s-extend] Updating Cowboy applications

+ Joshua McQuistan + joshua.mcquistan at mcq.io +
+ Thu Mar 13 02:41:12 CET 2014 +

+
+ +
Hello all,
+
+I have written a Cowboy application that works fine over localhost. I'm
+now looking at ways of deploying and updating it i.e., moving from dev
+to prod in a nice manner.
+
+I have dug around the archives and have found that Cowboy does not
+support hot code reloading meaning either a restart of the vm or playing
+with code:reload_file is necessary.
+
+The latter suggests a possible rewriting of OTP's code loading mechanism
+and seems like it might be sensible to avoid.
+
+The other approach then is a restart. In previous (non-Cowboy) set ups
+I've used nginx on port 80 / 443 that talks to the web app via a unix
+socket (e.g., "web/socket"). When updating I'll start a new instance on
+a new socket (e.g., "web/socket.new") then rely on the file system's
+"mv" to switch it to "web/socket"; this works because the underlying
+file system guarantees mv to be atomic (or at least to never see a
+missing file). I can then ask the old process to shut down nicely in the
+background.
+
+For this to work it would require Cowby / Ranch to be able to listen on
+unix sockets. A glance at the documentation suggests that unix sockets
+aren't available, is this the case? What's the feasibility of it getting
+added?
+
+It might just be simpler to load-balance across multiple servers and
+safely take them out one at a time while updating.
+
+My other question is, how do others approach this problem? Did I miss
+something vitally obvious?
+
+Regards,
+Joshua
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000357.html b/_build/static/archives/extend/2014-March/000357.html new file mode 100644 index 00000000..da65a33e --- /dev/null +++ b/_build/static/archives/extend/2014-March/000357.html @@ -0,0 +1,125 @@ + + + + [99s-extend] Updating Cowboy applications + + + + + + + + + + +

[99s-extend] Updating Cowboy applications

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Mar 13 14:22:03 CET 2014 +

+
+ +
Deploying is easy: releases.
+
+The "getting started" chapter of the guide, and all the examples use 
+that and it should be pretty easy to do.
+
+You can reload Cowboy modules directly using l(module). You can reload 
+most Ranch modules too but some of them will require using sys. Ranch 
+will get support for upgrades as soon as I finish the upgrade test 
+suite, but it's still low priority.
+
+And upgrade of Cowboy processes can only be added after we make them 
+special processes, which is still a way to go.
+
+There is no plans for supporting unix sockets for the simple reason that 
+it is not portable. On the other hand, if you use a separate library to 
+open a socket and give it to Ranch (socket option), possibly writing a 
+specific transport module for it, then it's very possible that you can 
+use unix sockets (and if it works, please do send feedback).
+
+On 03/13/2014 02:41 AM, Joshua McQuistan wrote:
+> Hello all,
+>
+> I have written a Cowboy application that works fine over localhost. I'm
+> now looking at ways of deploying and updating it i.e., moving from dev
+> to prod in a nice manner.
+>
+> I have dug around the archives and have found that Cowboy does not
+> support hot code reloading meaning either a restart of the vm or playing
+> with code:reload_file is necessary.
+>
+> The latter suggests a possible rewriting of OTP's code loading mechanism
+> and seems like it might be sensible to avoid.
+>
+> The other approach then is a restart. In previous (non-Cowboy) set ups
+> I've used nginx on port 80 / 443 that talks to the web app via a unix
+> socket (e.g., "web/socket"). When updating I'll start a new instance on
+> a new socket (e.g., "web/socket.new") then rely on the file system's
+> "mv" to switch it to "web/socket"; this works because the underlying
+> file system guarantees mv to be atomic (or at least to never see a
+> missing file). I can then ask the old process to shut down nicely in the
+> background.
+>
+> For this to work it would require Cowby / Ranch to be able to listen on
+> unix sockets. A glance at the documentation suggests that unix sockets
+> aren't available, is this the case? What's the feasibility of it getting
+> added?
+>
+> It might just be simpler to load-balance across multiple servers and
+> safely take them out one at a time while updating.
+>
+> My other question is, how do others approach this problem? Did I miss
+> something vitally obvious?
+>
+> Regards,
+> Joshua
+> _______________________________________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> https://lists.ninenines.eu/listinfo/extend
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000358.html b/_build/static/archives/extend/2014-March/000358.html new file mode 100644 index 00000000..7c7f0abe --- /dev/null +++ b/_build/static/archives/extend/2014-March/000358.html @@ -0,0 +1,78 @@ + + + + [99s-extend] Updating Cowboy applications + + + + + + + + + + +

[99s-extend] Updating Cowboy applications

+ Joshua McQuistan + joshua.mcquistan at mcq.io +
+ Thu Mar 13 15:23:09 CET 2014 +

+
+ +
> 
+> I wish I knew enough to answer your question. But I do hope you publish a tutorial documenting your solution for those following you down the trail.
+
+Will do.
+
+On 13/03/14 13:22, Loïc Hoguin wrote:
+> 
+> There is no plans for supporting unix sockets for the simple reason that
+> it is not portable. On the other hand, if you use a separate library to
+> open a socket and give it to Ranch (socket option), possibly writing a
+> specific transport module for it, then it's very possible that you can
+> use unix sockets (and if it works, please do send feedback).
+
+I had missed this last night, I will try passing the socket down and see
+if it works.
+
+I can also see the gen_tcp:listen in ranch_tcp but I'd prefer to avoid that.
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000359.html b/_build/static/archives/extend/2014-March/000359.html new file mode 100644 index 00000000..1ce4d916 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000359.html @@ -0,0 +1,76 @@ + + + + [99s-extend] Cowboy unexpectedly timing out when reading the body + + + + + + + + + + +

[99s-extend] Cowboy unexpectedly timing out when reading the body

+ Phillips, Christopher + Christopher.Phillips at turner.com +
+ Fri Mar 14 19:52:07 CET 2014 +

+
+ +
On a dev server I had a Cowboy app suddenly start returning timeouts when calling cowboy_req:body_qs(Request), with surprising frequency, which in turn led to 500s back to the calling client. It only appeared to happen when hitting one particular resource, and was sporadic, and I was wondering if there might be some explanation related to Cowboy (as opposed to maybe really weird VM issues). For full disclosure, we would first check the body with cowboy_req:body(Request) as part of an access log, then ignore the returned cowboy_req:req() that call passed back, since we could not then stream the body off of it again. It was working fine, so I don't think it was related, but it seems more solid now after I removed it and I don't know if that's related or not.
+
+
+
+Here is an example request that dumped when the process died -
+
+
+{req,[{socket,#Port<0.7113>},{transport,ranch_tcp},{connection,keepalive},{pid,<0.1805.0>},{method,<<"POST">>},{version,'HTTP/1.1'},{peer,{{10,188,32,225},53188}},{host,<<"bps-feedschedulervip1.turner.com">>},{host_info,undefined},{port,8091},{path,<<"/encoders/Player1/record">>},{path_info,[<<"record">>]},{qs,<<"authToken=...">>},{qs_vals,[{<<"authToken">>,<<"...">>}]},{bindings,[{id,<<"Player1">>}]},{headers,[{<<"host">>,<<"bps-feedschedulervip1.turner.com:8091">>},{<<"content-type">>,<<"application/x-www-form-urlencoded; charset=UTF-8">>},{<<"origin">>,<<"http://bps-newstrondev1.turner.com">>},{<<"content-length">>,<<"48">>},{<<"connection">>,<<"keep-alive">>},{<<"accept">>,<<"application/json, text/javascript, */*; q=0.01">>},{<<"user-agent">>,<<"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.74.9 (KHTML, like Gecko) Version/7.0.2 Safari/537.74.9">>},{<<"referer">>,<<"http://bps-newstrondev1.turner.com/newstron/record/record.html">>},{<<"accept-language">>,<<"en-us">>},{<<"accept-encoding">>,<<"gzip, deflate">>}]},{p_headers,[{<<"content-type">>,{<<"application">>,<<"x-www-form-urlencoded">>,[{<<"charset">>,<<"utf-8">>}]}},{<<"if-modified-since">>,undefined},{<<"if-none-match">>,undefined},{<<"if-unmodified-since">>,undefined},{<<"if-match">>,undefined},{<<"accept">>,[{{<<"application">>,<<"json">>,[]},1000,[]},{{<<"text">>,<<"javascript">>,[]},1000,[]},{{<<"*">>,<<"*">>,[]},10,[]}]},{<<"connection">>,[<<"keep-alive">>]}]},{cookies,undefined},{meta,[{charset,undefined},{media_type,{<<"application">>,<<"json">>,[]}}]},{body_state,waiting},{multipart,undefined},{buffer,<<>>},{resp_compress,false},{resp_state,waiting},{resp_headers,[{<<"content-type">>,[<<"application">>,<<"/">>,<<"json">>,<<>>]},{<<"Access-Control-Allow-Origin">>,<<"*">>}]},{resp_body,<<>>},{onresponse,#Fun<access_log_responder.onresponse.4>}]}
+
+
+
+
+As I said, it may be just due to VM issues or something, but I figured I'd ask in case there was any obvious issue.
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20140314/b2f802d3/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000360.html b/_build/static/archives/extend/2014-March/000360.html new file mode 100644 index 00000000..24c59e1b --- /dev/null +++ b/_build/static/archives/extend/2014-March/000360.html @@ -0,0 +1,80 @@ + + + + [99s-extend] Cowboy unexpectedly timing out when reading the body + + + + + + + + + + +

[99s-extend] Cowboy unexpectedly timing out when reading the body

+ Loïc Hoguin + essen at ninenines.eu +
+ Fri Mar 14 19:56:38 CET 2014 +

+
+ +
Cowboy does have a timeout too small, that will be fixed soon (by making 
+it configurable, per body-reading call). It will be in the next release.
+
+On the other hand there's something weird in what you said.
+
+On 03/14/2014 07:52 PM, Phillips, Christopher wrote:
+> first check the body with cowboy_req:body(Request) as part of an access
+> log, then ignore the returned cowboy_req:req() that call passed back,
+> since we could not then stream the body off of it again. It was working
+> fine, so I don't think it was related, but it seems more solid now after
+> I removed it and I don't know if that's related or not.
+
+If you ignore the Req being returned, especially after a body-reading 
+call, then Cowboy will not be able to figure out that you actually read 
+it, and will attempt to read it again to skip it, leading to issues.
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000361.html b/_build/static/archives/extend/2014-March/000361.html new file mode 100644 index 00000000..0140723a --- /dev/null +++ b/_build/static/archives/extend/2014-March/000361.html @@ -0,0 +1,95 @@ + + + + [99s-extend] Cowboy unexpectedly timing out when reading the body + + + + + + + + + + +

[99s-extend] Cowboy unexpectedly timing out when reading the body

+ Phillips, Christopher + Christopher.Phillips at turner.com +
+ Fri Mar 14 20:07:40 CET 2014 +

+
+ +
  This body is -small-. 48 bytes was my test data (per the
+content-length). That shouldn't take 5 seconds to read, and usually it
+took a millisecond or two, and returned to the client (despite actually
+controlling some hardware across a network and such) within a second. And
+it was ND; I tested this thing a couple of times locally and it appeared
+to work, and even deployed onto a VM it worked some of the time (as I
+said, might have been hardware or some other weirdness).
+
+  So can we only read the body once? Or what's the right approach if I
+want to access the body in both a module registered to the
+onrequest/onresponse callbacks, and in the REST handler?
+
+On 3/14/14, 2:56 PM, "Loïc Hoguin" <essen at ninenines.eu> wrote:
+
+>Cowboy does have a timeout too small, that will be fixed soon (by making
+>it configurable, per body-reading call). It will be in the next release.
+>
+>On the other hand there's something weird in what you said.
+>
+>On 03/14/2014 07:52 PM, Phillips, Christopher wrote:
+>> first check the body with cowboy_req:body(Request) as part of an access
+>> log, then ignore the returned cowboy_req:req() that call passed back,
+>> since we could not then stream the body off of it again. It was working
+>> fine, so I don't think it was related, but it seems more solid now after
+>> I removed it and I don't know if that's related or not.
+>
+>If you ignore the Req being returned, especially after a body-reading
+>call, then Cowboy will not be able to figure out that you actually read
+>it, and will attempt to read it again to skip it, leading to issues.
+>
+>-- 
+>Loïc Hoguin
+>http://ninenines.eu
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000362.html b/_build/static/archives/extend/2014-March/000362.html new file mode 100644 index 00000000..07e318d1 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000362.html @@ -0,0 +1,106 @@ + + + + [99s-extend] Cowboy unexpectedly timing out when reading the body + + + + + + + + + + +

[99s-extend] Cowboy unexpectedly timing out when reading the body

+ Loïc Hoguin + essen at ninenines.eu +
+ Fri Mar 14 20:11:27 CET 2014 +

+
+ +
Yep, only once. All functions that return {ok, ...} are like this. 
+There's no right approach, that's left as an exercise to the developer. :-)
+
+You can probably use cowboy_req:set_meta/meta if you really need to pass 
+it around.
+
+On 03/14/2014 08:07 PM, Phillips, Christopher wrote:
+>    This body is -small-. 48 bytes was my test data (per the
+> content-length). That shouldn't take 5 seconds to read, and usually it
+> took a millisecond or two, and returned to the client (despite actually
+> controlling some hardware across a network and such) within a second. And
+> it was ND; I tested this thing a couple of times locally and it appeared
+> to work, and even deployed onto a VM it worked some of the time (as I
+> said, might have been hardware or some other weirdness).
+>
+>    So can we only read the body once? Or what's the right approach if I
+> want to access the body in both a module registered to the
+> onrequest/onresponse callbacks, and in the REST handler?
+>
+> On 3/14/14, 2:56 PM, "Loïc Hoguin" <essen at ninenines.eu> wrote:
+>
+>> Cowboy does have a timeout too small, that will be fixed soon (by making
+>> it configurable, per body-reading call). It will be in the next release.
+>>
+>> On the other hand there's something weird in what you said.
+>>
+>> On 03/14/2014 07:52 PM, Phillips, Christopher wrote:
+>>> first check the body with cowboy_req:body(Request) as part of an access
+>>> log, then ignore the returned cowboy_req:req() that call passed back,
+>>> since we could not then stream the body off of it again. It was working
+>>> fine, so I don't think it was related, but it seems more solid now after
+>>> I removed it and I don't know if that's related or not.
+>>
+>> If you ignore the Req being returned, especially after a body-reading
+>> call, then Cowboy will not be able to figure out that you actually read
+>> it, and will attempt to read it again to skip it, leading to issues.
+>>
+>> --
+>> Loïc Hoguin
+>> http://ninenines.eu
+>
+
+-- 
+Loïc Hoguin
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/000363.html b/_build/static/archives/extend/2014-March/000363.html new file mode 100644 index 00000000..f9141c42 --- /dev/null +++ b/_build/static/archives/extend/2014-March/000363.html @@ -0,0 +1,116 @@ + + + + [99s-extend] Cowboy unexpectedly timing out when reading the body + + + + + + + + + + +

[99s-extend] Cowboy unexpectedly timing out when reading the body

+ Phillips, Christopher + Christopher.Phillips at turner.com +
+ Fri Mar 14 20:13:31 CET 2014 +

+
+ +
  Hmm, okay. Thanks Loic.
+
+On 3/14/14, 3:11 PM, "Loïc Hoguin" <essen at ninenines.eu> wrote:
+
+>Yep, only once. All functions that return {ok, ...} are like this.
+>There's no right approach, that's left as an exercise to the developer.
+>:-)
+>
+>You can probably use cowboy_req:set_meta/meta if you really need to pass
+>it around.
+>
+>On 03/14/2014 08:07 PM, Phillips, Christopher wrote:
+>>    This body is -small-. 48 bytes was my test data (per the
+>> content-length). That shouldn't take 5 seconds to read, and usually it
+>> took a millisecond or two, and returned to the client (despite actually
+>> controlling some hardware across a network and such) within a second.
+>>And
+>> it was ND; I tested this thing a couple of times locally and it appeared
+>> to work, and even deployed onto a VM it worked some of the time (as I
+>> said, might have been hardware or some other weirdness).
+>>
+>>    So can we only read the body once? Or what's the right approach if I
+>> want to access the body in both a module registered to the
+>> onrequest/onresponse callbacks, and in the REST handler?
+>>
+>> On 3/14/14, 2:56 PM, "Loïc Hoguin" <essen at ninenines.eu> wrote:
+>>
+>>> Cowboy does have a timeout too small, that will be fixed soon (by
+>>>making
+>>> it configurable, per body-reading call). It will be in the next
+>>>release.
+>>>
+>>> On the other hand there's something weird in what you said.
+>>>
+>>> On 03/14/2014 07:52 PM, Phillips, Christopher wrote:
+>>>> first check the body with cowboy_req:body(Request) as part of an
+>>>>access
+>>>> log, then ignore the returned cowboy_req:req() that call passed back,
+>>>> since we could not then stream the body off of it again. It was
+>>>>working
+>>>> fine, so I don't think it was related, but it seems more solid now
+>>>>after
+>>>> I removed it and I don't know if that's related or not.
+>>>
+>>> If you ignore the Req being returned, especially after a body-reading
+>>> call, then Cowboy will not be able to figure out that you actually read
+>>> it, and will attempt to read it again to skip it, leading to issues.
+>>>
+>>> --
+>>> Loïc Hoguin
+>>> http://ninenines.eu
+>>
+>
+>-- 
+>Loïc Hoguin
+>http://ninenines.eu
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/_build/static/archives/extend/2014-March/author.html b/_build/static/archives/extend/2014-March/author.html new file mode 100644 index 00000000..b935d6a0 --- /dev/null +++ b/_build/static/archives/extend/2014-March/author.html @@ -0,0 +1,167 @@ + + + + The Extend March 2014 Archive by author + + + + + +

March 2014 Archives by author

+ +

Starting: Mon Mar 3 21:49:33 CET 2014
+ Ending: Fri Mar 14 20:13:31 CET 2014
+ Messages: 24

+

+

+ Last message date: + Fri Mar 14 20:13:31 CET 2014
+ Archived on: Wed May 28 18:41:47 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/_build/static/archives/extend/2014-March/date.html b/_build/static/archives/extend/2014-March/date.html new file mode 100644 index 00000000..07c935eb --- /dev/null +++ b/_build/static/archives/extend/2014-March/date.html @@ -0,0 +1,167 @@ + + + + The Extend March 2014 Archive by date + + + + + +

March 2014 Archives by date

+ +

Starting: Mon Mar 3 21:49:33 CET 2014
+ Ending: Fri Mar 14 20:13:31 CET 2014
+ Messages: 24

+

+

+ Last message date: + Fri Mar 14 20:13:31 CET 2014
+ Archived on: Wed May 28 18:41:47 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/_build/static/archives/extend/2014-March/index.html b/_build/static/archives/extend/2014-March/index.html new file mode 120000 index 00000000..db4b46f7 --- /dev/null +++ b/_build/static/archives/extend/2014-March/index.html @@ -0,0 +1 @@ +thread.html \ No newline at end of file diff --git a/_build/static/archives/extend/2014-March/subject.html b/_build/static/archives/extend/2014-March/subject.html new file mode 100644 index 00000000..a8173ef7 --- /dev/null +++ b/_build/static/archives/extend/2014-March/subject.html @@ -0,0 +1,167 @@ + + + + The Extend March 2014 Archive by subject + + + + + +

March 2014 Archives by subject

+ +

Starting: Mon Mar 3 21:49:33 CET 2014
+ Ending: Fri Mar 14 20:13:31 CET 2014
+ Messages: 24

+

+

+ Last message date: + Fri Mar 14 20:13:31 CET 2014
+ Archived on: Wed May 28 18:41:47 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/_build/static/archives/extend/2014-March/thread.html b/_build/static/archives/extend/2014-March/thread.html new file mode 100644 index 00000000..d9b001cf --- /dev/null +++ b/_build/static/archives/extend/2014-March/thread.html @@ -0,0 +1,219 @@ + + + + The Extend March 2014 Archive by thread + + + + + +

March 2014 Archives by thread

+ +

Starting: Mon Mar 3 21:49:33 CET 2014
+ Ending: Fri Mar 14 20:13:31 CET 2014
+ Messages: 24

+

+

+ Last message date: + Fri Mar 14 20:13:31 CET 2014
+ Archived on: Wed May 28 18:41:47 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.3