Giter Club home page Giter Club logo

yourpeer.nyc's Introduction

These instructions are for Ubuntu Linux 22.04

Open a new issue and request to be onboarded

Open a new issue with the following:

  1. Your Github account name
  2. Your IP address

Jake will send you an envfile called .env.remote.dev on slack, which contains credentials to login to the RDS test database, and add your IP address to the AWS whitelist. Put .env.remote.dev in streetlives-api project directory (after cloning the project - see below).

Note: In the future, we will provide seed data in the repository so that we can eliminate this step.

Fetch all of the source code

mkdir -p ~/workspace/streetlives
git clone [email protected]:streetlives/yourpeer.nyc.git
git clone https://github.com/streetlives/streetlives-api
git clone [email protected]:streetlives/streetlives-web.git

Setup local postgres

Install Postgres

sudo apt install postgresql postgresql-14-postgis-3

Setup postgres for local login with password authentication

Make sure you can login to your local postgresql database using a password for authentication. Something like this:

local   all             streetlives                                md5

Create the Streetlives user, streetlives database, and the test database

Login to database as administrator. Here's how I do this on ubuntu:

sudo bash
su postgres
psql

By default, in ubuntu, this will allow you to login to the database without a specifying a password.

Then, as postgres user, from psql shell:

create user streetlives with password 'password';
create database streetlives_prod with owner streetlives;

Logout and log back into the new database with user streetlives:

psql -d streetlives_prod

create extension postgis  schema public;

Load a copy of the data into local Streetlives database

As your user (not postgres user), cd in project directory streetlives-api. You will dump a copy of the test database, then restore it to your local:

source .env.remote.dev
./scripts/backup.sh
sed -i 's/devuser/streetlives/g' prod-`date +%F`.sql
source .env.local
./scripts/restore-from-sql.sh

Run local applications

npm install
source .env.local
PORT=3001 npm start

Open http://localhost:8000/

nvm use v16
npx yarn install
REACT_APP_API_URL=http://localhost:3001 npm start

Visit http://localhost:3000/find and verify that the locations load (blue pins appear on the map).

yourpeer.nyc:

Put this in the .env file in your root directory:

DB_USER_AWS=streetlives
DB_PASSWORD_AWS=password
DB_NAME_AWS=streetlives_prod
DB_HOST_AWS=localhost
DB_PORT_AWS=5432

Then run:

python -m venv venv
source venv/bin/activate
pip install -r requirements.txt
GO_GETTA_PROD_URL=http://localhost:3001 python manage.py runserver

Visit http://localhost:8000/locations and verify that the locations load (yellow pins appear on the map).

Tools

Squirrel SQL

~/.local/squirrel-sql-4.2.0/squirrel-sql.sh

Connect to your local database with:

URL: jdbc:postgresql:streetlives_prod
Username: streetlives
Password: password

Deployment

Push to env/test branch to deploy to https://test.yourpeer.nyc/

Push to env/live branch to deploy to https://yourpeer.nyc/

Contributing

Please open a pull request. Ensure that each source file includes the correct license header template, like this:

Copyright (c) 2024 Streetlives, Inc., [your name]

Use of this source code is governed by an MIT-style
license that can be found in the LICENSE file or at
https://opensource.org/licenses/MIT.

yourpeer.nyc's People

Contributors

jbeard4 avatar

yourpeer.nyc's Issues

[Action required] Deprecation of Amazon RDS M4, R4, and T2 database instance types on MySQL, MariaDB, and PostgreSQL

Hello,

You are receiving this notification because we have identified that you have one or more Amazon RDS for MySQL, MariaDB, and PostgreSQL database instances running on M4, R4, and T2 instance types. You can disregard this notification if you are no longer running these database instances or have already upgraded them to new generation instance types.

In June 2023, Amazon RDS announced the deprecation of M4, R4, and T2 database instance types on Amazon RDS for MySQL, MariaDB, and PostgreSQL.

Starting March 11, 2024, Amazon RDS will begin disabling the creation of Amazon RDS for MySQL, MariaDB, and PostgreSQL database instances running on M4, R4, or T2 instance types. And starting on June 1, 2024, Amazon RDS will make best effort to begin upgrading MySQL, MariaDB, and PostgreSQL database instances running on M4, R4, or T2 instance types to equivalent size M5, R5, or T3 newer generation instance type, if available.

