Let us discuss what is Firebase admin and how to use it. Firebase Admin is Firebase Management tool. Unlike Google’s default console Firebase Admin enables all the queries to be executed right from the tool.
You can download tested install packages for OS X, Windows and Linux from following links:
- Multiple Platforms: Whatever systems you use. We are here for you. Firebase Admin is available for Windows, Mac and Linux.
- Powerful Query Builder: Testing your firebase query is simple now. Write query & test results directly using the query builder.
- Multiple Connections: Have Multiple Firebase Databases? Add as many connections as you want. Firebase Admin can handle them all.
- Open Source. Forever: Love Open Source? So do we! We will never charge you for the software. Today, Tomorrow and Forever.
- Realtime Update: Update in Firebase Admin will update Firebase. Or update in linked application will update in the Tool too. Realtime.
- Elegant User Interface: Software comes with Minimalistic UI. No redundant elements or styles. Just what you need with simple layout & style.
Firebase Admin is an open source project driven by volunteers. We will try answer every questions. But please be patient. You can create a new issue in the Github issue queue
- In place edit
- Language selection
- File Upload
- User Management
Not seeing what you want? Please create an issue
Wiki coming soon.
Installation Wiki coming soon.
New feature suggestions or UI improvements are always welcome. This project is powered by open source volunteers, so we have a limited amount of development resource to address all requests. We will certainly make best efforts to progress (particularly for those with strong community upvotes).
Code contributions are always welcome! Just try to follow our coding style: Coding Style Wiki coming soon.
If you plan to contribute, please create a Github issue (or comment on the relevant existing issue) so we can help coordinate with upcoming release plans.
For a general workflow, see Github’s guide to Fork a Repo.
Pull requests (PRs) should generally be for discrete issues (i.e. one issue per PR please) and be clean to merge against the current master branch. It would also be helpful if you can confirm what testing has been done (specific O/S targets if applicable).
A usual naming approach for feature branches is
issue-###. Include the issue number in your commit message / pull request description to link the PR to the original issue.