Production Speckle Server deployment

Hi,

the docker has limited functionality, so I am proceeding to the installation of the SpeckleServer to an actual server visible on www with OS Ubuntu 16.04. After the installation of Redis and Psql v13, I have to open some ports.

Which ports should be open publicly? I assume 3000 that node.js is running is mandatory. Another possible candidate is 6379 of Redis server. Should also psql:5432 port be open ? I assume not. The concept is that Redis serves the static content and Node.js the dynamic one ? The access to database is done through Redis ?

Best,
Dimitrios.Ververidis@PrismArch

Hi @Dimitrios.Ververidis, pretty much the only port you need to open is 3000. Make sure though you’ll set your canonical url env var to your actual ip adress :3000. You’ll miss https, which will make it an insecure deployment.

If this is part of the Prism project, we can, through our free academia partnership program, just deploy one for you at a subdomain of choice under speckle.xyz. Let us know!

Hi Dimitrie,

thanks for the offer. Indeed it is part of PrismArch project. I suspect that AEC partners will start the questions about data security, so I have to ask them first about external positioning of data. Let me first give it a try to our server.

I have followed the steps in https://github.com/specklesystems/speckle-server/tree/main/packages/server

"The Speckle Server is a node application tested against v12. To start it locally:

First, ensure you have postgres and redis ready and running (check the readme.md from the root of the git repo)

Finally, in the packages/server folder:

  • copy the .env-example file to .env,
  • If you have a custom setup, open and edit the .env file, filling in the required variables,
  • run npm install,
  • finally npm run dev,
  • check localhost:3000/graphql out!
    "

After “npm run dev” I get this in the log file.

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘run’, ‘dev’ ]
2 info using npm@6.14.8
3 info using node@v12.20.0
4 verbose run-script [ ‘predev’, ‘dev’, ‘postdev’ ]
5 info lifecycle @speckle/server@2.2.0~predev: @speckle/server@2.2.0
6 info lifecycle @speckle/server@2.2.0~dev: @speckle/server@2.2.0
7 verbose lifecycle @speckle/server@2.2.0~dev: unsafe-perm in lifecycle true
8 verbose lifecycle @speckle/server@2.2.0~dev: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/html/speckle/packages/server/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle @speckle/server@2.2.0~dev: CWD: /var/www/html/speckle/packages/server
10 silly lifecycle @speckle/server@2.2.0~dev: Args: [
10 silly lifecycle ‘-c’,
10 silly lifecycle ‘cross-env NODE_ENV=development DEBUG=speckle:* nodemon ./bin/www --watch . --watch ./bin/www -e js,graphql,env’
10 silly lifecycle ]
11 silly lifecycle @speckle/server@2.2.0~dev: Returned: code: 126 signal: null
12 info lifecycle @speckle/server@2.2.0~dev: Failed to exec dev script
13 verbose stack Error: @speckle/server@2.2.0 dev: cross-env NODE_ENV=development DEBUG=speckle:* nodemon ./bin/www --watch . --watch ./bin/www -e js,graphql,env
13 verbose stack Exit status 126
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid @speckle/server@2.2.0
15 verbose cwd /var/www/html/speckle/packages/server
16 verbose Linux 4.15.0-126-generic
17 verbose argv “/usr/bin/node” “/usr/bin/npm” “run” “dev”
18 verbose node v12.20.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 126
22 error @speckle/server@2.2.0 dev: cross-env NODE_ENV=development DEBUG=speckle:* nodemon ./bin/www --watch . --watch ./bin/www -e js,graphql,env
22 error Exit status 126
23 error Failed at the @speckle/server@2.2.0 dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 126, true ]

And this is my .env

###########################################################
# Basics
# The following env vars are expected to exist.
# Fill them in here, or make sure you provide them via
# your deployment environment.
############################################################
PORT=3000

CANONICAL_URL="http://myiphiddenhere:3000"
SESSION_SECRET="I am a secret that should not be revealed"

# Redis connection: default for local development environment
REDIS_URL="redis://myiphiddenhere:6379"