We strongly recommend that you migrate your existing Amazon RDS database instances running M4, R4, and T2 instance types to newer generation instance types before May 31, 2024. You may use the following recommendation:

  • Upgrade M4 instance to M5 instance or higher
  • Upgrade R4 instance to R5 instance or higher
  • Upgrade T2 instance to T3 instance or higher

A list of your impacted resource(s) can be found in the 'Affected resources' tab of your AWS Health Dashboard.

How will my Amazon RDS Reserved Instances (RIs) be impacted?

If you upgrade your instance types that are receiving a billing benefit from RIs, the RIs will no longer cover the database instances and you may see additional on-demand charges on your bill. To avoid this, we recommend the following:

  • If you have no RIs, or if your RIs have expired, you should migrate your instances at the earliest convenience.
  • If you have active RIs which expire before June 1, 2024, you should wait for the RIs to expire and then migrate your instances. You can then purchase new RIs for the upgraded instance types.
  • If you have RIs which will be active after May 31, 2024, you should not migrate your instances. RDS will automatically upgrade database instances and RIs that are active after May 31, 2024.

To seamlessly upgrade your database’s instance type or engine version, you may consider using RDS Blue Green Deployments [1] for RDS MySQL and RDS PostgreSQL. If you have any questions or concerns, please reach out to AWS Support [2].

[1] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html
[2] https://aws.amazon.com/support

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210


Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_PLANNED_LIFECYCLE_EVENT/AWS_RDS_PLANNED_LIFECYCLE_EVENT_130801b45ba1a22f4066170dcce3b2ec80fe3a5f7b3951817494479a0543f765&eventTab=details

Use a period as the decimal separator for Spanish translation

In the US they use periods before a decimal - seems most central american countries do too, whatever the case, we should not mix periods and commas ahead of the decimal, in the screen shot the first location uses a decimal while all others use a comma - and it seems the comma is incorrect if we assume most Spanish speakers in the US are from Central America. So let's remove the distance numbers from the Spanish translation.
Also, not sure what's going on with the first location - is it curtailing the region ("Brookl...") cos the number of characters in the line is long, or cos the heading takes up three lines or something else? none of the other locations curtail the region.

Screenshot_20231215-103956

[Action required] Update Your Amazon RDS and Amazon Aurora SSL/TLS Certificates by August 22, 2024

Hello,

[AWS Health may periodically trigger reminder notifications about this communication.]

You are receiving this message because your AWS Account has one or more Amazon RDS, or Amazon Aurora database instances in the US-EAST-1 Region using a SSL/TLS Certificate that is expiring on August 22, 2024.

A list of your affected resources can be found in the 'Affected resources' tab of your AWS Health Dashboard.

This is a follow-up notification for SSL/TLS CA certification expiration. If you believe you have already finished this work and still received this email, it is likely because you created new instances using the 2019 Certificate Authority (CA). After January 25, 2024 all newly created instances that do not explicitly specify a different CA will use the ‘rds-ca-rsa2048-g1’ CA. For information on setting an account level CA override, see the modify-certificates API documentation [1].

If your applications connect to these instances using the SSL/TLS protocol, you will need to take action before August 22, 2024 to prevent connectivity failures to your existing database instances. Even if you do not currently use SSL for your connections, you could still be affected if your databases server certificate expires, so we still recommend updating your CA.

To protect your communications with your database instances, a CA generates time-bound certificates that are checked by your database client software to authenticate any database instance before exchanging information. Following industry best practices, AWS renews the CA and creates new certificates on a routine basis to ensure customer connections are properly protected for years to come. The current CA in the US-EAST-1 Region will expire on August 22, 2024. Before this date you will need to update your DB server certificate. The following is the general process to do this:

First, update your application clients with the new certificate, if your application client is using a trust store then add the new CA certificates into the trust stores of your client applications. RDS provides download links to the CA certificates in our User Guide [2]. For more detailed instructions on updating the trust stores on your client application see our documentation [3].

Second, update the certificate on all your affected database instances to one of the newly issued CAs. ‘rds-ca-rsa2048-g1’ is the default recommended CA because there is no algorithm change. The other CAs use new key algorithms so it could require more testing of your client setup to ensure compatibility. For more information on the new CAs see our documentation [4].

Third, if you want to use a different CA than the default ‘rds-ca-rsa2048-g1’, you will need to set an account level CA override so your new instances will use the CA of your choice. To do this a modify-certificates API is available that will allow you to override the default CA on newly created database instances to either the old or one of the new CAs. This override will only apply while the CA you are overriding to is valid. To use this API you will need to be running the AWS CLI version 1.17 or later. For more information see the modify-certificates API documentation [1]. There is also a describe-certificates API [5], that will indicate your current default CA override if you have one set. To set a specific CA during instance creation use the ca-certificate-identifier option on the create-db-instance API to create a DB instance with a specific CA. For more information, see the create-db-instance API documentation [6].

