I understand. However, it's very likely users are the same because almost everyone is connecting via external provider (GitHub mainly)
Install error: "no such file or directory"
I've been following the @Ted tutorial as seen here:
I'm having an issue at the point where I need to fetch the nodebb files ("no such file or directory"):
**testuser@forum:~$ git\ clone\ -b\ v0.6.x\ https://github.com/NodeBB/NodeBB.git\ nodebb
-bash: git clone -b v0.8.x https://github.com/NodeBB/NodeBB.git nodebb: No such file or directory
I even tried replacing the 0.6.x with 0.8.x but it did not help.
I am a total noob at this, and have been trying to install nodebb on DigitalOcean for a few days now.
Any help offered would be greatly appreciated
This tutorial already seems outdated. I suggest you to follow official NodeBB document depending on your OS.
If I could install using the official docs I wouldn't be searching for alternative methods. For total noobs, nodebb has got to rank as the most difficult forums install I've ever had to endure.
@ron_jeremy Let's start from the beginning. Given the tutorial you tried to follow, you are using Ubuntu, right ? If you did not manage to install with two different tutorials, may be the problem is somewhere else.
From what you say, the problem occurs when you try to fetch NodeBB with Git. Could you please post here the command you used to do it ? And format your output so we can read it easily, I have hard time to read the one you posted.
For total noobs, nodebb has got to rank as the most difficult forums install I've ever had to endure.
It's also the newest, so there are some rough spots to iron out...
@hukadan Hello and thanks for offering to help!
I started with a fresh install (droplet on DigitalOcean) of Ubuntu x64 then followed the @Ted tutorial. Everything was going great until I got to the part where I had to fetch the nodebb files. See my original post to see the command I used and where I am stuck. And, you can reference that on the tutorial I was following to see what step I'm on.
@ron_jeremy Yep. I read that already. But if I try the command given on the tutorial, it works for me. So I had the impression you typed something else. So, just to be sure, you just did :
% git clone -b v0.8.x https://github.com/NodeBB/NodeBB.git nodebb
And it did not work ?! Also, I tried to reproduce the "no such file or directory" on my system but could not. On my system, this command gives me :
% git clone -b v0.8.x https://github.com/NodeBB/NodeBB.git nodebb Cloning into 'nodebb'... remote: Counting objects: 84932, done. remote: Compressing objects: 100% (222/222), done. remote: Total 84932 (delta 111), reused 0 (delta 0), pack-reused 84710 Receiving objects: 100% (84932/84932), 25.97 MiB | 1017.00 KiB/s, done. Resolving deltas: 100% (62000/62000), done. Checking connectivity... done.
Of course, same result with
v0.6.x. If you cannot achieve that you clearly have a problem but it is not related to NodeBB.
jarey last edited by
@ron_jeremy I'm seeing escaping backslashes in your original command, you shouldn't need those when you type the 'git clone' command
You don't actually need the last argument, you can just clone with the command:
git clone https://GitHub.com/Nodebb/nodebb.git
I think if he clone the repo that way, he would be working on master branch by default. Instead using the -b 0.8.x he is setting the 0.8.x branch to work with. So it would affect the installation, so master its not the stable branch.
But you are right, he could simply type the command you suggested, and then switch to 0.8.x branch.
I am up and running! I am pretty sure I figured out what the issue was. Oh man, this is embarrassing...
So, I used the Terminal on my Mac to ssh into the server. However, what I didn't know is that I must have somehow lost the connection either from being away from the computer for too long and/or letting the computer go to sleep. So, when I would go back to continue with the tutorial I was no longer connected to the server, and thus when I was running the command I would see the error. I dunno, I think that's what happened. Anyway, that's my story and I'm sticking to it!