Need Install Documentation

[MattGyverLee]

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

npm install

• Install the ones it missed:

npm install csurf
npm install bcrypt
npm install passport-twitter
npm install passport-google-oauth
npm install passport-github2
npm install passport-facebook

• Install deprecated and special modules:

npm install mimelib@0.2.14
npm install moment@2.11.2
npm install emailjs
npm install git+https://github.com/bryanph/full-auth-middleware.git

https://stackoverflow.com/questions/17509669/how-to-install-an-npm-package-from-github-directly

• create auth.js and config.js files

cd server/config
cp auth.sample.js auth.js
cp config.sample.js config.js

External Utilities:

• Install Java 8

  • Need workaround on Ubuntu 14.04:
  • http://neo4j.com/docs/operations-manual/current/installation/linux/debian/?_ga=2.248729927.1391978100.1498432735-1122742413.1498432735

• Install Redis:

  • https://www.digitalocean.com/community/tutorials/how-to-install-and-use-redis

• Install Nodejs

  • http://debian.neo4j.org/?_ga=2.5412211.1391978100.1498432735-1122742413.1498432735
  • Log in to http://localhost:7474 and set password
  • Enable Bolt interface (Open a Bolt connector to your embedded instance to get GUI administration and other benefits. neo4j/neo4j#7608)

• Install elasticsearch

  • https://www.elastic.co/guide/en/elasticsearch/reference/current/_installation.html

• Create API key for twitter and input it into server/config/auth.js

  • When you get there: Twitter login will fail with this error (https://twittercommunity.com/t/desktop-applications-only-support-the-oauth-callback-value-oob-oauth-request-token/252/15)

Debugging:

• browse to node_modules/parallelshell/index.js and replace "process.cwd" with "process.cwd()"

  • If you don't do this, parallelshell will fail on the "npm run dev" command.

For running Production:

• nodejs index.js

I need to create stats.js file. The step below doesn't work for me, so I can't manage to run Production.

webpack --env production --profile --json --config='webpack.config.prod.js' --output-filename='stats.json'

For running Dev:

npm run dev

• Open http://localhost:3001
• Try to create account
  • Email will fail, but a verified account is created in the database.
  • Login with this account.

And I get a blank screen

[bryanph]

Thanks for your detailed issue, I'll make sure to add installation instructions in the coming days and make the overall process easier.

[bryanph]

In the meanwhile, you could take a look at #94 where I posted some installation instructions.

[MattGyverLee]

With help from #94 , I got Geist up and running on Ubuntu 16.04 server!
Everything loads up with:
npm run dev
and I can use the server.

Now I'm trying to run production:
npm run build:webpack
generated the stats.json I was missing, but when i try to run in production mode by setting environment
export NODE_ENV=production
and running:
node index.js
I get this error:

matt@Geist:~/Geist$ node index.js
/home/matt/Geist/server/config/auth.js:36
    "bundleFileName": process.env.NODE_ENV === 'development' ? 'auth.bundle.js' : stats.assetsByChunkName.auth[0],
                                                                                  ^

ReferenceError: stats is not defined
    at Object.<anonymous> (/home/matt/Geist/server/config/auth.js:36:83)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/matt/Geist/server/app.js:87:20)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)

running the Geist service (with the right path in the config) fails as well.
What am I doing wrong?

[bryanph]

@erros84 glad to hear you got it running.
Is this line at the top of auth.js?

const env = process.env.NODE_ENV;

if (env !== 'development') {
    const stats = require('../../stats.json')
}

it is in the sample auth config.

[MattGyverLee]

yes it is, and I don't get the missing file error anymore now that I generated the stats.json. with npm run build:webpack

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...

[bryanph]

Make sure you set the environment variable in the same command.
So running NODE_ENV=production node index.js

[MattGyverLee]

I backed off to a clean copy of auth.js. Same problem with NODE_ENV=production node index.js.

Using this at the top of auth.js:

if (env !== 'development') {
    const stats = require('../../stats.json')
    console.log(`env is ${env}`)
    console.log(`Version is ${stats.version}`);
    console.log(`auth is ${stats.assetsByChunkName.auth[0]}`);
}

The results are:

env is production
Version is 2.6.0
auth is auth.af7562d9a53ff9c299d9.bundle.js

so...there seems to be an issue with scope, as it evaluates outside const auth but not inside.

I pulled the files down from your latest git commit.

[bryanph]

Woops you are right, it was the scoping. I pushed a fix.
Sorry for the hassle.

[MattGyverLee]

What service! Thanks! Works now.

[MattGyverLee]

But when I open page i get "stats not defined" in routes.js down the line.
Do you have stats defined globally somehow on your machine? How are you not seeing this?

[bryanph]

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.
That said, i removed the scoping there as well

[MattGyverLee]

I'm on nodejs 8.1.3, i'll downgrade to 7.10.0.

[MattGyverLee]

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.

Aug 02 01:32:52 Geist systemd[1]: Started Geist-Prod.
Aug 02 01:32:53 Geist nodejs[5434]: env is production
Aug 02 01:32:53 Geist nodejs[5434]: Version is 2.6.0
Aug 02 01:32:53 Geist nodejs[5434]: auth is auth.6e2c3df3db3f3bc53b0a.bundle.js
Aug 02 01:32:54 Geist nodejs[5434]: listening on port 3001

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 <script src="https://192.168.1.104/static/app.6e2c3df3db3f3bc53b0a.bundle.js"></script> is a dead link.

Maybe I generated my stats.json file the wrong way...what is the correct process?

Any ideas?

I have run npm run build and this runs as well (also without errors).

[bryanph]

Kudos to you for your perseverance!
In my production setup, I load the static files using nginx, a separate webserver. Hence, these are not loaded by the node.js server (it just does the API logic). So I expose the public/ folder on the URL /static/ and the assets folder on the URL /media/ using an external webserver (in my production setup).

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.

[MattGyverLee]

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.

[bryanph]

@erros84 minification and some performance optimization and some dev functionality is turned off. And that is a pretty cool name haha!

[bryanph]

See #165