Day 3
I have successfully run rocket.chat on my local machine (macOS).
Here’s what & how I followed the steps to accomplish this:
prerequisites: install homebrew, yarn
Phase1: Fork & Clone Repo
Step1: Fork https://github.com/RocketChat/Rocket.Chat
Step2: Clone https://github.com/<your-username>/Rocket.Chat
Step3: cd Rocket.Chat
git remote add upstream https://github.com/RocketChat/Rocket.Chat.git
Phase2: Install Node.js
Step4: brew install nvm (install node version manager)
Step5: cd Rocket.Chat
cat package.json | grep -A4 engines | grep node
Step6: nvm install x.x.x (replace with node version [step5])
Step7: node -v (check node version)
Phase3: Setup Deno
(I used homebrew, but it installs the latest version and sets up the environment variable automatically but we have to follow the manual step using curl to set up the rocket.chat supported version)
Step8: cat .tool-versions | grep deno
Step9: curl -fsSL https://deno.land/install.sh | sh -s v1.x.x (replace x.x with required version, let’s say 1.43.5 in my case)
Get Shashank Kumar’s stories in your inbox
Join Medium for free to get updates from this writer.
Step10: deno — version (check if it has installed successfully)
but here’s the catch, we have to manually fix the environment variable, else it’ll show errors like command not found.
Open terminal and type nano ~/.zshrc or sudo nano ~/.zshrc
Add the following lines:
export DENO_INSTALL=”$HOME/.deno”
export PATH=”$DENO_INSTALL/bin:$PATH”
now deno — version will successfully show the version
Phase4: Install Meteor
Step11: cat apps/meteor/.meteor/release (confirm the meteor version)
Step12: curl https://install.meteor.com/\?release\=x.x | sh (install meteor replacing x.x with the meteor version from step11)
Step13: meteor — version (verify if it has installed successfully)
Phase4: Run the Rocket.Chat project
Step14: yarn
Step15: yarn build
Step16: yarn dev (for RAM>16GB) or yarn dsv (for RAM <16GB)
The first build can take ten or more minutes. Subsequent dev builds will take lesser time. Once it is finished, check your terminal for a message confirming the successful deployment. The local server will now be running on http://localhost:3000.
And we are good to go with exploring and editing files.
