2
0
Fork
You've already forked cms
0

Add a motd to provide some guidance #39

Open
opened 2025年02月20日 09:50:34 +01:00 by RickCogley · 0 comments
RickCogley commented 2025年02月20日 09:50:34 +01:00 (Migrated from github.com)
Copy link

It might be user-friendly to add a message in /etc/motd (message of the day) regarding some of the key points about sysadmin for lume cms on a vps. It's a typical file that, if exists, will get displayed when you log in. On my Hetzner vps, the file did not even exist, but if you just create it, it will work.

For example:


=== WELCOME - LUME CMS TIPS ===
Lume is git cloned to ~/www
Use systemctl to control the daemons:
systemctl status lumecms
systemctl stop lumecms
systemctl start lumecms
systemctl restart lumecms
systemctl status caddy
etc
Use journalctl to check logs:
journalctl -r -u lumecms
q to quit

Of course, there's an argument to be made for not overwriting any existing /etc/motd so, in that case maybe create it in /etc/motdlume and just give a message that it's there if people want to incorporate.

Just an idea.

It might be user-friendly to add a message in `/etc/motd` (message of the day) regarding some of the key points about sysadmin for lume cms on a vps. It's a typical file that, if exists, will get displayed when you log in. On my Hetzner vps, the file did not even exist, but if you just create it, it will work. For example: ``` === WELCOME - LUME CMS TIPS === Lume is git cloned to ~/www Use systemctl to control the daemons: systemctl status lumecms systemctl stop lumecms systemctl start lumecms systemctl restart lumecms systemctl status caddy etc Use journalctl to check logs: journalctl -r -u lumecms q to quit ``` Of course, there's an argument to be made for not overwriting any existing `/etc/motd` so, in that case maybe create it in `/etc/motdlume` and just give a message that it's there if people want to incorporate. Just an idea.
Sign in to join this conversation.
No Branch/Tag specified
main
lumecms/outra-versión
lumecms/proba-2
v0.15.7
v0.15.6
v0.15.5
v0.15.4
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.16
v0.14.15
v0.14.14
v0.14.13
v0.14.12
v0.14.11
v0.14.10
v0.14.9
v0.14.8
v0.14.7
v0.14.6
v0.14.5
v0.14.4
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.0
v0.13.0-beta.1
v0.13.0-beta.0
v0.12.5
v0.12.4
v0.12.3
v0.12.2
v0.12.1
v0.12.0
v0.11.5
v0.11.4
v0.11.3
v0.11.2
v0.11.1
v0.11.0
v0.10.5
v0.10.4
v0.10.3
v0.10.2
v0.10.1
v0.10.0
v0.9.4
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.3
v0.8.2
v0.8.1
v0.8.0
v0.7.7
v0.7.6
v0.7.5
v0.7.4
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.10
v0.5.9
v0.5.8
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.11
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
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
lume/cms#39
Reference in a new issue
lume/cms
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?