How is it not a security issue to serve the API key in `public/auth.html`?
It's a public key, if I'm not mistaken.
Show HN: A minimal setup for React/ES6 sites with a Firebase back end
21–30 of 40 posts
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#22https://github.com/Jon-Biz/simple-static-react-firebase/blob... Sorry, but with those many dependencies, I could hardly call that minimal.
The boilerplate you have to write (and handle) is minimal. This is more important to me than the number of packages I have to install for development. And, only React, ReactDom and Firebase (which has to be required in the page html, unfortunately, due to Firebase issues) actually ship down to th client While I can appreciate the benefit of keeping your entire codebase small (especially the bits that aren't yours), I…
Yeah, how is this a lot of dependencies?
babel-core, babel-loader, babel-polyfill, babel-preset-es2015 and babel-preset-react can be considered one dependency (it's babel...).
react and react-dom are another.
webpack, the dev server, and 3 webpack plugins can be considered a 3rd.
That's 3 "real" dependencies. If that's a lot, then i'd love to see a "real" minimal setup.
Just because javascript dependencies tend to take the unix philosophy to the extreme doesn't mean that each of those should be treated equally.
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#23/pubic/ output directory. Put your assets in here next to the compiled js and css. Splendid!
:groan:
I have four of these little repos now, all forked from each other, all with that spelling mistake, no doubt.
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#24Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#25Does this come with Server side rendering out of the box?
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#26Demo Pls
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#27Earlier quoted context omitted.
The boilerplate you have to write (and handle) is minimal. This is more important to me than the number of packages I have to install for development. And, only React, ReactDom and Firebase (which has to be required in the page html, unfortunately, due to Firebase issues) actually ship down to th client While I can appreciate the benefit of keeping your entire codebase small (especially the bits that aren't yours), I…
Yeah, how is this a lot of dependencies? babel-core, babel-loader, babel-polyfill, babel-preset-es2015 and babel-preset-react can be considered one dependency (it's babel...). react and react-dom are another. webpack, the dev server, and 3 webpack plugins can be considered a 3rd. That's 3 "real" dependencies. If that's a lot, then i'd love to see a "real" minimal setup. Just because javascript dependencies tend to ta…
JavaScript dependencies are to Unix philosophy as C++ is to object-oriented programming... In name only, and seemingly in complete misunderstanding of the concept.
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#28Has anyone here dealt with Firebase's authentication / authorization model in production?
Yup, it's pretty solid, no issues to report.
Except that the default is read/write for all users[0]. This starter kit doesn't mention security at all, even just to warn the user about full read/write.
[0] - https://www.firebase.com/docs/security/quickstart.html
"By default, your app has rules which grants every request full read and write permissions to your database"
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#29Earlier quoted context omitted.
Yup, it's pretty solid, no issues to report.
Except that the default is read/write for all users[0]. This starter kit doesn't mention security at all, even just to warn the user about full read/write. [0] - https://www.firebase.com/docs/security/quickstart.html "By default, your app has rules which grants every request full read and write permissions to your database"
Which is exactly what new developers (who are attracted to these kinds of services) ignore.
Re: Show HN: A minimal setup for React/ES6 sites with a Firebase back end
#30Earlier quoted context omitted.
Yup, it's pretty solid, no issues to report.
Except that the default is read/write for all users[0]. This starter kit doesn't mention security at all, even just to warn the user about full read/write. [0] - https://www.firebase.com/docs/security/quickstart.html "By default, your app has rules which grants every request full read and write permissions to your database"
Thanks. Let me make an issue to update the docs on that.
I've been using Firebase a while, and so I didn't fully think through the experience for users unfamiliar with firebase.
By necessity, this repo use of firebase is somewhat opinionated. I intend to add comments and docs to explain the architecture and how to set it up to work with different kinds of persistent data (ie - shared and public data as well as user related docs). And, of course, to set up secure separate docs for different users.