Closed MartinHenriksen closed 5 years ago
Hello Mr. @MartinHenriksen! Good to see you around these parts :) I've added some comments to the pr, let's see how we go about them!
It looks like the the permissions of the SpeckleServer-folder is the reason sudo was required: Would it be safe to give write access to the folder for non-root users? @didimitrie
It looks like you're trying to install things from a folder you don't have permissions for. These steps just worked on a fresh Debian 9 install:
As root:
curl -sL https://deb.nodesource.com/setup_10.x | bash
to get packages from NodeSourceapt install mongodb redis-server nodejs git
to install thingsadduser speckle
to create a new usersu - speckle
to become the speckle userAs speckle:
git clone https://github.com/speckleworks/SpeckleServer.git
to get the SpeckleServer sourcecd ~/SpeckleServer
npm install
to get dependenciescp .env-base .env
to get base configuration. Edit .env
at this point.cd ~/SpeckleServer/plugins
git clone https://github.com/speckleworks/SpeckleAdmin.git
to get the admin interfacegit clone https://github.com/speckleworks/SpeckleViewer.git
to get the 3D viewercd ~/SpeckleServer
npm start
to start the server on port 3000Note that those steps don't produce a "proper" deployment. You probably want to:
@logan12358 you are right it does look like it is a problem with permissions, but I don't know how it should be resolved in a way that would work for all.
I setup a Ubuntu instance on ec2 and in that case I would still need sudo to follow the steps you describe; even the adduser
only works as sudo adduser
.
Maybe there is some note on deploying the instance that could help avoid the need for sudo
The first steps (under "As root") should be performed with root permissions, either by logging in as root or by using sudo. The steps after that can be performed as the new speckle user without permissions.
The steps performed with root permissions are unavoidable on Debian or Ubuntu, as they involve system-wide installations.
On Fri, Mar 8, 2019, at 12:07 PM, Martin B. Henriksen wrote:
@logan12358 https://github.com/logan12358 you are right it does look like it is a problem with permissions, but I don't know how it should be resolved in a way that would work for all. I setup a Ubuntu instance on ec2 and in that case I would still need sudo to follow the steps you describe; even the
adduser
only works assudo adduser
. Maybe there is some note on deploying the instance that could help avoid the need for sudo— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/speckleworks/SpeckleServer/pull/124#issuecomment-470737643, or mute the thread https://github.com/notifications/unsubscribe-auth/ABI9rqY92rgBA_992otjUm1T9E5V_ghrks5vUZuTgaJpZM4bj2Yi.
updated instructions with inputs from @logan12358 and @didimitrie
closing this as it is superseded by #126
this PR addresses #123 - very small changes to the readme