forked from team/site
fix numbering on markdown files
This commit is contained in:
parent
474571ac0c
commit
1847394cfb
|
@ -36,14 +36,14 @@ This tutorial will teach you the few commands that should allow you to take care
|
|||
When you're first starting to use a shell in a UNIX-like environment, you will want to be able to do the following things:
|
||||
|
||||
1. logging in and logging out
|
||||
1. list the files or directories in a directory
|
||||
1. move between directories
|
||||
1. read, write, and save files
|
||||
1. create new files or directories
|
||||
1. move or copy files between directories
|
||||
1. delete files or directories
|
||||
1. download files from elsewhere on the internet
|
||||
1. learn more about new commands
|
||||
2. list the files or directories in a directory
|
||||
3. move between directories
|
||||
4. read, write, and save files
|
||||
5. create new files or directories
|
||||
6. move or copy files between directories
|
||||
7. delete files or directories
|
||||
8. download files from elsewhere on the internet
|
||||
9. learn more about new commands
|
||||
|
||||
When you're logged into a shell, you should see a command prompt and a blinking cursor. At this point, simply type a command and hit Enter to run it. You can try this as you work through learning the commands below.
|
||||
|
||||
|
|
|
@ -39,13 +39,13 @@ location (`~/.weechat/relay_socket`). to get started using it, follow these step
|
|||
* `/set relay.network.password mysupersecretpassword` - don't use this password
|
||||
of course. note that you might already have this set.
|
||||
|
||||
1. at your shell:
|
||||
2. at your shell:
|
||||
* `chmod o+rw ~/.weechat/relay_socket` - note that other members of the team group
|
||||
are not included in the granted permissions. this allows nginx to connect
|
||||
to your socket on your behalf. you will need to do this every time you start
|
||||
weechat as the socket doesn't exist until weechat starts up.
|
||||
|
||||
1. in your relay client:
|
||||
3. in your relay client:
|
||||
* glowing-bear:
|
||||
- $user.ttm.sh
|
||||
- port 443
|
||||
|
@ -57,9 +57,9 @@ location (`~/.weechat/relay_socket`). to get started using it, follow these step
|
|||
- relay host: $user.ttm.sh
|
||||
- relay port: 443
|
||||
- your relay password
|
||||
- (if you get "Error: Could not connect using WebSocket", check to be sure
|
||||
~/ and ~/.weechat have at least o+rx permissions so nginx can reach
|
||||
~/.weechat/relay_socket)
|
||||
- (if you get "Error: Could not connect using WebSocket", check to be sure
|
||||
~/ and ~/.weechat have at least o+rx permissions so nginx can reach
|
||||
~/.weechat/relay_socket)
|
||||
|
||||
## znc
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@ media and social media. we aim to put the users in control of the tools of
|
|||
communication that are currently being neutered by corporate commodification
|
||||
of the www.
|
||||
|
||||
1. provide tools, resources and encouragement for users to develop ideas and
|
||||
2. provide tools, resources and encouragement for users to develop ideas and
|
||||
best practices for the next generation of public access unix systems. the
|
||||
"next generation" is always ahead of the present, so this implies that the
|
||||
system is in a constant state of development and self-improvement, with a
|
||||
|
@ -27,10 +27,10 @@ continually rolling set of goals, and regular testing and evaluation of
|
|||
experimental projects. --all of which is powered by user involvement in a
|
||||
brainstorming/experimenting/teaching/learning/doing model.
|
||||
|
||||
1. serve partly as a meta-community among other tildes and pubnixes, both
|
||||
3. serve partly as a meta-community among other tildes and pubnixes, both
|
||||
sharing best practices and learning from their experiences.
|
||||
|
||||
1. last but absolutely not least --> MAKE IT FUN! it should not be a bitter
|
||||
4. last but absolutely not least --> MAKE IT FUN! it should not be a bitter
|
||||
place to sulk or rant about mainstream culture. it should be a social
|
||||
environment in which users can go wild and push their creative skills to the
|
||||
limit. it should be a place to appreciate what does not exist in other
|
||||
|
|
|
@ -20,9 +20,9 @@ change to your ~/public_html/blog directory: `cd ~/public_html/blog`
|
|||
|
||||
1. `bb post`
|
||||
|
||||
1. write a post (it will open your preferred $EDITOR for you, so make sure it's set)
|
||||
2. write a post (it will open your preferred $EDITOR for you, so make sure it's set)
|
||||
|
||||
1. save, close, and then select from the bashblog menu choices
|
||||
3. save, close, and then select from the bashblog menu choices
|
||||
|
||||
|
||||
---
|
||||
|
|
|
@ -14,7 +14,7 @@ tmux or screen session. let's use systemd user units to manage it!
|
|||
|
||||
mkdir -p ~/.config/systemd/user/
|
||||
|
||||
1. create a basic service. save something like this in
|
||||
2. create a basic service. save something like this in
|
||||
`~/.config/systemd/user/my-new-service.service` (using the name of the unit
|
||||
you're creating)
|
||||
|
||||
|
@ -27,11 +27,11 @@ you're creating)
|
|||
[Install]
|
||||
WantedBy=default.target
|
||||
|
||||
1. enable it
|
||||
3. enable it
|
||||
|
||||
systemctl --user enable --now my-new-service.service
|
||||
|
||||
1. enable-linger for your user account
|
||||
4. enable-linger for your user account
|
||||
|
||||
loginctl enable-linger
|
||||
|
||||
|
|
Loading…
Reference in New Issue