For more detailed instructions on how to perform these updates, please see the Amazon RDS instances [7] and Amazon Aurora instances [8] documentation.

Please be aware of the following timeline:

  1. As soon as possible - You should update your client trust store, then you can update your instances server certificate to one generated by one of the new CAs.

  2. After January 26, 2024 - any new database instances default to using the ‘rds-ca-rsa2048-g1’ certificate. If you wish for new instances to use a different certificate, you can specify which certificate to use with the AWS console or the AWS CLI. For more information, see the create-db-instance API documentation [6].

  3. After August 22, 2024 - ‘rds-ca-2019’ will expire. You will need to take action before August 22, 2024, to prevent connectivity failures to your existing database instances.

For more information see our blog [9], and if you have questions or concerns, please contact AWS Support [10].

[1] https://docs.aws.amazon.com/cli/latest/reference/rds/modify-certificates.html
[2] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions
[3] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL-certificate-rotation.html#UsingWithRDS.SSL-certificate-rotation-updating
[4] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.RegionCertificateAuthorities
[5] https://docs.aws.amazon.com/cli/latest/reference/rds/describe-certificates.html
[6] https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html
[7] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL-certificate-rotation.html
[8] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.SSL-certificate-rotation.html
[9] https://aws.amazon.com/blogs/aws/rotate-your-ssl-tls-certificates-now-amazon-rds-and-amazon-aurora-expire-in-2024/
[10] https://console.aws.amazon.com/support/home

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210


Reference: https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_PLANNED_LIFECYCLE_EVENT/AWS_RDS_PLANNED_LIFECYCLE_EVENT_255bb7760d2537b4b9f0853eecbbb83aed3abceb9977a7fc1c06b04f2d012845&eventTab=details

Check on time translation

Seeing that the "to" between times is being translated, wondering how that's working in chinese and other pictographic languages. Perhpas the time format needs revisting - I recall simplifying the day/time was something we wanted to to so it might be e.g., "Mon-Fri 10-1"
Screenshot_20231214-194836

New events for Google Analytics

Can we track events when users:

  • Click on "get directions"
  • Click on a phone number link
  • Click on a service provider website link
  • Select and copy information from a location page
  • Uses search

Let me know if there's any questions about the event definitions

Add social media logos to YourPeer

Add logos for tiktok, instagram and facebook for @yourpeer.nyc

Suggest they also go on the menu as well as the usual footer location.

Bottom of page is cut off

The bottom of the page is cut off on one participant’s phone. They can’t see “View list”, “View map” or the button to apply filters unless they scroll.

This participant is using Samsung Galaxy S21 Ultra, Android 13 and Duck Duck Go. I tried Duck Duck go on my iPhone and it was fine.

image (16)
image (15)
image (17)

Modal inviting GoGetta users to use YourPeer

Let's encourage users to click into YourPeer - not turning GoGetta off till we have a way for specialists to see a preview of Yourpeer content, but not wanting service-seeking users on their FE.
Please design a pop-up for the homepage and map page that we can implement asap

[Action Required] AWS Elastic Beanstalk Node.js 14 on Amazon Linux 2 platform branches retire on September 30, 2024

Hello,

AWS Elastic Beanstalk is informing you that platform branches [1] based on Node.js 14 on Amazon Linux 2 will retire on September 30, 2024. This is to ensure that our customer's Elastic Beanstalk environments are aligned with the most current support offered by AWS.

  • What does retire mean, and what will happen after September 30, 2024?

Starting on September 30, 2024, retired platform branches will no longer be available for new environments on Elastic Beanstalk. Customers can continue to operate existing environments running on retired platform branches, but these branches will no longer be managed and supported by Elastic Beanstalk. For more information, see Elastic Beanstalk platform support policy [2] in the AWS Elastic Beanstalk Developer Guide.

  • What do I need to do now?

You have until September 30, 2024, to upgrade your Elastic Beanstalk environments configured on platform branches running on Node.js 14 on Amazon Linux 2. We strongly recommend that you start planning your migration to one of the Node.js platforms, which are current and fully supported:

  • Node.js 18 AL2
  • Node.js 18 AL2023
  • Node.js 20 AL2023
  • Which of my Elastic Beanstalk environments are impacted?

