Changes between Version 1 and Version 2 of WikiStart
- Timestamp:
- 04/29/25 10:41:06 (4 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v1 v2 1 = Welcome to Trac1 = Welcome to Operation Advanced Infrastructure 2 2 3 Trac is a '''minimalistic''' approach to '''web-based''' management of 4 '''software projects'''. Its goal is to simplify effective tracking and 5 handling of software issues, enhancements and overall progress. 3 == Motivation 6 4 7 All aspects of Trac have been designed with the single goal to 8 '''help developers write great software''' while '''staying out of the way''' 9 and imposing as little as possible on a team's established process and 10 culture. 5 This project is an ongoing effort to create a better infrastructure for our preliminary working environment and to document it accordingly. 6 It will help to onboard new team members, e.g. admins or developers in order to remove some load from existing personnel. 11 7 12 As all Wiki pages, this page is editable, this means that you can 13 modify the contents of this page simply by using your 14 web-browser. Simply click on the "Edit this page" link at the bottom 15 of the page. WikiFormatting will give you a detailed description of 16 available Wiki formatting commands. 8 == Goal 17 9 18 "[wiki:TracAdmin trac-admin] ''yourenvdir'' initenv" created 19 a new Trac environment, containing a default set of wiki pages and some sample 20 data. This newly created environment also contains 21 [wiki:TracGuide documentation] to help you get started with your project. 10 This project can be used as a blue print for a real production environment, when permit is given 22 11 23 You can use [wiki:TracAdmin trac-admin] to configure 24 [http://trac.edgewall.org/ Trac] to better fit your project, especially in 25 regard to ''components'', ''versions'' and ''milestones''. 12 == Key points 26 13 14 * Every part of the new infrastructure is reproducible 15 * Everything is under version control 16 * Commits have to be signed 17 * We provide git repositories, wikis and bug trackers to document everything 18 * We automate as many processes as possible 19 * Backups are done regularly 20 * Tested desaster recovery is mandatory - downtimes not longer than 8 hours max 27 21 28 T racGuide is a good place to start.22 These key points are non-negotiable 29 23 30 Enjoy! [[BR]] 31 ''The Trac Team'' 24 == Tools 32 25 33 == Starting Points 26 * '''gitolite''' for access control to our git repos 27 * '''trac''' for wiki and bug tracking 28 * '''guix''' to declare everything reproducible 29 * '''libre''' software whenever possible - exceptions, e.g. firmware must be clearly justified 34 30 35 * TracGuide -- Built-in Documentation 36 * [http://trac.edgewall.org/ The Trac project] -- Trac Open Source Project 37 * [http://trac.edgewall.org/wiki/TracFaq Trac FAQ] -- Frequently Asked Questions 38 * TracSupport -- Trac Support 31 == Recommended hardware 39 32 40 For a complete list of local wiki pages, see TitleIndex. 33 * 1 Server for CI / CD with 10 TB of storage space and at least 12 cores 34 * 1 Substitute server for binaries coming from CI / CD with 20 TB of storage space 35 * 1 Server to host gitolite repositories and trac installation 36 * 1 Computer for air gap data exchange 37 * Multiple developer machines 38 39 == Personnel 40 41 * Two '''hardcore''' admins with high expertise in Guix, Containers and Linux in general 42 * Another two admins with enough knowledge to roll out predeclared systems and to do detailed bug reports 43 44 == Time and money 45 46 * Hardware costs: below 10000 Euro without developer machines 47 * Time to train existing personnel: less than 3 months, if personnel already is motivated and has profound knowledge as admin
