Food Hacking Base:Administration: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
BaltimoreJoe (talk | contribs) No edit summary |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
The Internet infrastructure of the FHB consists of the following parts: | The Internet infrastructure of the FHB consists of the following parts: | ||
* .org domain registered via [https://www. | * .org domain registered via [https://www.gandi.net Gandi] | ||
* Webspace at [https://uberspace.de Uberspace] | * Webspace at [https://uberspace.de Uberspace] | ||
| Line 8: | Line 8: | ||
* [mailto:algoldor@yahoo.com Frantisek Algoldor Apfelbeck] | * [mailto:algoldor@yahoo.com Frantisek Algoldor Apfelbeck] | ||
* [mailto:steffen@beyer.io Steffen Beyer] | * [mailto:steffen@beyer.io Steffen Beyer] | ||
* [mailto:bigmac@xs4all.nl Marcel van der Peijl] | |||
* [mailto:webmind@puscii.nl webmind] | * [mailto:webmind@puscii.nl webmind] | ||
* [mailto:i.weidauer@gmx.net Ingo Weidauer] | * [mailto:i.weidauer@gmx.net Ingo Weidauer] | ||
* [mailto:joe.awni@gmail.com Joe Awni] | |||
Contact [mailto:admin@foodhackingbase.org admin@foodhackingbase.org] for general inquiries. | |||
The webspace (<tt>cd html/mediawiki</tt>) is managed as a Git repository for version control. I.e. after making a change, you should check it into the repository and write a comment, explaining what you did. That way, the other team members can see who did what, and why. | The webspace (<tt>cd html/mediawiki</tt>) is managed as a Git repository for version control. I.e. after making a change, you should check it into the repository and write a comment, explaining what you did. That way, the other team members can see who did what, and why. | ||
Latest revision as of 20:51, 24 July 2015
The Internet infrastructure of the FHB consists of the following parts:
The Admin Team™:
Contact admin@foodhackingbase.org for general inquiries.
The webspace (cd html/mediawiki) is managed as a Git repository for version control. I.e. after making a change, you should check it into the repository and write a comment, explaining what you did. That way, the other team members can see who did what, and why.
Just a few Git commands will suffice:
- git status – show changed files; should show no results when beginning and ending an admin session
- git add <filename> [filename...] – mark changed file for next commit
- git commit -m 'fired up the foo bar' – commit marked changes with a certain comment
- git log -3 – show last three changes