View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008634 | Taler | deployment and operations | public | 2024-03-13 09:45 | 2024-04-15 19:32 |
| Reporter | javier.sepulveda | Assigned To | javier.sepulveda | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.10 | Fixed in Version | 0.10 | ||
| Summary | 0008634: Apply version control to /etc folder - anastasis.lu | ||||
| Description | Either with directory binding and git, or with the configuring properly the etckeeper program. | ||||
| Tags | No tags attached. | ||||
| After doing some tests on this. I don't like bind-mount. As we are using a VPS and not physical server, so dealing with partitions (lsblk), and editing the /etc/fstab complicates too much things. I even lost the ssh access with the test server when doing the mount --bind. Using etckeeper is simple, but I don't like it neither: 1) Touches the original /etc, creating a .git folder inside 2) Even though you can enable a systemd timer for this program to work (which is nice), and avoid to use cronjobs, in the end, after each edition of the /etc, you will have automatic daily commits, with random names, which eventually won't be helpful for recovery. 3) You can't use GIT as usual, but have to use specific etckeeper command syntax every time. I am thinking on using hard symlinks from an external /root/etc-maintenance folder to the real /etc, but as far as I have tried GIT doesn't track symlinks even if they are hard ones. So I will keep going to think a better solution. For the moment no danger at all with the server, as I have created a snapshot from the provider control panel,so we can rollback that at any time. I have learnt in this process, that rush is not good, and I am very happy to see that even though I have been requested to do this in a way, I have decided to wait and further investigate. Thus I will keep doing some research to see if I can find a nice solution for this in combination with GIT, as to end up using etckeeper, there is always time. | |
| Please only assign as 'feedback' if there is any open issue/question to be addressed. Otherwise, you should probably just resolve! | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-13 09:45 | javier.sepulveda | New Issue | |
| 2024-03-13 09:45 | javier.sepulveda | Status | new => assigned |
| 2024-03-13 09:45 | javier.sepulveda | Assigned To | => javier.sepulveda |
| 2024-03-13 12:39 | javier.sepulveda | Note Added: 0021885 | |
| 2024-03-14 12:48 | javier.sepulveda | Assigned To | javier.sepulveda => Christian Grothoff |
| 2024-03-14 12:48 | javier.sepulveda | Status | assigned => feedback |
| 2024-03-18 11:19 | Christian Grothoff | Assigned To | Christian Grothoff => javier.sepulveda |
| 2024-03-18 11:19 | Christian Grothoff | Status | feedback => informing |
| 2024-03-18 11:19 | Christian Grothoff | Resolution | open => fixed |
| 2024-03-18 11:19 | Christian Grothoff | Fixed in Version | => 0.10 |
| 2024-03-18 11:19 | Christian Grothoff | Note Added: 0021942 | |
| 2024-04-11 23:50 | Christian Grothoff | Target Version | => 0.10 |
| 2024-04-15 19:32 | Christian Grothoff | Status | informing => closed |