Please, please, please READ. Lots.
Most of your questions have been answered multiple time in multiple places.
Answering them becomes extremely tedious so don't be surprised at some less than friendly responses if you clearly haven't bothered doing some research. And they will know.
Search has been around for 30+ years. Make use of it.
- Rocket.Chat is a large mature project. It has multiple departments hidden from view with github being the very last bit right at the end. Don't expect any fast answers.
- Github is NOT the primary resource for Rocket.Chat
- Rocket.Chat have an internal tracker. Github is where the code gets sent in the end. Issues are not regularly checked by the team.
- Github issues NEVER get assigned so please don't ask.
- Please don't @ people anywhere - it gets really irritating and you will get muted or ignored. Those who need to know will see.
- Make sure you ask if you can work on an issue - don't waste your own time. If an issue has been triaged as a bug or 'tasked' it will have been referred to the devs for them to fix. Look for another issue to solve.
- Feature requests or apps are a much better area to work on.
- If you decide to work on something then make sure you understand exactly what the problem is first. Many issues are support requests, not bugs that need fixing. Don't waste your valuable time.
- No one is going to sit down and teach you now. This is not school. If you want to learn you need to help yourself.
There are NO simple solutions.
There are lots of answers. Search is your friend.
If you make some effort to educate yourself and ask sensible, well documented questions then people may help.
No one is going to sit down and teach you for free.
Please read all the following. There are some very useful hints tips and links that will help you on your journey.
How to Report Bugs Effectively
How to ask a smart question that will attract attention
Don't be this user:
Rocket chat docs and areas of interest.
Rocket.Chat server feature requests
All of these are answered elsewhere.....
The core code is on github and is MIT licensed. You can take it and do with it as you want under MIT.
You CANNOT use the EE code.
It is likely that in time will ONLY released source code on github will be classified as open source. Any binaries eg docker images will have to be licensed one way or another.
Why?
Because Rocket.Chat needs to stay in business to pay developers and keep building software and no one will pay anywhere near enough volutarily to make that happen.
Tried, failed.
Most issues with building are because people have not read ALL the docs.
There are lots of them and there are lots of issues with information being in say Ubuntu deployment but not in Linux build server. It is why you MUST read everything.
If you clearly state you have read everything but haven't, someone is going to find you out really fast and tell you so quite bluntly. That is why you are asking them for help.....
Don't bother with working on versions less than 7 unless you have a very specific reason.
-
Are you using a supported client? Windows needs WSL + 12Gb to build. Minimum.
-
Are you using the correct version of Node? Needs v14.x for 6.x and v20.x for 7.x
-
Deno You need to install and update deno something like this:
curl -fsSL https://deno.land/install.sh | sh
cp deno from ~/.deno/bin to /usr/bin/deno or add it to your path
Only Deno versions >=1.37.1 and <2.0.0 are supported.
deno upgrade --version 1.43.6
-
Meteor Are you using the correct version of Meteor? It needs Meteor 2.6.x for Rocket.Chat v6.x and Meteor v3.x for Rocket.Chat v7.x
-
Building is slow It takes ages to build. Yup. It is a massive project to build. Get another coffee.
-
It fails.
Use yarn dsv instead of yarn dev
Using a local IP/localhost is fine for developing.
But for production you need to use a domain, https and reverse proxy. The iOS app will not work without it.
A common mistake is to deploy, then use the server locally to login. The system knows if you are entering from a different URL and will try and switch the Root URL to match. That will break things for everyone else.
So DON'T do it.
Once setup ALWAYS use the proper https URL from wherever you login, even if it is on the same host (if you use a headless server you won't make this sort of mistake)