Giter Club home page Giter Club logo

firebaseopensource.com's Introduction

firebaseopensource.com's People

Contributors

1amageek avatar abeisgoat avatar alihusnainarshad avatar anishkny avatar davideast avatar dependabot[bot] avatar dlackty avatar jsayol avatar kroikie avatar lupas avatar merlinnot avatar morganchen12 avatar patilshreyas avatar salakar avatar samtstern avatar thatfiredev avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

firebaseopensource.com's Issues

Add @react-firebase ?

Hey !

Thanks for building and maintaining this repo ๐Ÿ˜„

I built @react-firebase to make it easier to integrate Firebase in any React app.

It works and was designed to work with firebase web, react-native-firebase and firebase-admin !

The supported firebase services are :

I use it regularly and am committed to keeping it highly-tested and bug-free.

Repo : https://github.com/rakannimer/react-firebase

Docs : https://react-firebase-js.com/

Cheers !

DOC: No step-by-step instructions to 'Add Gradle Build Steps to rebuild APK packages' section

In the documentation, the section that describes how to add Gradle build steps to Jenkins in order to integrate it with revision control systems is not a list of steps that the reader can follow. E.g.

  1. From the main page for your project, click Configure.

  2. On the project configuration page, scroll down to the Build section, and then choose {insert appropriate build step} from the Add build step menu.

  3. and so on

If there are too many steps to list, would it be possible to have links to documentation/examples of how to implement those two items? Thanks!

Contents dropdown is misplaced in some projects

What Happened?
The "contents dropdown" is displayed in different positions depending on the structure of each project's content file. Apparently, it places itself before the first h2 from the content file, but some projects have their first h2 way bellow while others have it right on top.

What Did You Expect to Happen
I expected the contents dropdown to be shown on top of the page for every project. I believe this would make it easier to find.

Screenshot (If Applicable)
The Firebase Android SDK is an example of a project that has the content dropdown misplaced:
fosdc_android_sdk

Here's how I expected it to look:
fosdc_firextensions

Fix <title> tags

In the latest migration, only the homepage has a proper <title>.

Add page title to JSON config spec

What Happened?
Sidebar added in #64 uses page path as title

What Did You Expect to Happen
Should be able to do something like this:

// Before
pages: ["foo.md", "bar.md"]

// After
pages: [ { title: "Foo", path: "foo.md" }, { title: "Bar", path: "bar.md" } ]

Screenshot (If Applicable)
N/A

Add more analytics events

Ideas:

  • Clicking on a "related" project
  • Clicking on any of the big links (buttons)
  • Clicking on a subheader link
  • Clicking on a page in the sidebar

Make github actions clearer

A few improvements:

  • Currently the "Github" link in the top bar and the "Clone Repo" link do the same thing
    • Neither makes it obvious you are about to leave the page.
  • The "Download ZIP" button is generally a bad idea and may be something we have pages
    opt-in for.

Nicer code highlighting

What Happened?
Our syntax highlight is kind of drab and boring:
screen shot 2018-11-20 at 12 25 44 pm

What Did You Expect to Happen
The code actually looks much better when rendered on GitHub:
screen shot 2018-11-20 at 12 25 53 pm

Screenshot (If Applicable)
See above.

Move to Cloud Build and Cloud Scheduler

Currently we're using GKE Cronjobs for everything. That's an overly complex tool and just not built for this job.

Move cronjobs to scheduler and building responsibility to Cloud Build.

Make build fail if Firestore fails

See attached logs. If Firestore doesn't respond we can end up deploying a pretty much empty site.
log-9a6939ef-6a83-43fd-a563-d4cf0c05b526.txt

