-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need Install Documentation #103
Comments
Thanks for your detailed issue, I'll make sure to add installation instructions in the coming days and make the overall process easier. |
In the meanwhile, you could take a look at #94 where I posted some installation instructions. |
With help from #94 , I got Geist up and running on Ubuntu 16.04 server! Now I'm trying to run production:
running the Geist service (with the right path in the config) fails as well. |
@erros84 glad to hear you got it running.
it is in the sample auth config. |
yes it is, and I don't get the missing file error anymore now that I generated the stats.json. with It passes that line, and gets stuck on line 36. My stats.json file starts with: {"errors":[],"warnings":[],"version":"2.6.0","hash":"af7562d9a53ff9c299d9","time":74775,"publicPath":"/static/","assetsByChunkName":{"app":["app.af7562d9a53ff9c299d9.bundle.js","app.af7562d9a53ff9c299d9.bundle.js.map"],"auth":["auth.af7562d9a53ff9c299d9.bundle.js","au so I don't see the problem... |
Make sure you set the environment variable in the same command. |
I backed off to a clean copy of auth.js. Same problem with Using this at the top of auth.js:
The results are:
so...there seems to be an issue with scope, as it evaluates outside I pulled the files down from your latest git commit. |
Woops you are right, it was the scoping. I pushed a fix. |
What service! Thanks! Works now. |
But when I open page i get "stats not defined" in routes.js down the line. |
hmm this is strange indeed, the scoping doesn't seem to be an issue for me. Maybe it has to do with different node.js versions. I am running version 7.10.0. |
I'm on nodejs 8.1.3, i'll downgrade to 7.10.0. |
I am well aware that this is a prototype, but it is a prototype I like so much that I am willing to battle with it. I have all the dev and prod dependencies installed (except react-tap-event-plugin that has conflicts). Runnig Geist in Dev mode seems to work without problems. Analytics seem to be working. Twitter login is working. Nevertheless, on nodejs 7.10.0, running in Production mode (as above) doesn't throw any more errors, but it still does not work.
Opening [host]:3001/ shows a title in the menu bar with no content. It is similar to accessing the site in dev mode before the webpack has finished loading. Looking at the code, the link to the bundle Maybe I generated my stats.json file the wrong way...what is the correct process? Any ideas? I have run |
Kudos to you for your perseverance! The production setup is not really meant to be run on a local pc to be honest. It is more for a production setup with multiple users. |
Ok, that helps to understand. There are 3 of us currently testing it at home and at work, and it took me a while to find that my port-forwarding for the dev version needed to expose both ports 3000 and 3001 to be accessible outside the LAN. So If I only have one multi-core server to play with (I moved the VM off of my main machine), what goodies am I losing by running in dev? By the way, I'm calling my server Krang (from the Ninja Turtles) as it functions as an external brain. |
@erros84 minification and some performance optimization and some dev functionality is turned off. And that is a pretty cool name haha! |
See #165 |
Hi Bryan,
I just spent a long evening trying to install Geist locally on an Ubuntu 14.04 VM. I probably should have used 16.04, as it would have made Java easier, but I was learning the constraints as I went.
I'm not a javascript guru, so I had to learn to use nodejs, which slowed me down considerably.
I was hoping that the dev version would bypass the auth protocol for a locally-run application. And as I mentioned on Twitter, if I can get it running locally, maybe I can make it edit, preview, and store DITA topics and tasks (#90), but I bet you (Bryan) could do it faster and better.
I created my own install documentation along the way (for repeatability), that may be helpful as you work on install instructions. This is what I've accomplished so far:
Initial Steps (on Main Branch):
Install Ubuntu in a VM.
Install Nodejs (4 or later: https://stackoverflow.com/questions/36843574/node-js-readline-unexpected-token) and NPM
Install mondoDB
Clone Geist git repo.
Browse to that folder.
Install most of the dependencies
https://stackoverflow.com/questions/17509669/how-to-install-an-npm-package-from-github-directly
External Utilities:
Install Java 8
Install Redis:
Install Nodejs
Install elasticsearch
Create API key for twitter and input it into server/config/auth.js
Debugging:
browse to node_modules/parallelshell/index.js and replace "process.cwd" with "process.cwd()"
For running Production:
I need to create stats.js file. The step below doesn't work for me, so I can't manage to run Production.
For running Dev:
And I get a blank screen
The text was updated successfully, but these errors were encountered: