The definition for fedora-hubs has changed over the months !
Hubs has come a long way from when it was initially started. From new milestones, to new goals, new road-maps.
There have been new contributors willing to contribute to hubs, but facing issues while setting it up locally. Thus an initiative to help out new contributors hack their way into the project. Few common terms and words, not so common to the non-hubs world 😛
To begin with: We have taken efforts in keeping the README file updated. You might want to keep looking back to this file while setting it up locally.
Below, I have explained a tiny bit more in detail about a few things that might be confusing or where one can face issues, also how these files happen to be inter-related.
After having installed all the dependencies and cloned the project, you need to configure the project to authenticate against Ipsilon, fedora’s multi-protocol Identity Provider service.
oidc-register --debug https://iddev.fedorainfracloud.org/ http://localhost:5000
If one faces an error regarding verification of certificate, the following command will replace httplib2’s ca cert file, else you’ll be thrown back since you don’t have the http setting.
cp /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ~/.virtualenvs/hubs/lib/python2.7/site-packages/httplib2/cacerts.txt
You also might want to keep clearing/refreshing your cookies. After having created the local configuration file as mentioned in the README, one needs to create the database.
Further which one can finish running the app by starting the devel server with their local config file.
Few not-so-common terminologies:
Hub: A hub can be associated with a page displaying the info that concerns the hub.
Widget: The various sized rectangular cards on a hub-page are termed as widgets.
One can find the various widgets under the widgets/ dir in the source-code.
Every widget has a respective html file under the widgets/templates dir.
User-Hub page: The hub page of a fas (fedora account system) user that lists down the widgets he/she has configured and wishes to display on his/her page.
While hacking on the project, you might want to navigate to localhost:5000/ to view the widget on a user-hub page.
Group-Hub page: The hub page of the various teams such as Infrastructure, Design-team, Commops, Marketing, i18n.
Similarly, while hacking on a widgets relevant to groups, you need to navigate to localhost:5000/ to view the respective widget on the group-hub page.
Again, when hacking on a new widget, according to the hub page you wish to display, one might want to add it either to the hubs/defaults.py file or to the populate.py file. One can look into it under the “Stubbing out a new widget” section of the README file.
You might see something similar to this on your localhost :
So, this is a group-hub page, Group:Infrastructure here, listing down the widgets with respect to the infrastructure group. Widgets are listed in the same order as added with their index values, in the populate.py file under the Infrastructure team.
This is a user-hub page:
fas_username: devyani7, listing down the widgets configured in the hubs/defaults.py file. Here, this user-hub page can be configured as the user wishes his/her page to appear to the visitors.
One channel where you can drop/lurk for further queries: #fedora-hubs on freenode.
We have weekly-meetings every Tuesday at 14:00 UTC 🙂
We also have a mailing-list: https://email@example.com