Food Hacking Base:Administration: Difference between revisions
Jump to navigation
Jump to search
(registrar) |
(add admin@ email) |
||
| Line 10: | Line 10: | ||
* [mailto:webmind@puscii.nl webmind] | * [mailto:webmind@puscii.nl webmind] | ||
* [mailto:i.weidauer@gmx.net Ingo Weidauer] | * [mailto:i.weidauer@gmx.net Ingo Weidauer] | ||
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. | ||
Revision as of 12:18, 3 December 2014
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