Closed brandon-bethke-timu closed 8 years ago
We have seen a related issue when phantomjs starts converting SPA routes to an html site, link to known issue.
The tl;dr recommendation is to delete the build_html/ directory, and run grunt (which starts the docbase:def task). If the build succeeds, the generator should start an http-server after the grunt execution. Or if you prefer to run it manually, the html site will be created under the build_html/ directory.
Sorry, it's not working. I installed phantomjs using npm, version 2.1.1 was installed. I still get the error. The build_html/ directory never is created / doesn't exist.
Can you share the log output from yo docbase
? It's hard to tell without
it.
On Wed, Apr 6, 2016 at 1:03 AM, brandon-bethke-neudesic < notifications@github.com> wrote:
Sorry, it's not working. I installed phantomjs using npm, version 2.1.1 was installed. I still get the error. The _buildhtml/ directory never is created / doesn't exist.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/appbaseio/Docbase/issues/15#issuecomment-205960327
ᐧ ᐧ
@brandon-bethke-neudesic this tells us that your installation is going well, but there is a failure in the html pages creation task in the grunt process. It does not tell us the nature of failure.
@mateusfreira introduced a new commit in the grunt process that should provide debug information on failure. You can now set the parameter enableCrawlerDebug in './node_modules/grunt-docbase/tasks/docbase.js#L34' to true and docbase will print the necessary debug information for us to fix this.
Thank you. Here is the terminal output with the enableCrawlerDebug flag set.
@brandon-bethke-neudesic are you using Docbase as a root user? Able to replicate the bug in that scenario.
I am using a mac and I am logged as an Admin user, but I am not doing a sudo or anything like that.
What is the output of ls -l
after the build failure error?
@brandon-bethke-neudesic thanks, it's missing the bower_components/ directory. That's the reason document generation is failing, working on a fix.
@brandon-bethke-neudesic a new yeoman generator has been released that addresses this. Does it work for you?
I am sorry, but it does not work. I uninstalled and then re-installed yo and docbase-generator. I get the same error message and the bower_components/ directory is not there.
@brandon-bethke-neudesic can you execute manually the command
bower install --allow-root
and send us the result?
Is bower something that needs to be installed manually? because it's not in the node_modules folder and I get command not found when I try to execute the command.
@brandon-bethke-neudesic yes, it can be installed with npm install -g bower
. Docbase currently assumes npm
, bower
and grunt-cli
to be installed on the user's system.
In conclusion, the problem appears to have been that bower was not installed. Sorry.
I'm seeing this issue but have bower, npm, grunt-cli installed etc. We're running on Ubuntu. Any ideas what else to check?
@clarkd Can you set the parameter enableCrawlerDebug in './node_modules/grunt-docbase/tasks/docbase.js#L34' to true and share the resulting output?
@siddharthlatest I've managed to get it working by installing a previous version of Phantom. All going well now! Pretty happy with the docs already although a quick question - does it support multi-level nav beyond a single dropdown/depth?
@clarkd It doesn't support that right now.
When I perform the following steps I get an error in the console and a blank page is displayed when I hit the local site. Can't figure out if this is an issue with the product or not.
) yo docbase ) when prompted
) For hosted option select 'Magic'
) For publish option select 'Locally'
*) For color option select 'green'
...stuff is printed to console
Running "docbase:def" (docbase) task starting Erro generating page: build_html/index.html