Taiga deploy scripts
Scripts for initial deployment of Taiga services.
It installs:
WARNING: these scripts are in an alpha state
http://taigaio.github.io/taiga-doc/dist/setup-alternatives.html#setup-taiga-scripts
Taiga has a mailing list. Feel free to join it and ask any questions you may have.
To subscribe for announcements of releases, important changes and so on, please follow @taigaio on Twitter.
I have followed the instructions and everything works fine, until after some time using taiga it becomes incredibly slow and this is the only log that says something about it.
Nginx:
2018/09/18 19:33:49 [error] 1338#1338: *354 upstream timed out (110: Connection timed out) while reading response header from upstream, client: x.x.x.x, server: _, request: "GET /api/v1/resolver?milestone=sprint-1-1&project=zalce-sushi-itto HTTP/1.1", upstream: "http://127.0.0.1:8001/api/v1/resolver?milestone=sprint-1-1&project=zalce-sushi-itto", host: "xxxxxxxxxx.com", referrer: "http://xxxxxxxxxxx.com/zalce-sushi-itto/taskboard/sprint-1-1"
I am developing a project where my backend is done in node.js and my interface in ionic.
I am managing a mongoDB database, when I run the project from the web and log in, it takes the data correctly, but when I try to run the project from a mobile device I have the following problem.
OPTIONS http: // localhost: 3800 / net :: ERR_CONNECTION_REFUSED
ERROR
HttpErrorResponse {headers: HttpHeaders, status: 0, statusText: "Unknown Error", url: "http://localhost:3800/api/login", ok: false, …}
error: ProgressEvent {isTrusted: true, lengthComputable: false, loaded: 0, total: 0, type: "error", …}
headers: HttpHeaders {normalizedNames: Map(0), lazyUpdate: null, headers: Map(0)}
message: "Http failure response for http://localhost:3800/api/login: 0 Unknown Error"
name: "HttpErrorResponse"
ok: false
status: 0
statusText: "Unknown Error"
url: "http://localhost:3800/api/login"
__proto__: HttpResponseBase
I did my backend in Node.js and use mongoDb as a database, this is the code used.
import mongoose from 'mongoose';
import express from 'express';
import http from 'http';
import app from '../rutas/app';
export default class Server {
port: number = Number( process.env.PORT ) || 3800;
servicio = require ('http').createServer(app);
connect(){
mongoose.Promise = global.Promise;
mongoose.connect('mongodb://localhost:27017/DB_mongoDB', { useNewUrlParser: true, useCreateIndex: true })
.then(() => {
this.servicio.listen(this.port);
});
})
.catch(err => console.log(err));
}
}
Try changing the localhost for my iP but the same error comes up.
The information on my iP is placed in my frontend in my environment folder as follows.
After
export const environment = {
production: true,
url: 'http://localhost:3800'
};
Before:
export const environment = {
production: true,
url: 'http://181.12.32.422:3800'
};
But it does not work.
I appreciate the help you can give me.
Hi! I'm not sure if this is the best place to ask.
Is that possible to add snap as a format to deploy taiga.
I would like to use taiga on my rasbpi with snappy ubuntu core.
Thx.
Hi,
I am getting an error similar to the one that pawel2105 had on issue #5 . I am trying to follow here and apply the fix that niwibe suggested but there is no taiga-front/app/config/main.coffee file nor taiga-front/app/config/ directory!
I am using a fresh installation of ubuntu 14.0.4 on a digital ocean VPS on which i just installed Git and everything else is default. i am also using a sudo user called taiga
I simply can not make any APIs calls at all. here is what i get in my browser's console, any help?
Initialize navigation urls
jquery.js:10 Initialize api urls
jquery.js:10 Using the default logging exception handler.
jquery.js:10 Initialize resources
jquery.js:10 Initialize application
jquery.js:10 Analytics: no acount id provided. Disabling.
jquery.js:9 GET http://digitaloceanIPAddr:8000/api/v1/projects 502 (Bad Gateway)
app.js:2 FAIL
Hey guys,
I tried to install taiga on a vm, which fulfills the requirements of taiga. Everything is actually working, but when I try to log in for the first time as admin with 123123 as the password, I'll get the Bad Gateway Error. Did somebody experience the same thing and has an idea how to solve this? Any help is highly appreciated!
The config file for the taiga frontend (conf.json) created in setup-frontend.sh is moved to dist/js/.
Unfortunately this is an unvalid path.
The correct path should be dist/
I've run the server installation on a clean Ubuntu instance on EC2 (nothing installed on it, except git).
The installation runs fine without any issues, but I end up with just an error page.
I tried ubuntu 14.04.1 image and I had some issues with locales (because of that Postgresql doesn't start) but after locale fix and when postgresql is up I still cannot make it work entirely. It looks like something is missing in DB initialization, cos I can log in to the Taiga, however there is no admin user, but I don't have any templates. When I try to create a project I see
taiga.projects.models.DoesNotExist: ProjectTemplate matching query does not exist
Any idea what went wrong?
I've run the production install script on a standard DigitalOcean droplet, where the default user is root (Yes I know this is a bad idea, but it was a quick and dirty install to see if I could get it working).
The script finished without error, but it wrote the nginx sites file incorrectly. Instead of the correct home directory for the root user (/root) it used /home/root.
It's not a big issue because I don't think anyone would really be running this script as root if they were going to use the server properly, but it might be worth fixing for people like me who just wanted something up quickly to test it out.
How will you manage the port to 18.04 with another repo or this one with option to choose within 1604 and 1804??
I am using a fresh Ubuntu 14.04 image in AWS. I clone taiga-scripts using a "taiga" user account and execute setup-server.sh successfully. I can access the website, but when attempting to login using admin/123123, I receive the following error:
Oops, something happened...
According to our Oompa Loompas, your username/email or password are incorrect.
Registration also fails with the following error:
"Something happened and our Oompa Loompas are working on it."
I reached the same results when following the manual installation process for a production environment.
Hello,
Scripts tries to install postgresql 9.3 on my server but I have postgresql 9.4 (I'm on jessie).
Bests !
I was installing taiga on digitalocean droplet on debian testing. the script gave a warning that postgresql-9.3 don't exist. I think the script has to be update with 9.4.
So in relation to my other issue I raised in taiga-front I found that the problem is the hostname setting that was used during the taiga-scripts process (it's the only thing I can find with the setting "localhost:8000" I have no idea where this file is actually set so I have a two part question:
Would I lose everything if I re-ran taiga-scripts with the proper hostname?
Where does this hostname get set? I have already tried the config file and added "url" to it and it didn't help. I just want every instance of "localhost:8000" to be changed to "team.example.com"
Hello guys,
I have two things to say/ask.
Currently I am running Taiga 3.1. The default upgrade steps says to checkout the latest stable release. Which means can i directly upgrade Taiga to 4.2 from 3.1 ? Need some clarity on this.
I installed Taiga 4.2 in a new machine. Exported the DB from my old Taiga 3.1 server and restored it in the newly installed 4.2 machine. I logged into postgreSQL and verified that all the databases are imported successfully, but i don't see any of projects its just a clean page without projects. When i login to the taiga.devops.com/admin/ page it throws error. Attached the traceback.
Environment:
Request Method: POST
Request URL: http://taiga.devops.com/admin/login/?next=/admin/
Django Version: 1.11.22
Python Version: 3.6.3
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.admin',
'django.contrib.staticfiles',
'django.contrib.sitemaps',
'django.contrib.postgres',
'taiga.base',
'taiga.base.api',
'taiga.locale',
'taiga.events',
'taiga.front',
'taiga.users',
'taiga.userstorage',
'taiga.external_apps',
'taiga.projects',
'taiga.projects.references',
'taiga.projects.custom_attributes',
'taiga.projects.history',
'taiga.projects.notifications',
'taiga.projects.attachments',
'taiga.projects.likes',
'taiga.projects.votes',
'taiga.projects.milestones',
'taiga.projects.epics',
'taiga.projects.userstories',
'taiga.projects.tasks',
'taiga.projects.issues',
'taiga.projects.wiki',
'taiga.projects.contact',
'taiga.projects.settings',
'taiga.searches',
'taiga.timeline',
'taiga.mdrender',
'taiga.export_import',
'taiga.feedback',
'taiga.stats',
'taiga.hooks.github',
'taiga.hooks.gitlab',
'taiga.hooks.bitbucket',
'taiga.hooks.gogs',
'taiga.webhooks',
'taiga.importers',
'djmail',
'django_jinja',
'django_jinja.contrib._humanize',
'sr',
'easy_thumbnails',
'raven.contrib.django.raven_compat']
Installed Middleware:
['raven.contrib.django.middleware.SentryMiddleware',
'taiga.base.middleware.cors.CoorsMiddleware',
'taiga.events.middleware.SessionIDMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware']
Traceback:
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
64. return self.cursor.execute(sql, params)
The above exception (column users_user.uuid does not exist
LINE 1: ..._user"."last_login", "users_user"."is_superuser", "users_use...
^
HINT: Perhaps you meant to reference the column "users_user.id".
) was the direct cause of the following exception:
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/core/handlers/exception.py" in inner
41. response = get_response(request)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/core/handlers/base.py" in _legacy_get_response
249. response = self._get_response(request)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
187. response = self.process_exception_by_middleware(e, request)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/core/handlers/base.py" in _get_response
185. response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
57. response = view_func(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/admin/sites.py" in login
393. return LoginView.as_view(**defaults)(request)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/views/generic/base.py" in view
68. return self.dispatch(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in _wrapper
67. return bound_func(*args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/views/decorators/debug.py" in sensitive_post_parameters_wrapper
76. return view(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in bound_func
63. return func.__get__(self, type(self))(*args2, **kwargs2)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in _wrapper
67. return bound_func(*args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in _wrapped_view
149. response = view_func(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in bound_func
63. return func.__get__(self, type(self))(*args2, **kwargs2)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in _wrapper
67. return bound_func(*args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/views/decorators/cache.py" in _wrapped_view_func
57. response = view_func(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/decorators.py" in bound_func
63. return func.__get__(self, type(self))(*args2, **kwargs2)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/auth/views.py" in dispatch
90. return super(LoginView, self).dispatch(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/views/generic/base.py" in dispatch
88. return handler(request, *args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/views/generic/edit.py" in post
182. if form.is_valid():
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/forms/forms.py" in is_valid
183. return self.is_bound and not self.errors
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/forms/forms.py" in errors
175. self.full_clean()
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/forms/forms.py" in full_clean
385. self._clean_form()
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/forms/forms.py" in _clean_form
412. cleaned_data = self.clean()
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/auth/forms.py" in clean
187. self.user_cache = authenticate(self.request, username=username, password=password)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/auth/__init__.py" in authenticate
70. user = _authenticate_with_backend(backend, backend_path, request, credentials)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/auth/__init__.py" in _authenticate_with_backend
116. return backend.authenticate(*args, **credentials)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/auth/backends.py" in authenticate
18. user = UserModel._default_manager.get_by_natural_key(username)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/contrib/auth/base_user.py" in get_by_natural_key
48. return self.get(**{self.model.USERNAME_FIELD: username})
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/manager.py" in manager_method
85. return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/query.py" in get
374. num = len(clone)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/query.py" in __len__
232. self._fetch_all()
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/query.py" in _fetch_all
1121. self._result_cache = list(self._iterable_class(self))
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/query.py" in __iter__
53. results = compiler.execute_sql(chunked_fetch=self.chunked_fetch)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/sql/compiler.py" in execute_sql
899. raise original_exception
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/models/sql/compiler.py" in execute_sql
889. cursor.execute(sql, params)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
79. return super(CursorDebugWrapper, self).execute(sql, params)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/raven/contrib/django/client.py" in execute
114. return real_execute(self, sql, params)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
64. return self.cursor.execute(sql, params)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/utils.py" in __exit__
94. six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/utils/six.py" in reraise
685. raise value.with_traceback(tb)
File "/home/taiga/.virtualenvs/taiga/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
64. return self.cursor.execute(sql, params)
Exception Type: ProgrammingError at /admin/login/
Exception Value: column users_user.uuid does not exist
LINE 1: ..._user"."last_login", "users_user"."is_superuser", "users_use...
^
HINT: Perhaps you meant to reference the column "users_user.id".
After a fresh install with taiga-scripts (production or devel) on a virtualbox clean ubuntu 14.04 machine,
the login page is followed by an error page.
The firefox console gave me :
Blocking of a multi- query origins (Cross - Origin Request) : the " Same Origin " policy does not refer to the remote resource on http: // localhost: 8000 / api / v1 / auth . Reason: the header CORS "Access -Control- Allow- Origin " is missing .
I check the local connexion on the machine (with a direct api request) the user admin/123123 is existing.
circusctl status
gave me
circusd-stats: active
taiga: active
I precise that I already do this 6 month before (taiga 1.8) and everything was fine
For orchestrate the deploy, make an ansible playbook.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package postgresql-server-dev-9.3
E: Couldn't find any package by regex 'postgresql-server-dev-9.3'
touch: cannot touch ‘/home/bitnami/.setup/postgresql’: No such file or directory
touch: cannot touch ‘/home/bitnami/.setup/buildessential’: No such file or directory
~ ~/taiga-scripts
After installing using the scripts the landing page loads fine from the VM IP but I can't register new users and therefore can't login to test the rest of the app. Am I missing anything?
So, I have my configuration of Taiga running on Docker containers, and I want to share.
https://github.com/douglasmiranda/docker-taiga
I know this is not the best place, but you can close the issue, and it will be here so people can search and find.
Related: #54
In the setup-buildessentials.sh the cairo package has been replaced by libcairo2-dev.
Also the touch "/.setup/postgresql" and the "/.setup/buildessentials" throws an error. A "mkdir ~/.setup" command should be called first.
I installed taiga by taiga-scripts, but I'm having some problems with backend.
http:///api/v1/projects Failed to load resource: net::ERR_CONNECTION_REFUSED
And I want to completely uninstall taiga. How do I uninstall taiga?
E: Unable to locate package libzmq3-dev
[APT-GET] Installing package nodejs...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package nodejs
[APT-GET] Installing package npm...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package npm
./scripts/setup-nodejs.sh: line 6: -2: substring expression < 0
[APT-GET] Installing package python3-pip...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package python3-pip
[APT-GET] Installing package python-pip...
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package python-pip
[APT-GET] Installing package virtualenvwrapper...
Reading package lists...
Hey,
I'm trying to setup Taiga using Taiga-Scripts in a Docker Container using a Dockerfile.
Dockerfile:
FROM ubuntu:16.04
MAINTAINER me
doing apt things
RUN echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections
RUN echo "Acquire::http::No-Cache true;" >> /etc/apt/apt.conf
RUN echo "Acquire::http::Pipeline-Depth 0;" >> /etc/apt/apt.conf
RUN apt-get update
RUN apt-get install -y git sudo apt-utils
create taigausr, add to sudoers, w/ passwd
RUN useradd -ms /bin/bash taigausr
RUN echo "taigausr ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
switch to taigausr, taiga-scripts will run in normal user context (elevated by sudo)
USER taigausr
WORKDIR /home/taigausr
setup taiga with official taiga-scripts from github
RUN git clone https://github.com/taigaio/taiga-scripts.git
WORKDIR taiga-scripts/
RUN ./setup-server.sh
EXPOSE 80 443
COPY entypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
ENTRYPOINT ["/entrypoint.sh"]
CMD ["/entrypoint.sh"]
everything seems to be fine
but when the script try to invoke
python manage.py migrate --noinput
nothing happend.
I know, that docker-script is in alpha state, but having a fresh setup in my Docker Environment would be nice.
I dont know much abou python and virtualenv, but I think the build tty is not able to do this virtualenv thing?!
you can see the output here ( http://pastebin.com/iW0LyTv7 )
when I setup everything manual, everything works fine.
sorry for my english (maybe also sorry for the noobie question, it's my first try to create a Dockerfile)
Thanks
p.s.: Memory could not be an issue, 16GB on this machine..
o/
On https://github.com/taigaio/taiga-scripts/blob/master/scripts/setup-nginx.sh#L84
Your writing your configuration file in sites-available/default, it may be dangerous, someone may have changed this file, you may use site-available/taiga instead.
Bests,
Hi, all.
What are Default user and pass for PostgreSQL DB using Taiga Sctipts?
I've tried user postgres pass postgres but got failed.
I want to integrate Taiga with Metabase.
Implement a Dockerfile and a compose with a container for backend and other one for frontend.
So, I think it would be nice to create a repository: /awesome-taiga so we can list components, deploy configurations, and everything related to taiga.
It works in local
But when I'm connecting via IP, it seems that it doesn't connect to the data base, (it does nothing when I click to sign up) and I've got this error : http://172.21.184.100:8000/api/v1/auth 502 (Bad Gateway)
Here is my local.py file:
from .common import *
MEDIA_URL = "/media/"
STATIC_URL = "/static/"
# This should change if you want generate urls in emails
# for external dns.
SITES["front"]["domain"] = "localhost:8000"
DEBUG = True
PUBLIC_REGISTER_ENABLED = True
DEFAULT_FROM_EMAIL = "[email protected]"
SERVER_EMAIL = DEFAULT_FROM_EMAIL
#EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"
#EMAIL_USE_TLS = False
#EMAIL_HOST = "localhost"
#EMAIL_HOST_USER = ""
#EMAIL_HOST_PASSWORD = ""
#EMAIL_PORT = 25
thanks
Hello guys,
Thanks for the great work, It works perfectly.
Here is my question: After install, how can I do the upgrade?
Is it just "git pull" in each project folder?
I tried to use the install scripts on a fresh vm running ubuntu server 14.04 and I tried using docker (guide in #3).
But both result in a page stating:
"Something happened and our Oompa Loompas are working on it.
Try reloading again soon."
I also tried to look for ways to read any logs that Taiga produces to see what the error is, but I cannot seem to find any. If you could point me in the right direction I could either fix it myself or give a better bug report.
I really want to try Taiga as it seems to fit my needs perfectly. Any help would be appreciated.
E: Unable to locate package python3-pip
./scripts/setup-python.sh: line 4: pip3: command not found
/root/.virtualenvwrapper-conf.sh: line 5: /root/.local/bin/virtualenvwrapper.sh: No such file or directory
I am not sure if this is intentional or not. After the script is done running, it does not generate a local.py
I have it up and running but I do not have a username and password to login with. I used the setup-server.sh on ubuntu 14.04
Here is the install log https://pastebin.com/kp5QZ5Gt
With a fresh vagrant install, I see the following error:
Anybody interested porting Taiga to a docker image ?
My previous issue was closed prematurely here: #40
I am using a fresh Ubuntu 14.04 image in AWS. I clone taiga-scripts using a "taiga" user account and execute setup-server.sh successfully. I can access the website, but when attempting to login using admin/123123, I receive the following error:
Oops, something happened...
According to our Oompa Loompas, your username/email or password are incorrect.
Registration also fails with the following error:
"Something happened and our Oompa Loompas are working on it."
I reached the same results when following the manual installation process for a production environment.
I am receiving the following error in the Javascript console:
OPTIONS http://localhost:8000/api/v1/auth net::ERR_CONNECTION_REFUSED
I attempted to change "localhost" to the server's IP address via local.py, and I ran regenerate.sh; neither helped to resolve the error.
I verified port :8000 is listening.
In your email you're giving a: http://localhost:9001, seems wrong to me.
It a no brainer, can send a PR
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.