############################################################
# Postgres Database
# the connection uri is built up from these variables
############################################################
# If you specify a user and password, do not specify the protocol in the
# POSTGRES_URL variable.
# These defaults are set for the local development environment
POSTGRES_URL="localhost"
# this overrides the default root user in the postgres instance
POSTGRES_USER="speckle"
# this sets the root user password in the postgres instance
POSTGRES_PASSWORD="speckle"
# this overrides the default database name in postgres
POSTGRES_DB="speckle"

############################################################
# Emails
############################################################
EMAIL=false
# EMAIL_HOST="-> FILL IN <-"
# EMAIL_PORT="-> FILL IN <-"
# EMAIL_USERNAME="-> FILL IN <-"
# EMAIL_PASSWORD="-> FILL IN <-"

############################################################
# Auth strategies
# At least one needs to be enabled!
############################################################
STRATEGY_LOCAL=true

# STRATEGY_GITHUB=false
# GITHUB_CLIENT_ID="-> FILL IN <-"
# GITHUB_CLIENT_SECRET="-> FILL IN <-"

# STRATEGY_GOOGLE=false
# GOOGLE_CLIENT_ID="-> FILL IN <-"
# GOOGLE_CLIENT_SECRET="-> FILL IN <-"


############################################################
# Tracing & co.
# Note: all data is anonymous, and it helps us deliver
# better software. Disabling this makes Speckle sad!
############################################################
# SENTRY_DSN="-> FILL IN <-"
# DISABLE_TRACING=""
# DISABLE_TRACKING=""

############################################################
# Local dev environments
# If your frontend is served in dev from somewhere else,
# this is going to help out :)
############################################################
# FRONTEND_HOST=localhost
# FRONTEND_PORT=8081

I assume that something is wrong at

cross-env NODE_ENV=development DEBUG=speckle:* nodemon ./bin/www --watch . --watch ./bin/www -e js,graphql,env

???

I have cleaned the node modules and install them again.

Also I have changed in .env REDIS_URL=“redis://myiphiddenhere:6379” with REDIS_URL=“redis://localhost:6379”

now I get with

“sudo npm run dev”

other errors

@speckle/server@2.2.0 dev /var/www/html/speckle/packages/server
cross-env NODE_ENV=development DEBUG=speckle:* nodemon ./bin/www --watch . --watch ./bin/www -e js,graphql,env

