starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add netbox housekeeping systemd units #7358

New Issue
Closed
opened 2025-12-29 20:22:16 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:22:16 +01:00
Owner
Copy Link

Originally created by @YoSiJo on GitHub (Dec 15, 2022).

Originally assigned to: @abhi1693 on GitHub.

Change Type

Addition

Area

Administration

Proposed Changes

In the housekeeping documentation only the way over the antiquated Cron procedure was described. This is very irritating if you consider that the rest of the stored services are already realized via Service Unit.
I have therefore already provided in a fork, a branch, in which I have established service and timer unit, as well as documentation.
For a Pull-Request I need however still one Issue assigned to me, which I request hereby. At least that's what the texts suggest to me when I want to make a pull request.

https://github.com/YoSiJo/netbox/tree/systemd-housekeeping-docs

Originally created by @YoSiJo on GitHub (Dec 15, 2022). Originally assigned to: @abhi1693 on GitHub. ### Change Type Addition ### Area Administration ### Proposed Changes In the [housekeeping documentation](https://github.com/netbox-community/netbox/blob/develop/docs/administration/housekeeping.md) only the way over the antiquated Cron procedure was described. This is very irritating if you consider that the rest of the stored services are already realized via Service Unit. I have therefore already provided in a fork, a branch, in which I have established service and timer unit, as well as documentation. For a Pull-Request I need however still one Issue assigned to me, which I request hereby. At least that's what the texts suggest to me when I want to make a pull request. https://github.com/YoSiJo/netbox/tree/systemd-housekeeping-docs
adam added the status: acceptedtype: documentation labels 2025-12-29 20:22:16 +01:00
adam closed this issue 2025-12-29 20:22:16 +01:00
adam commented 2025-12-29 20:22:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 14, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Feb 14, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:22:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 27, 2023):

@YoSiJo sorry this one hasn't gotten any attention. Would you still like to submit a PR for your proposed changes?

@jeremystretch commented on GitHub (Feb 27, 2023): @YoSiJo sorry this one hasn't gotten any attention. Would you still like to submit a PR for [your proposed changes](https://github.com/netbox-community/netbox/compare/develop...YoSiJo:netbox:systemd-housekeeping-docs)?
adam commented 2025-12-29 20:22:17 +01:00
Author
Owner
Copy Link

@YoSiJo commented on GitHub (Feb 28, 2023):

Gladly, the branch is ready and probably only needs a small rebase.
But it can be that I come temporally only on the weekend.

@YoSiJo commented on GitHub (Feb 28, 2023): Gladly, the branch is ready and probably only needs a small rebase. But it can be that I come temporally only on the weekend.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7358
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?