A list of your affected Beanstalk environments is available in the 'Affected resources' tab of your AWS Health Dashboard.

You can also use the "AWS CLI describe-environments" command to display a filtered list of all environments that are configured with Node.js 14 on Amazon Linux 2. See the following example command:

aws elasticbeanstalk describe-environments --region us-east-1 --query "Environments[?PlatformArn.contains(@,'Node.js 14 running on 64bit Amazon Linux 2/')]" --output text

For more information see the AWS CLI Command Reference for Elastic Beanstalk [3].

  • Where can I find more information about Elastic Beanstalk platform support?

Retiring platform branch versions are listed in the Retiring platform versions [4] page of the AWS Elastic Beanstalk Platforms Guide (They are no longer listed on the Supported platforms [5] page). For more information, see Elastic Beanstalk platform support policy [2] in the AWS Elastic Beanstalk Developer Guide.

If you have any questions or concerns, please contact AWS Support [6].

[1] https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-glossary.html
[2] https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-support-policy.html
[3] https://awscli.amazonaws.com/v2/documentation/api/latest/reference/elasticbeanstalk/describe-environments.html
[4] https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-retiring.html
[5] https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html
[6] https://aws.amazon.com/support

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210


Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/ELASTICBEANSTALK/AWS_ELASTICBEANSTALK_PLANNED_LIFECYCLE_EVENT/AWS_ELASTICBEANSTALK_PLANNED_LIFECYCLE_EVENT_8f4c05ef48f41409f9bd32d93907dae6add5ed6c959c8ff7639b393e20f0cf38&eventTab=details

Pin Drift

At different map zoom levels pins appear in different locations- some pins appear to be in the middle of the river at high zoom.
Screenshot 2023-11-14 at 14 26 21
Screenshot 2023-11-14 at 14 25 56

Zoom to view minimum 5 locations of selected category on mobile

Particularly relevant for mobile. If users have their location on, or if they're using the default central park location, when they select a category the map should zoom to return at least 5 visible results (or, all results if there less than 5) close to their location

[Action Required] AWS Lambda end of support for Node.js 16

Hello,

We are contacting you as we have identified that your AWS Account currently has one or more AWS Lambda functions using the Node.js 16 runtime.

We are ending support for Node.js 16 in Lambda on June 12, 2024. This follows Node.js 16 End-Of-Life (EOL) reached on September 11, 2023 [1].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in several stages. Starting on June 12, 2024, Lambda will no longer apply security patches and other updates to the Node.js 16 runtime used by Lambda functions, and functions using Node.js 16 will no longer be eligible for technical support. Also, Node.js 16 will no longer be available in the Console, although you can still create and update functions using Node.js 16 via AWS CloudFormation, the AWS CLI, AWS SAM, or other tools. Starting July 15, 2024, you will no longer be able to create new Lambda functions using the Node.js 16 runtime. Starting August 15, 2024, you will no longer be able to update existing functions using the Node.js 16 runtime.

We recommend that you upgrade your existing Node.js 16 functions to Node.js 20 before June 12, 2024. A list of your Node.js 16 functions can be found in the 'Affected resources' tab of the AWS Health Dashboard.

End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.

This notification is generated for functions using the Node.js 16 runtime for the $LATEST function version. The following command shows how to use the AWS CLI [3] to list all functions in a specific region using Node.js 16, including published function versions. To find all such functions in your account, repeat this command for each Region:

aws lambda list-functions --region us-west-2 --output text --query "Functions[?Runtime=='nodejs16.x'].FunctionArn"

From 180 days before deprecation, you can also use Trusted Advisor to identify all functions using the Node.js 16 runtime, including published function versions [4].

If you have any concerns or require further assistance, please contact AWS Support [5].

[1] https://github.com/nodejs/Release
[2] https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html
[3] https://aws.amazon.com/cli/
[4] https://docs.aws.amazon.com/awssupport/latest/user/security-checks.html#aws-lambda-functions-deprecated-runtimes
[5] https://aws.amazon.com/support

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210


Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/LAMBDA/AWS_LAMBDA_PLANNED_LIFECYCLE_EVENT/AWS_LAMBDA_PLANNED_LIFECYCLE_EVENT_f722a90cfdb3f849e1613318c96ce5b6dd6c1d5fab231850f990ec2642e2ced0&eventTab=details

Text formatting for Service descriptions

In GoGetta, we have been creating lists by using the bullet symbol and a line return in anticipation of YourPeer enabling basic WYSIWYG formatting in service description and other text entry fields.
Could you enable line return formatting in the service description filed to let us show the bullet lists we have been creating.

