forked from unitoo/configurations
Racchiude una serie di file utili per configurare vari applicativi, sia lato server sia lato client.
|
|
||
|---|---|---|
| apache | ||
| emacs | ||
| erpnext/print-formats | ||
| etc/systemd/system | ||
| git | ||
| grafana/dashboards | ||
| grub | ||
| IAM | ||
| iptables | ||
| lynis/etc/lynis | ||
| modprobe/etc/modprobe.d | ||
| mysql | ||
| neovim | ||
| nextcloud | ||
| pam/etc/pam.d | ||
| postgresql | ||
| prometheus/exporters/etc | ||
| rc.local/etc | ||
| redis/etc | ||
| security/etc/security | ||
| solargraph | ||
| ssh/etc/ssh | ||
| sysctl/etc | ||
| terminal/alacritty | ||
| usr/local/bin | ||
| COPYING | ||
| README.md | ||
dot-files
Unitoo standardized dotfiles.
Directory Logic
The directory tree logic is the following: program_name/program_name.extension.
Each conf file can have an associated Markdown file named program_name/program_name.md.
You can also put the conf inside the actual path of the configuration file following this logic: program_name/path/to/conf/program_name.conf
Examples:
neovim/neovim.confnginx/etc/nginx/nginx.confnginx/etc/nginx/nginx.md
Syntax highlighting
In order to display the proper syntax highlighting on Gitea, you should use the appropriate file extension as described here: https://github.com/alecthomas/chroma
Support
unitoo.it · Mastodon @unitoo · GitHub @UnitooTeam