[nodemon] 2.0.6
[nodemon] to restart at any time, enter rs
[nodemon] watching path(s): . bin/www
[nodemon] watching extensions: js,graphql,env
[nodemon] starting node ./bin/www
speckle:db-startup Loaded knex conf for development +0ms
[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
speckle:www error: password authentication failed for user “speckle”
speckle:www at Parser.parseErrorMessage (/var/www/html/speckle/packages/server/node_modules/pg-protocol/dist/parser.js:278:15)
speckle:www at Parser.handlePacket (/var/www/html/speckle/packages/server/node_modules/pg-protocol/dist/parser.js:126:29)
speckle:www at Parser.parse (/var/www/html/speckle/packages/server/node_modules/pg-protocol/dist/parser.js:39:38)
speckle:www at Socket. (/var/www/html/speckle/packages/server/node_modules/pg-protocol/dist/index.js:10:42)
speckle:www at Socket.emit (events.js:314:20)
speckle:www at Socket.EventEmitter.emit (domain.js:483:12)
speckle:www at addChunk (_stream_readable.js:297:12)
speckle:www at readableAddChunk (_stream_readable.js:272:9)
speckle:www at Socket.Readable.push (_stream_readable.js:213:10)
speckle:www at TCP.onStreamRead (internal/stream_base_commons.js:188:23) +0ms
[ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)

Should I create manually speckle database or it is created automatically ?

Hi,

If you installed postgresql manually, you have to create the database and specify it in the .env, along with a valid user for the postgres installation.

But if you just want to get up and running faster, you can use our docker-compose files for running the dependencies in docker containers, configured as expected.

Check out our documentation about it: Deploying a local Server | Speckle Docs

Also, if you don’t plan to develop the speckle server in this environment, you can also run speckle server in docker containers (Method 1 from the mentioned documentation)

Cristian

2 Likes

ok that was it.

I guess that automatically creating speckle database and user could improve things. Alternatively it should be mentioned that it should be manually created.

I am writing the psql commands here for convenience:

create user speckle with encrypted password ‘speckle’;
CREATE DATABASE speckle;
grant all privileges on database speckle to speckle;

Best,
Dimitrios

1 Like

Hi,
I have installed also pgAdmin and works perfect.

Now I want to add Front-end and Viewer. It is not clear which should be installed first.


1. Instructions for Front-end

The frontend now includes the viewer. Until we get to publish it as a separate module, there’s a few extra steps:

  • make sure you build the Speckle Viewer
  • afterwards, run lerna bootstrap

Compiles and hot-reloads for development

npm run serve

Compiles and minifies for production

npm run build

2. Instructions for Viewer

For development purposes, to start a webpack live reload server run:

npm run serve

You can now access the example at http://localhost:9000/example.html.

To build the library, you should run:

npm run build

???

It really depends on how you’re running your server, production mode or development mode, and for what intents. I’m going to assume you just want to have it running locally for now:

  • NODE_ENV=production: you just need to npm install && npm run build in the frontend package folder.
  • NODE_ENV=development: run npm install && npm run serve in the frontend package folder.

If i read through this correctly, probably the second applies. Once that’s run, the frontend will be proxied by the server at localhost:3000, so ignore the output from vue cli you will see post npm run serve.

Hi dimitrie,

it is already visible to www with an ip so it is not for localhost use.

We want to run it in development mode.
Since programmers and end-users are at their homes and experimenting with it, it should be visible from everywhere.

So I am proceeding with the “Front-end” package in development mode.

Where should I put the variable “NODE_ENV=development” ? in .env ?

If it’s run with npm run dev, it will be in dev mode! Just run then npm install && npm run build in the frontend package and let me know if a frontend pops up!

1. Install

It has some issues but it seems ok.

npm install 



> core-js@3.8.1 postinstall /var/www/html/speckle/packages/frontend/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
> https://opencollective.com/core-js 
> https://www.patreon.com/zloirock 

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)


> ejs@2.7.4 postinstall /var/www/html/speckle/packages/frontend/node_modules/ejs
> node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)


> @apollo/protobufjs@1.0.5 postinstall /var/www/html/speckle/packages/frontend/node_modules/@apollo/protobufjs
> node scripts/postinstall


> nodemon@1.19.4 postinstall /var/www/html/speckle/packages/frontend/node_modules/nodemon
> node bin/postinstall || exit 0

npm WARN camera-controls@1.28.0 requires a peer of three@^0.126.1 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/nodemon/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1704 packages from 1064 contributors and audited 1712 packages in 44.367s

57 packages are looking for funding
  run `npm fund` for details

found 16 vulnerabilities (3 low, 5 moderate, 8 high)
  run `npm audit fix` to fix them, or `npm audit` for details


2. BUILD

Also here are some warnings but it seems ok

npm run build

> @speckle/frontend@2.2.1 build /var/www/html/speckle/packages/frontend
> vue-cli-service build


â ™  Building for production...

 WARNING  Compiled with 9 warnings                                                                                                                                                                                                           11:47:57 AM

 warning  

