Don't worry if I am sounding a bit condescending in some parts of this
On 07/12/2012 12:30 AM, Ian wrote:
> On 11/07/2012 11:47, Thomas Lindgren wrote:I'll make sure to add instructions about that in the upcoming Cowboy
>> 1. Too few dedicated erlang web programmers, so still a lot of DIY.
>> This may be a bootstrapping/community issue. Which is nontrivial, by
>> the way.
>> 2. Packages: Let me gripe a bit. At work, we've had endless trouble
> 1) Found cowboy needs rebar - and rebar documentation is
> 2) Find rebar is not available on windows. OK. I'll upgrade a VM I haveCowboy isn't available on Windows either, AFAIK. None of my software has
> to Unbuntu 12:04. (which takes 3 hours, fails and needs nursing back to
> health. After removing and re-installing some packages things are now
> OK, apart from the occasional crash. Aside - virtual box provides a
> rather standard environment, so should not be a problem. And I though
> Linux was supposed not to crash like Windows. Not my experience. Oh
> well - press on.
been tested properly on Windows (or at least I didn't get feedback about
it). I think few open-source Erlang developers use Windows and unless
they send patches or finance some work towards this it's going to
improve very slowly. Not trying to make an apology of it, just
explaining the whys.
> 3) I discover that the install of rebar into an apt-get install ofThat's because Debian and Ubuntu's Erlang packages is completely broken.
> Erlang will cause all sort of problems.
> In my book that means that at least one of those installs is not simple
Can't really blame Erlang for that.
> 4) Screw up courage and download and compile Erlang 15B - all goesAs you noticed it's much easier from source. There's also Ubuntu
> well. Woo-Hoo on a roll here!
packages provided by Erlang Solutions, or tool assisted source install
using kerl. But these are all third party.
> 5) Download, and compile rebar from source. That appears to work and itI'll definitely sound condescending with this one, but this is an honest
> tells me to put it on the path.
> 6) Eh? Type "path" - gets "not installed" error message. Back to Google.
question. Why do you not know about the PATH environment variable?
That's generally useful in any kind of development work. Should this
also be included in the various projects' documentation?
> Which should I use? Will the next upgrade to Ubuntu wipe some of them?Don't think I knew about that one. There's probably various other
> Don't know. Don't know how to find out. Look in each one and decide that
> /usr/local/bin is probably a fair choice, because it contains erl. Copy
> rebar in.
> 7) Now I can start the instructions at
> Note the title includes the sales pitch "In 5 minutes". I have already
tutorials here and there not explaining everything properly. I'm open to
suggestions for the steps you feel are needed to be put in the
I doubt you can go from 0 knowledge to running Cowboy application in 5
Anyway Cowboy lacks proper user guides because the API is just about to
> 8) Issue first command and find hg is not an installed command. Apt-getAll these steps are about that third party tool, which hasn't been
> install hg can't find the package.
> It wasn't the start position! Google turns up that hg is actually
> 9) hg installs and I get to clone woody from bitbucket. Step 1 complete.
> 10) Next command is ./app.sh cowgirl . I think that create the app (or
> 11) Then ./build-compile.sh - OK, build and compile. NO errors. Great.
> 12) Next comes ./build-release.sh
> This fails saying files exist and were not generated. It adds that I
> 13) When I do I get this.
> ian@anake:~/projects/cowgirl$ ./build-release.sh force=1
> This is copy/pasted from the log, so I can see I did indeed spell force
updated in a long time, and the rebar you use is probably too recent for
it. Things still change a lot in both rebar and Cowboy so it's not
surprising to see old guides stop working here and there.
> Where now? Is the pre-existence of those files a problem? I have noThat tool is building a release. Do you know what a release is? It's one
> idea, and no idea how to find out. However experience tells me to make a
> real effort to fix the first error, even if later ones can be ignored.
> Should I delete them all and try again?
> What does the error in the generate mean? It can't mean the application
of the most advanced topic in Erlang/OTP, a lot of Erlang developers
never used releases. That guide/tool is clearly not something useful for
> The talk is right. Erlang is just too damn difficult to do the easy stuff.The problem you point out is general lack of good user guides. Erlang's
community has many experts writing amazing software, some of it open
source, but most of them do not have the time or skill to properly write
good documentation. Writing good documentation is a work on its own and
few developers are good at it. On the other hand, these experts are
generally here on the mailing list or on IRC where they can provide
quick help to solve specific problems. (And don't look at me, I'm no
> It may have been humorously presented (I wasn't there), but theEasiest way to start is to clone the cowboy_examples repository and play
> take-away it so true.
> Early difficulties are putting off many would-be adopters.
> (And I'm stuck! Help appreciated! )
around with the existing code: https://github.com/extend/cowboy_examples
I've started rewriting examples with one proper application per example
Hope this helps.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.