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

installation: 'systemctl start/enable postgresql' only needed in CentOS #7335

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

Originally created by @koratfood on GitHub (Dec 8, 2022).

Change Type

Correction

Area

Installation/upgrade

Proposed Changes

In netbox/docs/installation/1-postgresql.md, lines 33-36 are written as though they apply to both Ubuntu and CentOS. However, on Ubuntu, most services (postgresql included) are automatically both started and enabled as part of the standard dpkg installation process. Although attempting to start an already-started systemd service instance does not hurt anything, it really serves no practical purpose.

I therefore propose that lines 33-36 be made exclusive to the CentOS section where it is actually needed. As the current CentOS-exclusive content terminates right above these lines, it should be a simple matter of indenting them.

Also, systemctl start postgresql and systemctl enable postgresql can both be performed with the single line systemctl --now enable postgresql. I propose that this be changed accordingly, possibly replacing the current 'systemctl start' line with a very brief explanation of the '--now' option.

Please feel free to assign this to me if you want, and I can submit a PR.
Thanks.

Originally created by @koratfood on GitHub (Dec 8, 2022). ### Change Type Correction ### Area Installation/upgrade ### Proposed Changes In netbox/docs/installation/1-postgresql.md, lines 33-36 are written as though they apply to both Ubuntu and CentOS. However, on Ubuntu, most services (postgresql included) are automatically both started and enabled as part of the standard dpkg installation process. Although attempting to start an already-started systemd service instance does not hurt anything, it really serves no practical purpose. I therefore propose that lines 33-36 be made exclusive to the CentOS section where it is actually needed. As the current CentOS-exclusive content terminates right above these lines, it should be a simple matter of indenting them. Also, `systemctl start postgresql` and `systemctl enable postgresql` can both be performed with the single line `systemctl --now enable postgresql`. I propose that this be changed accordingly, possibly replacing the current 'systemctl start' line with a very brief explanation of the '--now' option. Please feel free to assign this to me if you want, and I can submit a PR. Thanks.
adam added the type: documentationpending closure labels 2025-12-29 20:22:03 +01:00
adam closed this issue 2025-12-29 20:22:03 +01:00
adam commented 2025-12-29 20:22:03 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 7, 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 7, 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:03 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 11, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Mar 11, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#7335
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?