chunk chunk-2de4fc0d [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VCard/VCard.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/directives/ripple/VRipple.sass
   - couldn't fulfill desired order of chunk group(s) , , , , , , , , , , , , 
   - while fulfilling desired order of chunk group(s) , , , , 

 warning  

chunk chunk-2de4fc0d [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VProgressLinear/VProgressLinear.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/directives/ripple/VRipple.sass
   - couldn't fulfill desired order of chunk group(s) , , , , , , , , , , , , 
   - while fulfilling desired order of chunk group(s) , , , , 

 warning  

chunk chunk-39862bf6 [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VInput/VInput.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VTextField/VTextField.sass
   - couldn't fulfill desired order of chunk group(s) , , , , , , , , , , , , , 

 warning  

chunk chunk-39862bf6 [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VLabel/VLabel.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VTextField/VTextField.sass
   - couldn't fulfill desired order of chunk group(s) , , , , , , , , , , , , , 

 warning  

chunk chunk-39862bf6 [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VTextField/VTextField.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VMessages/VMessages.sass
   - couldn't fulfill desired order of chunk group(s) 
   - while fulfilling desired order of chunk group(s) , , , , , , , , , , , , , 

 warning  

chunk chunk-7265f96a [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VBtn/VBtn.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VIcon/VIcon.sass
   - couldn't fulfill desired order of chunk group(s) 
   - while fulfilling desired order of chunk group(s) , , , , , , , , , , , , , , , , 

 warning  

chunk chunk-7265f96a [mini-css-extract-plugin]
Conflicting order. Following module has been added:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VProgressCircular/VProgressCircular.sass
despite it was not able to fulfill desired ordering with these modules:
 * css ./node_modules/css-loader/dist/cjs.js??ref--9-oneOf-3-1!./node_modules/postcss-loader/src??ref--9-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--9-oneOf-3-3!./node_modules/vuetify/src/components/VIcon/VIcon.sass
   - couldn't fulfill desired order of chunk group(s) 
   - while fulfilling desired order of chunk group(s) , , , , , , , , , , , , , , , , 

 warning  

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets: 
  fonts/materialdesignicons-webfont.4187121a.woff2 (312 KiB)
  fonts/materialdesignicons-webfont.fec1b66a.woff (446 KiB)
  fonts/materialdesignicons-webfont.3d1f8fa2.eot (982 KiB)
  fonts/materialdesignicons-webfont.3e722fd5.ttf (981 KiB)
  img/onboardingsplash.2f7ac815.png (322 KiB)
  js/chunk-97dcf120.c005d14e.js (927 KiB)
  js/chunk-9fd2d8fe.52aaf3af.js (811 KiB)
  js/chunk-b5664fd0.67e4c1bb.js (856 KiB)
  css/chunk-vendors.78cc2cdf.css (525 KiB)
  js/chunk-vendors.dbe842ea.js (1.15 MiB)

 warning  

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (1.68 MiB)
      css/chunk-vendors.78cc2cdf.css
      js/chunk-vendors.dbe842ea.js
      css/app.286e3040.css
      js/app.b7c808fe.js


  File                                    Size              Gzipped

  dist/js/chunk-vendors.dbe842ea.js       1179.42 KiB       363.16 KiB
  dist/js/chunk-97dcf120.c005d14e.js      926.81 KiB        235.17 KiB
  dist/js/chunk-b5664fd0.67e4c1bb.js      856.49 KiB        212.19 KiB
  dist/js/chunk-9fd2d8fe.52aaf3af.js      811.17 KiB        201.02 KiB
  dist/js/chunk-5e276b1e.5e4d16bc.js      162.88 KiB        42.78 KiB
  dist/js/chunk-59c2a73e.25c00f8b.js      127.37 KiB        32.34 KiB
  dist/js/chunk-d51158c6.81097395.js      121.15 KiB        31.63 KiB
  dist/js/chunk-35728398.a7e08557.js      112.73 KiB        30.40 KiB
  dist/js/chunk-7a7da7de.a4eafdb5.js      97.63 KiB         26.90 KiB
  dist/js/chunk-73c9b9a8.04e40100.js      94.28 KiB         25.48 KiB
  dist/js/chunk-5308cdee.d9dc7761.js      93.36 KiB         25.11 KiB
  dist/js/chunk-3aadb008.b62a3919.js      54.36 KiB         15.19 KiB
  dist/js/chunk-194bd293.c0811b3c.js      35.17 KiB         10.16 KiB
  dist/js/chunk-28ffb2ef.87a87270.js      24.33 KiB         7.94 KiB
  dist/js/chunk-39862bf6.45ffa45e.js      21.71 KiB         6.27 KiB
  dist/js/chunk-c20ae132.8d82ed3e.js      19.73 KiB         6.54 KiB
  dist/js/chunk-2de4fc0d.302252b6.js      18.78 KiB         5.67 KiB
  dist/js/app.b7c808fe.js                 16.91 KiB         5.19 KiB
  dist/js/chunk-6365c9b5.12a97951.js      16.35 KiB         5.43 KiB
  dist/js/chunk-6cc4f16d.208f9762.js      15.29 KiB         5.03 KiB
  dist/js/chunk-7380123c.f253979d.js      13.43 KiB         4.77 KiB
  dist/js/chunk-7265f96a.befbbfa0.js      11.26 KiB         3.75 KiB
  dist/js/chunk-a1707080.c0afb415.js      9.54 KiB          3.43 KiB
  dist/js/chunk-06f72f4a.f788c72c.js      7.31 KiB          2.82 KiB
  dist/js/chunk-defab8a4.b8edb57c.js      4.47 KiB          1.90 KiB
  dist/js/chunk-2d0c8ff6.beb06388.js      2.56 KiB          1.16 KiB
  dist/js/chunk-2d22cdf7.dbf53099.js      2.43 KiB          1.14 KiB
  dist/js/chunk-2d0c8c18.7c241438.js      0.57 KiB          0.38 KiB
  dist/css/chunk-vendors.78cc2cdf.css     525.10 KiB        72.54 KiB
  dist/css/chunk-5e276b1e.0429c530.css    79.62 KiB         10.34 KiB
  dist/css/chunk-97dcf120.04f4151a.css    69.94 KiB         9.12 KiB
  dist/css/chunk-b5664fd0.180bab9e.css    61.00 KiB         8.46 KiB
  dist/css/chunk-73c9b9a8.c1a9306c.css    61.00 KiB         7.98 KiB
  dist/css/chunk-d51158c6.6eb2c579.css    59.65 KiB         7.84 KiB
  dist/css/chunk-3aadb008.d0d754b7.css    57.54 KiB         7.16 KiB
  dist/css/chunk-35728398.93a42a47.css    55.70 KiB         8.04 KiB
  dist/css/chunk-59c2a73e.fe41332e.css    54.65 KiB         7.72 KiB
  dist/css/chunk-5308cdee.943e7c6d.css    52.57 KiB         7.36 KiB
  dist/css/chunk-7a7da7de.c982246f.css    51.23 KiB         6.73 KiB
  dist/css/chunk-9fd2d8fe.a302e4bd.css    26.60 KiB         4.24 KiB
  dist/css/chunk-39862bf6.4b83cbbc.css    22.39 KiB         3.04 KiB
  dist/css/chunk-6365c9b5.875b4c62.css    21.42 KiB         3.02 KiB
  dist/css/chunk-06f72f4a.08a54220.css    18.10 KiB         2.39 KiB
  dist/css/chunk-defab8a4.b5c9c2ff.css    16.87 KiB         1.98 KiB
  dist/css/chunk-6cc4f16d.2b364ad1.css    12.05 KiB         1.59 KiB
  dist/css/chunk-7265f96a.c04b5267.css    9.82 KiB          2.14 KiB
  dist/css/chunk-194bd293.dfe851b7.css    9.70 KiB          1.71 KiB
  dist/css/chunk-2de4fc0d.138af52c.css    9.55 KiB          1.89 KiB
  dist/css/chunk-28ffb2ef.9814ad34.css    4.65 KiB          1.17 KiB
  dist/css/chunk-c20ae132.ffe22fa2.css    4.65 KiB          1.17 KiB
  dist/css/chunk-7380123c.9deb4d24.css    3.14 KiB          0.80 KiB
  dist/css/chunk-a1707080.9deb4d24.css    3.14 KiB          0.80 KiB
  dist/css/app.286e3040.css               2.17 KiB          0.63 KiB

  Images and other types of assets omitted.

 DONE  Build complete. The dist directory is ready to be deployed.
 INFO  Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

I tried the following to call the front-end

“http://[ip]:3000/explorer/”

which says that I should login:

If I press login I get black screen with the following:

“Error occured while trying to proxy to: ip:3000/authn/verify/explorer/c6qdx4tg93azokxr1rnuja”

Apologies, gave you some wrong instructions there… npm run dev in the frontend package folder, and the frontend should be accessible then at the root url!

I’ll go make my second coffee to be properly awake.

In development mode, the server package (running at port 3000) proxies frontend requests to the frontend host:port, as configured in the .env file (FRONTEND_HOST, FRONTEND_PORT)

Btw, running packages in development mode exposed on the internet is not recommended (security issues).

“npm run dev”
worked fine

indeed ip:3000 is working now visualizing the front-end

Next thing is to check if commiting from several people is working, and how we can merge some test work first in Rhino and Grasshoper, and then in Revit.

PS: I went for a walk since too many coffees harm.

Hi cristi,

in order to run in production mode
I have first to run server with “build” mode

server > npm install
server > npm run build

and then also the front-end with “build” ?

front-end > npm install
front-end > npm run build

what will not work in build mode ?

ip:3000\graphql ?
pgAdmin ?
ip:3000\profile
ip:3000\explorer

Are there any other open windows ?

One of my tasks is to semantically search for information inside rvt (IFC actually). So, can I query one of the tables of the database to get the rvt model to transform it IFC ? We have found ways to transform IFC to RDF and do semantics queries.

             List of relations

Schema | Name | Type | Owner
--------±------------------------±------±--------
public | api_tokens | table | speckle
public | authorization_codes | table | speckle
public | branch_commits | table | speckle
public | branches | table | speckle
public | commits | table | speckle
public | knex_migrations | table | speckle
public | knex_migrations_lock | table | speckle
public | object_children_closure | table | speckle
public | objects | table | speckle
public | personal_api_tokens | table | speckle
public | pwdreset_tokens | table | speckle
public | refresh_tokens | table | speckle
public | scopes | table | speckle
public | server_acl | table | speckle
public | server_apps | table | speckle
public | server_apps_scopes | table | speckle
public | server_config | table | speckle
public | server_invites | table | speckle
public | stream_acl | table | speckle
public | stream_commits | table | speckle
public | streams | table | speckle
public | token_scopes | table | speckle
public | user_roles | table | speckle
public | user_server_app_tokens | table | speckle
public | users | table | speckle
(25 rows)

Best,
Dimitrios@PrismArch

Hi,

For the frontend, npm run build only compiles the Vue app and doesn’t run any service with it.
npm run build is used to build the package, not run it (the run in npm run is just for executing a script, and build is the name of the script, defined in package.json, under scripts)

Again, these are features useful for development of the packages. If you want to be able to access them in the browser, you must use nginx or the nodejs process to serve the files in development mode (npm run serve)

If you just want to run a Speckle server, we automated the build and running processes and created a docker-compose file that you can use to get up and running without issues like these.

Maybe try Deploying a local Server | Speckle Docs ?

So first, make sure you get the latest version from git.
Then, edit the docker-compose-speckle.yml:

  • change the environment variables for speckle-server: POSTGRES_URL to 127.0.0.1, REDIS_URL to 127.0.0.1, CANONICAL_URL and SESSION_SECRET.
  • if you run postgres and redis on the VM directly, add: network_mode: host right below restart: always to both frontend definition and the server definition (with the same level of indentation as restart: always)

Then run the docker-compose up command as described in the documentation. You can check logs with docker-compose -f docker-compose-speckle.yml logs

You should be able to access the speckle server in the browser at http://PUBLIC_IP_ADDRESS:3000/

ok,

so the production mode is dockerized, so no changes can be easily done. Since our project is exploratory in virtual reality, we will stick to dev mode (for the time being)

I have tried to invite new members from

but I get this:

Should the user be already registered to the server to send the invite ?

Sorry probably due to the fact that I forgot to setup mails in .env

Should I rebuild or just edit and run dev ?

D.

Ha, yes! you beat me to it.

You’ll need to provide the following env variables to be able to send emails:

We’re using mailjet. There are other smtp providers, such as sendgrid, amazon ses, etc. that you could try. Alternatively, just ask everyone to join… manually :slight_smile:

PS: and yes, you will need to restart the server process once those are filled in.

Hmmm,

when I am trying to commit from Rhino @home @mylaptop, It does not seem to connect to the server which is at the lab.

After a while it stops without commiting

Since the port is open, I suspect some priviledges issues ???

D.