Login to new server as root, then add a deploy user
sudo useradd --create-home deploy
sudo adduser deploy sudo
sudo passwd deployUpdate the password, then
Change the new users default to bash by adding /bin/bash to the end of the last line of /etc/passwd
sudo vim /etc/passwdNow login as that user
Make directory .ssh on the remote server
mkdir .ssh
exitAnd add your ssh key to authorized keys
scp ~/.ssh/id_rsa.pub [email protected]:~/.ssh/authorized_keys
Mi server uses a port different of 22 for SSH, but I do not realize how to specify the port on the command
scp /.ssh/id_rsa.pub [email protected]:/.ssh/authorized_keys
Could you tell me how to specify the ssh port?
Thanks
@samarthmshah I have pretty much exactly the same questions as you. Have you found the answers yet? I found the answers to one of your questions in te comments section of the video:
Jordan Adams: "The reason to opt for a secondary deploy user is purely security. Normally you'd go ahead and root (limit) this user to the app's location on the server. That way if the deploy account is compromised by for example a disgruntled developer, the rest of the server is safe.
The reason for setting up passwordless auth for this deploy user is so that you don't have to enter a password for each deployment. Instead you're authenticating by a private key on your machine."
Hey all.
I'm running a node app but using a server.js file in the root directory. I've gotten to the point where I want to deploy my app, but whenever i run 'fly production' I get the following error:
> error: Forever cannot find process with id: /home/deploy/moshHamedaniNode/server.js
My flightplan.js file starts out like so:
var plan = require('flightplan');
var appName = 'moshHamedaniNode';
var username = 'deploy';
var startFile = 'server.js';
var tmpDir = appName+'-' + new Date().getTime();
...
Finally, the following files are all located in the root directory:
flightplan.js
package.json
server.js
As far as I can tell the appName, username and startFile variables are all named correctly in the flightplan.js file. Can anyone give me some feedback as to why I'm getting this error?
As far as I can tell the appName, username and startFile variables are all named correctly in the flightplan.js file. Can anyone give me some feedback as to why I'm getting this error?
Looks like I was able to fix the issue by changing my flightplan.js file to this:
var appName = 'node-app';
var username = 'deploy';
var startFile = 'server.js';
However, now when I go to my IP address I get the error: This site can’t be reached - refused to connect. Do I still have something wrong in my flightplan.js to keep it from deploying my code to my droplet?
I guess, the advantage of one single deploy user, when you have more than one developer, is that when one developer do a git pull and another developer too, some files might get different ownership settings and we have to fix it with chown. I think our problem can also be fixed with proper group rights. Like to hear comments about this. "Proper group rights VS additional deploy user:
My hostgator server has something called
jailshellwhich I guess does not allow access to thesudocommand:Plus, I don't know why this happens? Is it not linux?
And most importantly, can you please elaborate why would we need an extra user called
deploy? Is there some reason behind it?Thanks Will. You have amazing tutorials.