mirror of https://git.envs.net/envs/help.git
make sure in some parts the user use the username
This commit is contained in:
parent
6e8c7dda2b
commit
2ad1e3f09c
|
@ -8,7 +8,7 @@ you can create a script called `~/.efingerd` which will be run when anyone finge
|
|||
## querying
|
||||
the standard query for finger is simply
|
||||
|
||||
`finger user@envs.net`
|
||||
`finger username@envs.net`
|
||||
|
||||
which displays login name, home directory, shell, real name, current login time, idle time, whether or not the user has mail, and the contents of the user's `~/.plan`, `~/.project` and `~/.tz` file.
|
||||
|
||||
|
|
24
docs/help.md
24
docs/help.md
|
@ -54,11 +54,11 @@ you can check the records yourself with the `dig` tool like this:
|
|||
ports 22, 80, 443, 2222 and 2223 are available for ssh
|
||||
use ssh.envs.net to reach the secondary ip and use 80 and 443 for ssh.
|
||||
so, for example, you can do:
|
||||
`ssh user@envs.net`
|
||||
`ssh -p2223 user@envs.net`
|
||||
`ssh username@envs.net`
|
||||
`ssh -p2223 username@envs.net`
|
||||
|
||||
or for the secondary ip:
|
||||
`ssh -p443 user@ssh.envs.net`
|
||||
`ssh -p443 username@ssh.envs.net`
|
||||
|
||||
!!! tip
|
||||
if you have a slightly shaky connection then you can also use `mosh`.
|
||||
|
@ -90,7 +90,7 @@ define ssh host aliase in `~/.ssh/config`
|
|||
Host envs.net
|
||||
HostName envs.net
|
||||
Port 2223
|
||||
User user
|
||||
User username
|
||||
LocalForward localhost:6667 localhost:6667
|
||||
```
|
||||
|
||||
|
@ -121,7 +121,7 @@ from URL (on remote machine)
|
|||
`echo $(curl -sL https://example.com/id_rsa.pub) | tee -a ~/.ssh/authorized_keys`
|
||||
|
||||
over ssh (on local machine)
|
||||
`ssh-copy-id -i ~/.ssh/id_rsa.pub -p2223 user@envs.net;`
|
||||
`ssh-copy-id -i ~/.ssh/id_rsa.pub -p2223 username@envs.net;`
|
||||
|
||||
### ssh remote execution
|
||||
`ssh envs.net ping google.de`
|
||||
|
@ -134,19 +134,19 @@ exec a local script
|
|||
|
||||
## # scp usage
|
||||
copy ssh pub key to remote:
|
||||
`scp -P 2223 ~/.ssh/authorized_keys user@envs.net:~/.ssh/authorized_keys`
|
||||
`scp -P 2223 ~/.ssh/authorized_keys username@envs.net:~/.ssh/authorized_keys`
|
||||
|
||||
copy website index.html from remote:
|
||||
`scp -P 2223 user@envs.net:~/public_www/index.html ~/public_www/`
|
||||
`scp -P 2223 username@envs.net:~/public_www/index.html ~/public_www/`
|
||||
|
||||
## # rsync usage
|
||||
sync website to remote:
|
||||
`rsync -avz -e "ssh -p 2223" ~/public_www user@envs.net:~`
|
||||
`rsync -avz -e "ssh -p 2223" ~/public_www username@envs.net:~`
|
||||
sync website from remote:
|
||||
`rsync -avz -e "ssh -p 2223" user@envs.net:~/public_www ~/`
|
||||
`rsync -avz -e "ssh -p 2223" username@envs.net:~/public_www ~/`
|
||||
|
||||
## # sftp usage
|
||||
connect: `sftp -oPort=2223 user@envs.net`
|
||||
connect: `sftp -oPort=2223 username@envs.net`
|
||||
|
||||
### commands:
|
||||
exit: `exit`
|
||||
|
@ -173,8 +173,8 @@ add `~/.ssh/authorized_keys:`
|
|||
`put .ssh/authorized_keys .ssh/authorized_keys`
|
||||
|
||||
### single line usage (on local machine)
|
||||
to remote: `sftp -P 2223 user@envs.net:remotedir <<< $'put localfile_path'`
|
||||
from remote: `sftp -P 2223 user@envs.net:remotefile localfile`
|
||||
to remote: `sftp -P 2223 username@envs.net:remotedir <<< $'put localfile_path'`
|
||||
from remote: `sftp -P 2223 username@envs.net:remotefile localfile`
|
||||
|
||||
## # your shell
|
||||
avaliable shells: `ash`, `bash`, `csh`, `dash`, `elvish`, `fish`, `ksh`, `mksh`, `sash`, `sh`, `tcsh`, `xonsh`, `yash`, `zsh`
|
||||
|
|
|
@ -31,7 +31,7 @@ create an account on any of these services as you like.
|
|||
|
||||
### # code related stuff
|
||||
- [gitea](https://git.envs.net/) - git with a cup of tea. - lightweight code hosting solution.
|
||||
members can be use your email credantials for login. (*user@envs.net* | *your email pw*)
|
||||
members can be use your email credantials for login. (*username@envs.net* | *your email pw*)
|
||||
- [drone](https://drone.envs.net/) - drone is a container-native, continuous delivery platform.
|
||||
(includes a "drone-ssh-runner" and "drone-docker-runner".)
|
||||
|
||||
|
|
Loading…
Reference in New Issue