It's very possible that the Exception is being caused by thet network - we
do use it to build the list of plugins.
Go ahead and send a pull request - I'll try it out locally.
On Mon, Aug 27, 2012 at 3:58 PM, Ivan St. Ivanov
As promised more than a month ago, I reviewed the new site and synced all
the changes done in the wiki site. I have a change prepared locally. But
unfortunately I cannot start awestruct to see what I have done. I updated
it to its latest version, but still my _site subdirectory remains empty so
awestruct has nothing to serve:
Invalid argument -
`block in execute'
Serving site at D:/projects/seamforge/forge.github.com/_site
[2012-08-23 19:05:11] INFO WEBrick 1.3.1
[2012-08-23 19:05:11] INFO ruby 1.9.3 (2012-02-16) [i386-mingw32]
The only problematic line here is the fact that
Could that be the reason why I cannot start the server?
Anyway, with this I would like to state that at least the differences
between our old and new sites were spotted and prepared to be transferred.
Maybe I can push to my github repo and someone able to start the server can
review my changes?
On Wed, May 2, 2012 at 8:00 PM, Lincoln Baxter, III <
> Now, to deploy the website, simply checkout the 'develop' branch of
, and type: "awestruct -P production
> On Wed, May 2, 2012 at 9:58 AM, Lincoln Baxter, III <
> lincolnbaxter(a)gmail.com> wrote:
>> Sorry for the short notice. I've moved the master branch of
into the 'develop' branch of
in order to get our CI builds
>> We should be deleting the /website repository soon.
>> Lincoln Baxter, III
>> "Simpler is better."
> Lincoln Baxter, III
> "Simpler is better."
> forge-dev mailing list
forge-dev mailing list