| Author |
Message |
< Erlyweb mailing list ~ Beginner Question - How to install ErlyWeb |
| Guest |
 Posted: Tue Dec 18, 2007 7:01 pm |
 |
|
|
Guest
|
Yariv and other gurus,
Assuming that Erlang and Yaws are correctly installed and configured:
After unzipping the erlyweb-0.6.2.zip file, I see that there are beam
files under ebin, but there are also makefiles. Does anything need to
be compiled or can the beam files just be put somewhere? I seem to
remember that the 0.2 version came with bundles. What's changed these
days and are there any gotchyas to look out for?
This is the section that I have previously failed at a couple of
times, so expect me to need lots of help to get this bit right and
explained well. Thanks.
Oh, and is there an ETA on the 0.7 release? Will there be many
differences to allow for in the documentation?
Simon
--
simonpeter.org | simonpeter.com | newlife-upc.org | wisconsindistrictnews.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| ketralnis |
| Posted: Tue Dec 18, 2007 7:26 pm |
|
|
|
User
Joined: 20 Jul 2007
Posts: 151
Location: San Francisco, CA
|
> Assuming that Erlang and Yaws are correctly installed and configured:
> After unzipping the erlyweb-0.6.2.zip file, I see that there are beam
> files under ebin, but there are also makefiles. Does anything need to
> be compiled or can the beam files just be put somewhere?
The .beam files will probably just work as is. I have a lib/ directory
in my project root (that's an svn:externals entry, in my case), like
this (some extra files listed to get your bearings):
start.sh
ebin/*.beam (my beams)
src/*.erl (my source)
src/components/*.{et,erl}
www/style.css
lib/erlyweb/Makefile
lib/erlyweb/ebin/*.beam (the pre-included beams)
lib/erlyweb/src/...
Then I launch erl (or yaws) with start.sh that contains (more or less):
--------
#!/bin/sh
APPDIR=`pwd`
FULLPA="-pa $APPDIR -pa $APPDIR/ebin -pa $APPDIR/lib/erlyweb/ebin"
erl $FULLPA
--------
If you plan to re-compile the beam files (for instance, because you
have Erlang R12B that has a better compiler for the things that
erlyweb does, like returning largely pre-formed IOlists), then you'll
need to modify (in the structure above) lib/erlyweb/Emakefile and
change the first line:
{"src/erlyweb/*", [debug_info, {outdir, "ebin"}, {i,"/opt/local/lib/
yaws/include"}]}.
Change "/opt/local/lib/yaws/include" to the path to your yaws include
files (that's the path for a MacPorts install that you won't have to
change if you're on a Mac and installed Yaws from MacPorts), then do
"make" in lib/erlyweb/. You may need to remove all of the pre-included
beams in lib/erlyweb/ebin/ to force it to re-compile if it doesn't
already.
At least that's what I do. You may choose to set it up differently.
> I seem to
> remember that the 0.2 version came with bundles. What's changed these
> days and are there any gotchyas to look out for?
>
> This is the section that I have previously failed at a couple of
> times, so expect me to need lots of help to get this bit right and
> explained well. Thanks.
>
> Oh, and is there an ETA on the 0.7 release? Will there be many
> differences to allow for in the documentation?
>
> Simon
>
> --
> simonpeter.org | simonpeter.com | newlife-upc.org |
> wisconsindistrictnews.org
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
  
|
| Guest |
| Posted: Tue Dec 18, 2007 11:47 pm |
|
|
|
Guest
|
On Dec 18, 2007 1:25 PM, David King <dking@ketralnis.com> wrote:
>
> > Assuming that Erlang and Yaws are correctly installed and configured:
> > After unzipping the erlyweb-0.6.2.zip file, I see that there are beam
> > files under ebin, but there are also makefiles. Does anything need to
> > be compiled or can the beam files just be put somewhere?
>
> The .beam files will probably just work as is. I have a lib/ directory
> in my project root (that's an svn:externals entry, in my case), like
> this (some extra files listed to get your bearings):
>
> start.sh
> ebin/*.beam (my beams)
> src/*.erl (my source)
> src/components/*.{et,erl}
> www/style.css
> lib/erlyweb/Makefile
> lib/erlyweb/ebin/*.beam (the pre-included beams)
> lib/erlyweb/src/...
Do I understand correctly that you include the beam files for ErlyWeb
in your project? My mental model was that the ErlyWeb beam files
should be stored somewhere that Erlang/Yaws could find them on the
computer running the application. Would you recommend keeping them
with the project instead as a best practice?
What are the pros and cons to this approach?
> Then I launch erl (or yaws) with start.sh that contains (more or less):
>
> --------
> #!/bin/sh
> APPDIR=`pwd`
> FULLPA="-pa $APPDIR -pa $APPDIR/ebin -pa $APPDIR/lib/erlyweb/ebin"
>
> erl $FULLPA
> --------
Looks good. Does an equivalent Windows batch file look similar? I have
a Mac so this should work just fine for me. 
> If you plan to re-compile the beam files (for instance, because you
> have Erlang R12B that has a better compiler for the things that
> erlyweb does, like returning largely pre-formed IOlists), then you'll
> need to modify (in the structure above) lib/erlyweb/Emakefile and
> change the first line:
>
> {"src/erlyweb/*", [debug_info, {outdir, "ebin"}, {i,"/opt/local/lib/
> yaws/include"}]}.
>
> Change "/opt/local/lib/yaws/include" to the path to your yaws include
> files (that's the path for a MacPorts install that you won't have to
> change if you're on a Mac and installed Yaws from MacPorts), then do
> "make" in lib/erlyweb/. You may need to remove all of the pre-included
> beams in lib/erlyweb/ebin/ to force it to re-compile if it doesn't
> already.
Ok. I think I follow that. I'll try the first half of your guidance
before attempting to recompile ErlyWeb for myself. I don't use
MacPorts, I'm a download and compile it myself kind of guy most of the
time, except for Erlang stuff, it's still just too different for me
just yet.
> At least that's what I do. You may choose to set it up differently.
I'll try it your way to start with if I can.
The only issue is that I need ErlyWeb installed to run the project
create command in the Music tutorial and your setup has ErlyWeb in the
already created structure. This is a little bit "chicken and egg" for
me. Unless you can assure me that I can just manually create the
project structure and then add the ErlyWeb beam files into it
afterwards.
The joy of new environment confusion!
Simon
--
simonpeter.org | simonpeter.com | newlife-upc.org | wisconsindistrictnews.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Dec 19, 2007 12:06 am |
|
|
|
Guest
|
On Dec 18, 2007 3:46 PM, Simon Chappell <simonpeterchappell@gmail.com> wrote:
>
> On Dec 18, 2007 1:25 PM, David King <dking@ketralnis.com> wrote:
> >
> > > Assuming that Erlang and Yaws are correctly installed and configured:
> > > After unzipping the erlyweb-0.6.2.zip file, I see that there are beam
> > > files under ebin, but there are also makefiles. Does anything need to
> > > be compiled or can the beam files just be put somewhere?
> >
> > The .beam files will probably just work as is. I have a lib/ directory
> > in my project root (that's an svn:externals entry, in my case), like
> > this (some extra files listed to get your bearings):
> >
> > start.sh
> > ebin/*.beam (my beams)
> > src/*.erl (my source)
> > src/components/*.{et,erl}
> > www/style.css
> > lib/erlyweb/Makefile
> > lib/erlyweb/ebin/*.beam (the pre-included beams)
> > lib/erlyweb/src/...
>
> Do I understand correctly that you include the beam files for ErlyWeb
> in your project? My mental model was that the ErlyWeb beam files
> should be stored somewhere that Erlang/Yaws could find them on the
> computer running the application. Would you recommend keeping them
> with the project instead as a best practice?
>
> What are the pros and cons to this approach?
The easiest way to install ErlyWeb is to unzip the package in your
Erlang code path (this is the default place where Erlang finds .beam
files during runtime -- it's usually /usr/local/lib/erlang/lib or
something). You don't have to compile anything yourself.
If you do want to compile it yourself, you have to change the top line
in the Emakefile to match your Yaws path before you call 'make'.
I don't recommend keeping the ErlyWeb files in the project directory.
There's nothing horribly wrong about it, but it may give you the false
impression that you can have multiple apps running with different
versions of ErlyWeb, which is not the case. I think it's more
straightforward to install ErlyWeb in the Erlang code path.
Yariv
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| ketralnis |
| Posted: Wed Dec 19, 2007 12:24 am |
|
|
|
User
Joined: 20 Jul 2007
Posts: 151
Location: San Francisco, CA
|
> Do I understand correctly that you include the beam files for ErlyWeb
> in your project?
Yes, in lib/erlyweb/ebin
> Would you recommend keeping them with the project instead as a best
> practice?
Meh; I track HEAD in my development version, so it makes sense for me.
It's up to you.
> What are the pros and cons to this approach?
* Pro: Easier to track HEAD on erlyweb (esp. using svn:externals)
* Pro: don't have to install erlyweb on development and production
servers and keep them in sync
* Pro: heavy customisations to erlyweb is easier to track and use
* Pro: developing on erlyweb itself is easier than tucking it away in /
usr/local or wherever and editing it there
* Pro: If you have multiple developers, they all have the same version
* Pro: I keep other libraries (like plists, some perl modules), so
it's just one more library to track rather than having to do it
separately.
* Con: if you have multiple erlyweb apps that do this, you have
multiple independent versions of erlyweb
* Con: the chicken-and-egg situation you describe below
There are probably more cons. But it's my preference. It works, at any
rate
>> Then I launch erl (or yaws) with start.sh that contains (more or
>> less):
>>
> Looks good. Does an equivalent Windows batch file look similar? I have
> a Mac so this should work just fine for me.
Similar, yes. I don't have a Windows machine handy to craft and test
one.
>> The only issue is that I need ErlyWeb installed to run the project
> create command in the Music tutorial and your setup has ErlyWeb in the
> already created structure. This is a little bit "chicken and egg" for
> me. Unless you can assure me that I can just manually create the
> project structure and then add the ErlyWeb beam files into it
> afterwards.
That's true. You can manually create most of it, it won't matter to
erlyweb
> The joy of new environment confusion!
Happy to help
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Dec 19, 2007 12:37 am |
|
|
|
Guest
|
>
> Oh, and is there an ETA on the 0.7 release? Will there be many
> differences to allow for in the documentation?
I was planning on releasing it by now, but there seemed to be minor
issues creeping up every now and then (plus, the documentation has
some catching up to do) so I figured I should let the dust settle
before releasing it. It should be released before New Year's. There
won't be any new features for this release between now and then.
Yariv
>
> Simon
>
> --
> simonpeter.org | simonpeter.com | newlife-upc.org | wisconsindistrictnews.org
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| wailian |
| Posted: Tue Mar 20, 2012 2:52 am |
|
|
|
Guest
|
| One of them is the Ugg bailey button boot which has classic and uniquely designed buttons on its body to give that elegant and luxurious look. It has a fantastic look and this includes the Bailey Triplet Boot which has 3 buttons. These boots have a shaft (the upper part of the boot) which can be turned up or turned down depending upon your need. These buttons are both for style or decoration along with being functional or usable as well. |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
