brigadehub
Advanced tools
BrigadeHub is an beta stage data portal for volunteer coding organizations. While being built for Code for America Brigades, it can be be used for any project-based coding organization. It's being built to consolidate the efforts of maintaining a brigade's information into a single location, to distribute the task of content creation across the various non-technical brigade roles, and to enhance the experience of both members and admins of these unique organizations.
For a complete top-down view of the roadmap, take a look at our active Roadmap Wiki (currently being worked on).
In short, BrigadeHub is designed to meet some very specific goals:
There are three different ways of interacting with/using Brigadehub:
Depending on the needs of your organization, you'll want to decide which will work best for you.
Note: Unless otherwise specified, links like location.of.mongo and path/to/file do not represent the actual link you need to use in your enviroment, and should be replaced with the appropriate locations.
Brigadehub Suite is the flagship install of Brigadehub, and is more or less a brigade-in-a-box. It installs three components: Core, Admin Theme, and Public Theme. It's deployed in such a way that you should never need to touch the code, but if you want to, it's a simple matter. It provides Admin tools to manage your brigade information, and a slick frontend to display the info you're managing. Your frontend developers can dynamically pull the data about your brigade via the Core API if they have external tools that need the same data. And you can rest assured that we'll be working on patches and updates over time to make this the most secure and stable platform ever.
Heroku (click to open)Heroku sports this handy one-click-install feature, which will handle most of the configuration for you. Base the install off [brigadehub/brigadehub](https://github.com/brigadehub/brigadehub), and you're good to go (the button below does that ⬇)
Docker (click to open)***Pre-requisites***
Installation and Running
docker pull brigadehub/suite
docker run -d --expose=8080:desiredport -e MONGODB='mongodb://location.of.mongo:27017/brigadehub-suite' -e PORT=desiredport brigadehub/suite
NPM CLI (click to open)***Pre-requisites***
Installation and Running
yarn global add brigadehub
PORT=desiredport MONGODB_URI=mongodb://location.of.mongo:27017/brigadehub-suite brigadehub-suite
Source (click to open)***Pre-requisites***
Installation and Running
git clone https://github.com/brigadehub/brigadehub
cd brigadehub
make install
make start
To work on Brigadehub Suite as a developer, you need to clone and link internally all four portions of the suite. Fork all 4 repos into your desired organization or account, and work from those, making sure to update from upstream periodically.
Pre-requisites
Installation and Running
First, clone the following repositories into your own account, either your organization's org or your personal account:
Once you've forked all four, clone the repos locally (replacing your-account with the appropriate org/account name):
git clone https://github.com/your-account/brigadehub
git clone https://github.com/your-account/core
git clone https://github.com/your-account/theme-public-c4sf
git clone https://github.com/your-account/theme-admin-c4sf
In separate terminals, run the following:
cd theme-public-c4sf
make upstream/set
make install
make link
cd theme-admin-c4sf
make upstream/set
make install
make link
cd core
make upstream/set
make install
make link
cd brigadehub
make upstream/set
make install
make link
make start/develop
Any changes made in core, theme-public-c4sf, and theme-admin-c4sf will restart the server in brigadehub, and allow you to preview the changes. When you're done with your changes, make sure the tests pass via make test, and create a pull request from the appropriate repo.
Sync Changes with Upstream
To pull the most recent changes from upstream/master, run the following command:
make upstream/sync
This will fetch the upstream master branch and merge those changes into your local master branch.
Push Changes Upstream
To push your development changes back to the main brigadehub repo, push your changes up to your branch, and make a Pull Request into the upstream repository's master branch. Please include the following information in your pull request:
Please keep in mind that application changes are subject to review and revision, and may be rejected at the project maintainers discretion.
Brigadehub Admin Gateway installs two components: Core and Admin Theme. Your frontend developers can dynamically pull the data about your brigade via the Core API, but you as an administrator should never need to touch the code. This is a good option if you already have a site and want to augment it with brigadehub data.
Heroku (click to open)Heroku sports this handy one-click-install feature, which will handle most of the configuration for you. Base the install off [brigadehub/admin-gateway](https://github.com/brigadehub/admin-gateway), and you're good to go (the button below does that ⬇)
Docker (click to open)***Pre-requisites***
Installation and Running
docker pull brigadehub/admin-gateway
docker run -d --expose=8080:desiredport -e MONGODB='mongodb://location.of.mongo:27017/brigadehub-admin-gateway' -e PORT=desiredport brigadehub/admin-gateway
***Pre-requisites***
Installation and Running
yarn global add brigadehub-admin-gateway
brigadehub-admin-gateway --port desiredport --mongodb mongodb://location.of.mongo:27017/brigadehub-admin-gateway
***Pre-requisites***
Installation and Running
git clone https://github.com/brigadehub/admin-gateway
cd admin-gateway
make install
make start
To work on Brigadehub Admin Gateway as a developer, you need to clone and link internally all three portions of the install. Fork all 3 repos into your desired organization or account, and work from those, making sure to update from upstream periodically.
Pre-requisites
Installation and Running
First, clone the following repositories into your own account, either your organization's org or your personal account:
Once you've forked all three, clone the repos locally (replacing your-account with the appropriate org/account name):
git clone https://github.com/your-account/admin-gateway
git clone https://github.com/your-account/core
git clone https://github.com/your-account/theme-admin-c4sf
In separate terminals, run the following:
cd theme-admin-c4sf
make upstream/set
make install
make link
cd core
make upstream/set
make install
make link
cd admin-gateway
make upstream/set
make install
make link
make start/develop
Any changes made in core and theme-admin-c4sf will restart the server in admin-gateway, and allow you to preview the changes. When you're done with your changes, make sure the tests pass via make test, and create a pull request from the appropriate repo.
Sync Changes with Upstream
To pull the most recent changes from upstream/master, run the following command:
make upstream/sync
This will fetch the upstream master branch and merge those changes into your local master branch.
Push Changes Upstream
To push your development changes back to the main brigadehub repo, push your changes up to your branch, and make a Pull Request into the upstream repository's master branch. Please include the following information in your pull request:
Please keep in mind that application changes are subject to review and revision, and may be rejected at the project maintainers discretion.
Brigadehub Mini installs only one component: Core. No Frontends will be deployed with this install, exposing only the authentication routes and REST APIs. This is an advanced setting, and should be only done if you already have a site and admin portal to manage on your own. All features are accessible via REST API (GraphQL to come soon)
Heroku (click to open)Heroku sports this handy one-click-install feature, which will handle most of the configuration for you. Base the install off [brigadehub/mini](https://github.com/brigadehub/mini), and you're good to go (the button below does that ⬇)
Docker (click to open)***Pre-requisites***
Installation and Running
docker pull brigadehub/mini
docker run -d --expose=8080:desiredport -e MONGODB='mongodb://location.of.mongo:27017/brigadehub-mini' -e PORT=desiredport brigadehub/mini
***Pre-requisites***
Installation and Running
yarn global add brigadehub-mini
brigadehub-mini --port desiredport --mongodb mongodb://location.of.mongo:27017/brigadehub-mini
***Pre-requisites***
Installation and Running
git clone https://github.com/brigadehub/mini
cd mini
make install
make start
To work on Brigadehub Mini as a developer, you need to clone and link internally both portions of the install. Fork both repos into your desired organization or account, and work from those, making sure to update from upstream periodically.
Pre-requisites
Installation and Running
First, clone the following repositories into your own account, either your organization's org or your personal account:
Once you've forked both repos, clone the repos locally (replacing your-account with the appropriate org/account name):
git clone https://github.com/your-account/mini
git clone https://github.com/your-account/theme-admin-c4sf
In separate terminals, run the following:
cd core
make upstream/set
make install
make link
cd mini
make upstream/set
make install
make link
make start/develop
Any changes made in core and theme-admin-c4sf will restart the server in mini, and allow you to preview the changes. When you're done with your changes, make sure the tests pass via make test, and create a pull request from the appropriate repo.
Sync Changes with Upstream
To pull the most recent changes from upstream/master, run the following command:
make upstream/sync
This will fetch the upstream master branch and merge those changes into your local master branch.
Push Changes Upstream
To push your development changes back to the main brigadehub repo, push your changes up to your branch, and make a Pull Request into the upstream repository's master branch. Please include the following information in your pull request:
Please keep in mind that application changes are subject to review and revision, and may be rejected at the project maintainers discretion.
*Core API Documentation can be found on gitbook
Admin Theme Documentation is being worked on
Public Theme Documentation is being worked on
If you come upon issues while installing or using Brigadehub (any install), open an issue here in Github. If it occurs enough times, it'll make it here into Troubleshooting
Brigadehub works from a fork/PR methodology. If you would like to contribute, check the github issues and see if someone is working on the issue already. If not, comment in the issue that you are working on it (or create a new issue if it's not already there), then fork the repo and submit a PR when your work is complete. Claimed issues without update on the issue itself or via linked PR after 30 days will be unassigned and reopened for others to work on.
The changelog for Brigadehub (and each of its components) resides in the appropriate repos Releases tab.
Brigadehub is a Code for San Francisco Infrastructure project, and has been brought about by the generous work of the following individuals. If you make a contribution to Brigadehub (e.g. when opening a PR), feel free to add yourself to this list in addition to your changes. If you are contributing in a non-code fashion, open an issue to have your name added.
github``@``therebelrobot.com>Similar projects have been conceived and implemented previously (Laddr, Connector, Chime, etc.), but for one reason or another didn't meet the needs of Code for San Francisco and many other brigades. Brigadehub hopes to bridge those infrastructure gaps.
Have additional resources that could benefit those using Brigadehub? Open a Github Issue and let us know!
The MIT License (MIT)
Copyright (c) 2016-2017 Code for San Francisco
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Unknown package
We found that brigadehub demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
/Research
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.
Security News
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.
Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.