Krautspace/Unkraut
10
2
Issues 32 Projects 6 Activity

etckeeper installieren und einrichten #40

New issue
Closed
opened 2024-02-17 17:12:29 +01:00 by qbi · 1 comment
qbi commented 2024-02-17 17:12:29 +01:00
Owner
Copy link

Beim KAST2024 stellten wir fest, dass es doch sinnvoll sein kann, etckeeper auf den Maschinen laufen zu haben. Daher sollte das auf

  • blaukraut
  • sauerkraut
  • lagerkraut

installiert und eingerichtet werden.

Beim KAST2024 stellten wir fest, dass es doch sinnvoll sein kann, `etckeeper` auf den Maschinen laufen zu haben. Daher sollte das auf - `blaukraut` - `sauerkraut` - `lagerkraut` installiert und eingerichtet werden.
qbi added this to the KAST 2024 milestone 2024-02-17 17:12:29 +01:00
qbi added the
Kind/Feature
Priority
High
Kind/Enhancement
 labels 2024-02-17 17:12:29 +01:00
qbi added this to the IT-Infrastruktur project 2024-02-17 17:12:29 +01:00
qbi commented 2024-02-17 20:13:04 +01:00
Author
Owner
Copy link
  • etckeeper wurde auf allen drei Maschinen installiert
  • In /etc/etckeeper/etckeeper.conf habe ich jeweils AVOID_DAILY_AUTOCOMMITS=1 gesetzt. Das deaktiviert den täglichen Cornjob.
  • Weiterhin habe ich mit systemctl enable etckeeper.timer den Systemd-Timer aktiviert.
- `etckeeper` wurde auf allen drei Maschinen installiert - In `/etc/etckeeper/etckeeper.conf` habe ich jeweils `AVOID_DAILY_AUTOCOMMITS=1` gesetzt. Das deaktiviert den täglichen Cornjob. - Weiterhin habe ich mit `systemctl enable etckeeper.timer` den Systemd-Timer aktiviert.
qbi closed this issue 2024-02-17 20:13:04 +01:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
KAST 2024
Projects
Clear projects
No items
No project
IT-Infrastruktur
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Krautspace/Unkraut#40
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?