Step #1: > [email protected] get-routes /firebaseopensource.com/frontend
Step #1: > ts-node -O '{"module": "commonjs"}' src/scripts/routesList.ts
Step #1: 
Step #1: (node:113) DeprecationWarning: grpc.load: Use the @grpc/proto-loader module with grpc.loadPackageDefinition instead
Step #1: [2018-11-16T01:09:37.877Z] @firebase/firestore: Firestore (5.0.4): Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds.
Step #1: This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
Step #1: Found 7 routes
Step #1: Done.
Step #1: 
Step #1: > [email protected] gen /firebaseopensource.com/frontend
Step #1: > nuxt generate
Step #1: 
Step #1: 2018-11-16T01:09:39.548Z nuxt:generate Generating...
Step #1: 2018-11-16T01:09:39.641Z nuxt:build App root: /firebaseopensource.com/frontend
Step #1: 2018-11-16T01:09:39.642Z nuxt:build Generating /firebaseopensource.com/frontend/.nuxt files...
Step #1: 2018-11-16T01:09:39.645Z nuxt:build Generating files...
Step #1: 2018-11-16T01:09:39.646Z nuxt:build Generating routes...
Step #1: 2018-11-16T01:09:39.687Z nuxt:build Building files...
Step #1: ts-loader: Using [email protected] and /firebaseopensource.com/frontend/tsconfig.json
Step #1: WARNING Compiled with 1 warnings01:10:24
Step #1: 
Step #1: warning 
Step #1: 
Step #1: asset size limit: The following asset(s) exceed the recommended size limit (300 kB).
Step #1: This can impact web performance.
Step #1: Assets: 
Step #1: pages/projects/_org/_repo/index.6e896a0c0fb4d8fb9b0f.js (431 kB)
Step #1: pages/platform/_platform/index.cff62769ba4c5316ae45.js (382 kB)
Step #1: pages/index.8d947a4d7f450037e236.js (382 kB)
Step #1: 
Step #1: Hash: f8bca12b158d16429f51
Step #1: Version: webpack 3.12.0
Step #1: Time: 43590ms
Step #1: Asset Size Chunks Chunk Names
Step #1: pages/projects/_org/_repo/index.6e896a0c0fb4d8fb9b0f.js 431 kB 0 [emitted] [big] pages/projects/_org/_repo/index
Step #1: pages/platform/_platform/index.cff62769ba4c5316ae45.js 382 kB 1 [emitted] [big] pages/platform/_platform/index
Step #1: pages/index.8d947a4d7f450037e236.js 382 kB 2 [emitted] [big] pages/index
Step #1: layouts/default.0a9ea840477ea6c560c6.js 400 bytes 3 [emitted] layouts/default
Step #1: vendor.f9914d07c40f138de8ae.js 144 kB 4 [emitted] vendor
Step #1: app.85e566f9c630006ee470.js 27.5 kB 5 [emitted] app
Step #1: manifest.f8bca12b158d16429f51.js 1.59 kB 6 [emitted] manifest
Step #1: LICENSES 5.68 kB [emitted] 
Step #1: + 3 hidden assets
Step #1: 
Step #1: WARNING in asset size limit: The following asset(s) exceed the recommended size limit (300 kB).
Step #1: This can impact web performance.
Step #1: Assets: 
Step #1: pages/projects/_org/_repo/index.6e896a0c0fb4d8fb9b0f.js (431 kB)
Step #1: pages/platform/_platform/index.cff62769ba4c5316ae45.js (382 kB)
Step #1: pages/index.8d947a4d7f450037e236.js (382 kB)
Step #1: ts-loader: Using [email protected] and /firebaseopensource.com/frontend/tsconfig.json
Step #1: Hash: aed0a0b54593fc64d618
Step #1: Version: webpack 3.12.0
Step #1: Time: 3995ms
Step #1: Asset Size Chunks Chunk Names
Step #1: server-bundle.json 251 kB [emitted] 
Step #1: 2018-11-16T01:10:28.330Z nuxt: Call generate:distRemoved hooks (1)
Step #1: 2018-11-16T01:10:28.331Z nuxt:generate Destination folder cleaned
Step #1: 2018-11-16T01:10:28.341Z nuxt: Call generate:distCopied hooks (1)
Step #1: 2018-11-16T01:10:28.341Z nuxt:generate Static & build files copied
Step #1: 2018-11-16T01:10:28.345Z nuxt:render Rendering url /
Step #1: 2018-11-16T01:10:28.377Z nuxt:render Rendering url platform/all
Step #1: 2018-11-16T01:10:28.380Z nuxt:render Rendering url platform/ios
Step #1: 2018-11-16T01:10:28.381Z nuxt:render Rendering url platform/android
Step #1: 2018-11-16T01:10:28.382Z nuxt:render Rendering url platform/web
Step #1: 2018-11-16T01:10:28.382Z nuxt:render Rendering url platform/games
Step #1: 2018-11-16T01:10:28.383Z nuxt:render Rendering url platform/admin
Step #1: index:asyncData(/)
Step #1: platform:asyncData(/platform/all)
Step #1: platform:asyncData(/platform/ios)
Step #1: platform:asyncData(/platform/android)
Step #1: platform:asyncData(/platform/web)
Step #1: platform:asyncData(/platform/games)
Step #1: platform:asyncData(/platform/admin)
Step #1: (node:137) DeprecationWarning: grpc.load: Use the @grpc/proto-loader module with grpc.loadPackageDefinition instead
Step #1: [2018-11-16T01:10:38.672Z] @firebase/firestore: Firestore (5.0.4): Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds.
Step #1: This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
Step #1: 2018-11-16T01:10:39.051Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.188Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.267Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.336Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.381Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.451Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.521Z nuxt: Call generate:page hooks (1)
Step #1: 2018-11-16T01:10:39.521Z nuxt:generate Generate file: /index.html
Step #1: 2018-11-16T01:10:39.522Z nuxt:generate Generate file: platform/all/index.html
Step #1: 2018-11-16T01:10:39.522Z nuxt:generate Generate file: platform/ios/index.html
Step #1: 2018-11-16T01:10:39.523Z nuxt:generate Generate file: platform/android/index.html
Step #1: 2018-11-16T01:10:39.523Z nuxt:generate Generate file: platform/web/index.html
Step #1: 2018-11-16T01:10:39.523Z nuxt:generate Generate file: platform/games/index.html
Step #1: 2018-11-16T01:10:39.524Z nuxt:generate Generate file: platform/admin/index.html
Step #1: 2018-11-16T01:10:39.833Z nuxt:render Rendering url /
Step #1: 2018-11-16T01:10:39.835Z nuxt: Call generate:done hooks (1)
Step #1: 2018-11-16T01:10:39.836Z nuxt:generate HTML Files generated in 60.3s
Step #1: 2018-11-16T01:10:39.837Z nuxt:generate Generate done
Step #1: /firebaseopensource.com
Step #1: 
Step #1: === Deploying to 'fir-oss'...
Step #1: 
Step #1: i deploying hosting
Step #1: i hosting[fir-oss]: beginning deploy...
Step #1: i hosting[fir-oss]: found 24 files in frontend/dist
Step #1: โœ” hosting[fir-oss]: file upload complete
Step #1: i hosting[fir-oss]: finalizing version...
Step #1: โœ” hosting[fir-oss]: version finalized
Step #1: i hosting[fir-oss]: releasing new version...
Step #1: โœ” hosting[fir-oss]: release complete
Step #1: 
Step #1: โœ” Deploy complete!

Consider removing subprojects handling

With the addition of pages support there is basically no use for subprojects. They are also confusing since they don't have stars or other useful metrics.

Use "fan out" for getAllProjects function

The getAllProjects function should:

  • Get a list of all projects we want to update.
  • Send a pub sub event for each one

The getProject function should respond to the pub sub event. This will allow us to scale farther than we do now: we don't have to worry about getting all projects in one function before the 540s timeout.

Add a "staging" capability

Add a page like /staging?project="foo::bar" that would allow people to quickly see how their page will be displayed without running into any caching (so it should call getProject() and then dynamically render).

We may want to allow it to take a direct link to a json file in GitHub to allow for staging from a non-master branch.

Merge firebase configs

We have two firebase.json files now. I think we can merge them all into the root one if we do some path prefixing. The one in frontend is copied from the Nuxt site but the one in the root has information on functions and Firestore.

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.