[Sputnik-list] blueprint

[Yuri Takhteyev]

>  > 1. There is a script in my svn repository that you can use to package
>  > rocks: scripts/make_a_rock.sh
>
>  Not found

Oops, I never actually committed that directory.  It's committed now.

>  You must explain a bit your work flow.

At this point I keep all of my code in "rocks" separated by which
"rock" it will be released with.

I start off by doing a fresh install, as per instructions on the web
page.  I install everything into some directory inside ~/tmp/.  E.g.,
~/tmp/sputnik-7/.  (I often have a few versions running at the same
time.)  If I want to make sure that a particular rock is up to date
relative to SVN then I go through the steps that I just described on
the wiki:

http://sputnik.freewisdom.org/en/Installing_from_SVN

>  >>    "/opt/sputnik2/sputnik-svn/rocks"

"file:///opt/sputnik2/sputnik-svn/rocks"

>  > sputnik-blueprint/lua/sputnik/actions/blueprint_css.lua
>  > sputnik-blueprint/lua/sputnik/node_defaults/_blueprint_templates.lua
>  > sputnik-blueprint/lua/sputnik/node_defaults/_blueprint_css_screen.lua
>  > sputnik-blueprint/lua/sputnik/node_defaults/_blueprint_css_layout.lua
>  >
>  > This way those files will be available as if they were a part of
>  > "sputnik" package: require("sputnik.actions.blueprint_css")
>
>  Explain !
>  Luarocks would handle the (base) path ? See above.

LuaRocks just adds each rock to your search path.  So, when you say
require("sputnik.actions.blueprint_css"), Lua will go through every
rock looking for
<rock_name>/<version>/lua/sputnik/actions/blueprint_css.lua and will
use the first match it will find.  (It's a bit of a simplification
because LuaRocks may filter the search by <version>.)


>  I would, but I need my new setup to work !
>  With "Sputnik on the Rocks" I wasn't able to use CGI

Let me look into this.  It's possible that wsapi rock changed.

>  Did I get the good version of wsapi ?
>  #  bin/luarocks list
>  wsapi
>     cvs-1 (installed) - /opt/sputnik2/rocks/

Well, you are getting it from CVS, so it might change from one day to another.

>  I need first to put it in good shape (1 week min)
>  Actual code is a mess, juste a proto to show that it would work.
>  But to work proprely I need to make a new setup with SCM and CGI.

Yeah, whenever you feel it's ready for that.


>  > 4. If you have a google account, I can add you to the sputnik-wiki
>  > project (http://code.google.com/p/sputnik-wiki/) so that you could
>  > check the files into SVN.
>
>  Yes this email.

Ok, I'll add you.

>  I will, but maybe I will make a custom form for common parameters
>  before.

Deal.

- yuri

-- 
http://sputnik.freewisdom.org/