Externals..

[pedromorgan]

On this site we need to access the
original revel.github.io repos and its markdown etc..

Also we need to get a readonyl version of the modules and markdown...

So are these going to be checked out on $GOPATH and accessible on the server..
Is there a hook to update the rf.com branches as soon as an update is done ??

[brendensoares]

@pedromorgan could you provide more context into what this means? Perhaps give a step by step example?

[pedromorgan]

Ok here's the problem

The problem is that we need a love version of current "parts" of the revel project chekout out on the system
so the rf.com app can read..

so maybe we create a "workspace" directory..
with a kinda psuedo

WORKSPACE = "/temp/revelframwork.com.workspace"
for repo in [cmd, revel, modules,  examples, config]:
   for b in [master, develop]:
    // here we checkout to master_cmd, develop_examples etc same dir (no nest confusion)
   git clone gh.com/revel/{repo} {b}_{{repo}}
  cd the_checkout
     git checkout {{b}}
     git pull etc

[notzippy]

I wrote a tool called repo-tool, modeled after the repo tool written for managing android source code. Once you create a manifest file you can set it up however you like and update all the repositories using one command.. It pretty much does what the above script does.. Not sure your specific use case thought

[pedromorgan]

@notzippy ok so am "aunty sitting with laptop".. and https://github.com/notzippy/repo-tool looks good..

So for RF.com we need a dir maybe called workspace/
But snag here is that it works ok local, but imagine on revel.server then its a perms issue..

We need concurrently checkout on the file system to get access to *.md, *.yaml, conf files and 'others stuff..

eg a Modules documentiaon page is the /modules/xmod/README.md (rst)
and the master + develop (would prefer next branch of stuff approved after develop)