An example of a location where services are formatted this way (though they aren't shown formatted on the FE of GoGetta or YourPeer) is Acacia Network La Casa de Salud. (GoGetta) (YourPeer)

Although it has not yet been shown formatted, the FE should show the service information like this (wrapped to whatever width the column is):
Screenshot 2023-08-30 at 09 18 42

Reinstate clear X icon in search

When deleting a search the previous search results remain. It's unclear how to clear a search apart from going to the homepage or hitting clear all on the filter page.

Auto update of FE services number in the homepage subtitle

The FE has the number of peer-validated services on it in the subtitle on the homepage.
"Search through [number] free support services across NYC"
In reality it is constantly changing. To save me lifting this up and getting a change pushed, can we link that service to a query of services visible on the front end? If s, then let's round it to the nearest 10.

Haircut filter checkbox not returning correct results

Also asked by Lindsay via email: "haircut selection box does not impact the URL (or the page). Please double-check the functionality."

I (adam) checked it too. fyi if I enter https://test.yourpeer.nyc/personal-care?advanced=yes&personal-care=haircut this doesn't return correct results either.

According to GoGetta, haircuts are at
https://gogetta.nyc/find/location/688c0cbf-b8fa-4fb0-9138-9a9bfc00039a
https://gogetta.nyc/find/location/4dcd483d-eef8-4427-adb4-d6376f2ff1d8
https://gogetta.nyc/find/location/1ebd1a5d-c3a1-404d-aaf2-830552e4deea
https://gogetta.nyc/find/location/7ad659a1-e58f-4a5c-a052-6de931d0fed0

Add Bengali and see additional requested languages/dialects

A provider representative is requesting these most commonly used languages at provider locations other than Spanish and some french dialects

  1. Pulaar (Guinea)
  2. Pulaar (Mauritania)
  3. Hassānīya (Mauritania)
  4. Pulaar (Mali)
  5. Wolof
  6. Arabic (Mauritania)
  7. Arabic (Sudan)
  8. Arabic
    @shakilhossain1 could you check and see if Google Translate has these dialects?
    We can make a decision as to whether to implement some of these based on our ability to copyedit them.

Maintain pin selection when refreshing

Steps to recreate:
Homepage
1. Explore services
2. Click a pin, pin UI changes to selected, location details page shown (URL should change but doesn't)

Screenshot 2024-02-22 at 10 23 20

3. Refresh
4. Selection is lost

Screenshot 2024-02-22 at 10 27 28

Shelter filters: Incorrect locations identified. Fix location information to enable functioning filters

Family must identify:
Department of Homeless Services (DHS) (Prevention Assistance and Temporary Housing (PATH))
Department of Homeless Services (DHS) (Adult Family Intake Center (AFIC))
FYI, AFIC is missing form the map as per issue streetlives/streetlives_v2#409

Family should probably not identify
SCO Family of Services (Brooklyn DYCD Youth Drop-in Center)
United Bronx Parents, Inc. (Acacia Network)

Single Adult maybe shouldn't identify:
Covenant House (Northern New Jersey)
Violence Intervention Program (VIP) Community Services
Or, if it should, then we should create all the Youth Shelter locations as Adult locations. Obv it's annoying that there is an overlap for ages 18-25

"Any" should probably not identify... (tbd- AB to confirm with Specialists)

Add permanently visible organization names to map pins

Currently, map pins show organization names, which are visible by hovering, producing a small field containing the name, or by clicking the pin, which produces an information balloon, as well as opening the location name in the tray on mobile or the details page on desktop. Other map icons, like MTA and Train lines, also show details by clicking their pins.

We should provide permanently visible org names for pins, as Google pins do, for all shown locations. Ideally, we should show both the org and location name.

It's not clear if the information needs to be visible on click, as the associated summary details or full details appear anyhow.

Improve Search

By the way, the way the search is implemented is currently extremely naive. It uses SQL "like" query on the JSON data. This approach has a number of issues:

  • it's currently case-sensitive
  • its sensitive to whitespace (e.g. if you have two spaces between words, rather than one, it will fail to yield results with only one space)
  • search terms collide with fields on the JSON object. e.g. if you search for "accommodation", it will return all locations, because all locations contain the field "accommodation_services".

So there is tremendous room for improvement. @adambard1 Can you please create a ticket to improve the search?

Originally posted by @jbeard4 in https://github.com/streetlives/streetlives_v2/issues/409#issuecomment-1990536418

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.