mirror of https://github.com/tildeclub/site
Merge branch 'master' into wiki-categories
This commit is contained in:
GitHub
commit
4c7c9dfe9d
|
|
@ -13,6 +13,7 @@ index: dep-php index.html
|
|||
%.html: source/%.md
|
||||
$(info building $@)
|
||||
@$(PANDOC) \
|
||||
--from markdown+backtick_code_blocks \
|
||||
--template wiki.tmpl \
|
||||
--lua-filter header-permalinks.lua \
|
||||
--highlight-style=custom.theme \
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ category: tilde.club
|
|||
|
||||
To get started, run the following command:
|
||||
|
||||
setup-2fa
|
||||
setup-2fa
|
||||
|
||||
Allow the command to update your Two-Factor Authentication. After running the
|
||||
command, you’ll be asked a couple of questions, the first one being:
|
||||
|
|
@ -25,7 +25,7 @@ only be used once, so they really are in case of emergency.
|
|||
You’ll then be prompted with several questions, The choices are all
|
||||
about balancing security with ease-of-use. It begins with:
|
||||
|
||||
Do you want me to update your "~/.google_authenticator" file (y/n)
|
||||
Do you want me to update your "~/.google_authenticator" file (y/n)
|
||||
|
||||
You will need to answer 'yes'(y) for two-factor authentication to work with your login.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,4 +3,4 @@ title: archive.org
|
|||
category: links
|
||||
---
|
||||
|
||||
archive.org has an archive of tilde.club at http://web.archive.org/web/*/http://tilde.club
|
||||
archive.org has an archive of tilde.club at [http://web.archive.org/web/*/http://tilde.club](http://web.archive.org/web/*/http://tilde.club)
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: bashblog
|
||||
author: deepend / benharri
|
||||
author:
|
||||
- deepend
|
||||
- benharri
|
||||
category: software
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -13,8 +13,8 @@ in the [tildeverse irc network](https://tilde.chat). the official channel for
|
|||
~club is `#club`. stop by and say hello!
|
||||
|
||||
run `chat` to open [weechat](https://weechat.org) auto-connected to our irc
|
||||
server. try launching [tmux](tmux.html) or [byobu](https://superuser.com/a/423397)
|
||||
to keep your chat session running.
|
||||
server. try launching [tmux](tmux.html), [byobu](https://superuser.com/a/423397)
|
||||
or [screen](screen.html) to keep your chat session running.
|
||||
|
||||
other clients like irssi are available as well! just connect to localhost on
|
||||
port 6667 and `/join #club`.
|
||||
|
|
|
|||
|
|
@ -20,5 +20,4 @@ develop software using the many tools available to you on tilde.club.
|
|||
|
||||
Tilde.club does cost money to run, however it all makes it worth it if the community is active and enjoying what we offer.
|
||||
|
||||
|
||||
ask on irc if you have questions!
|
||||
|
|
|
|||
|
|
@ -4,8 +4,8 @@ author: deepend
|
|||
category: tutorial
|
||||
---
|
||||
|
||||
All users can now setup their own custom 404 error page. Just add a file named 404.html in ~/public_html
|
||||
All users can now setup their own custom 404 error page. Just add a file named `404.html` in `~/public_html`
|
||||
|
||||
An example of one users custom 404: [~benharri](http://tilde.club/~benharri/not_here).
|
||||
An example of one user's custom 404: [~benharri](http://tilde.club/~benharri/not_here).
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ category: tutorial
|
|||
`git` is a version control system. It's pretty confusing at first, but
|
||||
once you sort out what it can do and can't do, it starts to get better.
|
||||
|
||||
This tutorial is pretty good: http://git-scm.com/docs/gittutorial
|
||||
This tutorial is pretty good: [http://git-scm.com/docs/gittutorial](http://git-scm.com/docs/gittutorial)
|
||||
|
||||
The best way to learn `git` is to find someone who knows `git` really
|
||||
well and sort out issues with them. Ask on [IRC](chat.html) if you get
|
||||
|
|
|
|||
|
|
@ -7,10 +7,10 @@ JSON is the "Javascript Object Notation", basically a file format for
|
|||
data that's suitable for easy processing by most modern web-based tools.
|
||||
|
||||
Several tilde.club programs expose APIs essentially by spitting out
|
||||
JSON as their output, including e.g. the list of recently updated home
|
||||
JSON as their output, including e.g. the list of recently updated home
|
||||
pages at
|
||||
|
||||
http://tilde.club/~delfuego/tilde.24h.json
|
||||
[http://tilde.club/~delfuego/tilde.24h.json](http://tilde.club/~delfuego/tilde.24h.json)
|
||||
|
||||
If you're looking to parse JSON from the command line with a minimum of
|
||||
code, the `jq` program may be your thing. `jq` is a filter that takes
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@ category: links
|
|||
|
||||
`leafnode` is a news client suitable for "leaf" nodes, that is nodes that have no downstream feeds.
|
||||
|
||||
http://leafnode.sourceforge.net/
|
||||
[http://leafnode.sourceforge.net/](http://leafnode.sourceforge.net/)
|
||||
|
|
@ -148,9 +148,9 @@ Back at our command line, lets type the command `id`:
|
|||
|
||||
The `id` command is a tool to show us how the system keeps track of us. From this we can see that according to the system, our user ID (or uid) is 501, and our group id is also 501.
|
||||
|
||||
- Homework
|
||||
- Run `id` in your own directory, then run
|
||||
- Run `id -u root`
|
||||
- use the `grep` command to find your uid in the `/etc/passwd` file
|
||||
- Homework
|
||||
- Run `id` in your own directory, then run
|
||||
- Run `id -u root`
|
||||
- use the `grep` command to find your uid in the `/etc/passwd` file
|
||||
|
||||
As noted above, we can obtain our group id using the `id` command. Try locating your group in `/etc/group` using the commands that were specified above; your group name will probably be the same as your user (although at times this might not be true depending on the configuration of the system).
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ category: links
|
|||
|
||||
``slrn`` is a news reader for [Usenet](usenet-news.html).
|
||||
|
||||
Documentation for slrn can be found at http://slrn.sourceforge.net
|
||||
Documentation for slrn can be found at [http://slrn.sourceforge.net](http://slrn.sourceforge.net)
|
||||
|
||||
Tilde-specific slrn info is on http://tilde.club/~joeld/slrn.html
|
||||
Tilde-specific slrn info is on [http://tilde.club/~joeld/slrn.html](http://tilde.club/~joeld/slrn.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -6,21 +6,18 @@ category: software
|
|||
|
||||
On OS X:
|
||||
|
||||
Download the lastest version of OSXFUSE: [http://osxfuse.github.io/](http://osxfuse.github.io/)
|
||||
brew install sshfs
|
||||
- Download the lastest version of OSXFUSE: [http://osxfuse.github.io/](http://osxfuse.github.io/)
|
||||
- `brew install sshfs`
|
||||
|
||||
|
||||
Now you can mount a ssh server by issuing the following commands:
|
||||
|
||||
mkdir tilde.club
|
||||
sshfs jeffbonhag@tilde.club:/home/jeffbonhag tilde.club
|
||||
|
||||
|
||||
|
||||
mkdir tilde.club
|
||||
sshfs jeffbonhag@tilde.club:/home/jeffbonhag tilde.club
|
||||
|
||||
If you're on Linux and want to make an entry in your fstab:
|
||||
|
||||
mkdir -p /mnt/tilde.club
|
||||
mkdir -p /mnt/tilde.club
|
||||
|
||||
Put an entry in your `/etc/fstab` like this:
|
||||
|
||||
|
|
@ -28,12 +25,12 @@ jeffbonhag@tilde.club:/home/jeffbonhag /mnt/tilde.club fuse.sshfs _netdev,user,
|
|||
|
||||
then you can do
|
||||
|
||||
mount /mnt/tilde.club
|
||||
mount /mnt/tilde.club
|
||||
|
||||
If you want to use an identity file to mount instead of a password, this may
|
||||
work (untested):
|
||||
|
||||
jeffbonhag@tilde.club:/home/jeffbonhag /mnt/tilde.club fuse.sshfs _netdev,user,idmap=user,transform_symlinks,identityfile=/home/USER_C/.ssh/id_rsa,allow_other,default_permissions,uid=USER_C_ID,gid=GROUP_C_ID,umask=0 0 0
|
||||
jeffbonhag@tilde.club:/home/jeffbonhag /mnt/tilde.club fuse.sshfs _netdev,user,idmap=user,transform_symlinks,identityfile=/home/USER_C/.ssh/id_rsa,allow_other,default_permissions,uid=USER_C_ID,gid=GROUP_C_ID,umask=0 0 0
|
||||
|
||||
Although -- do you really need to do this? It just occurred to me that the
|
||||
first command is just as easy, and probably makes more sense.
|
||||
|
|
|
|||
|
|
@ -11,5 +11,5 @@ to find the correct timezone name that you'll need to export as the `TZ` environ
|
|||
for example, if you're in eastern time, add something like this
|
||||
`export TZ="America/Detroit"`
|
||||
|
||||
to your `.bashrc` .
|
||||
to your `.bashrc`
|
||||
|
||||
|
|
|
|||
|
|
@ -9,6 +9,6 @@ tilde.club via a network that does not allow high UDP ports; with a properly
|
|||
configured tunnel, you can still run [[mosh]] as your shell and keep on
|
||||
truckin.
|
||||
|
||||
https://code.google.com/p/tunnelblick/
|
||||
[https://tunnelblick.net/](https://tunnelblick.net/)
|
||||
|
||||
To find a VPN endpoint, see the [VPN Gate](vpn-gate.html) project.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ category: links
|
|||
evade censorship and filtering by setting up VPN tunnels. It was
|
||||
designed with the Great Firewall of China in mind.
|
||||
|
||||
http://www.vpngate.net/en/
|
||||
[http://www.vpngate.net/en/](http://www.vpngate.net/en/)
|
||||
|
||||
You may need client side software to make this work; [tunnelblick](tunnelblick.html) is one
|
||||
such service on the Mac.
|
||||
|
|
|
|||
|
|
@ -11,19 +11,20 @@ or maybe you just found a typo on one of the existing pages!
|
|||
follow these steps to submit a change.
|
||||
|
||||
1. grab a copy of the site's source code
|
||||
```bash
|
||||
git clone https://github.com/tildeclub/site tilde.club && cd tilde.club/wiki
|
||||
```
|
||||
|
||||
git clone https://github.com/tildeclub/site tilde.club && cd tilde.club/wiki
|
||||
|
||||
1. make a new article or update an existing one. make sure that you create the
|
||||
2. make a new article or update an existing one. make sure that you create the
|
||||
title and author keys in the yaml frontmatter (see an existing article for
|
||||
an example)
|
||||
|
||||
1. submit the code via a PR on github or with git-send-email(1) to root@tilde.club
|
||||
3. submit the code via a PR on github or with git-send-email(1) to root@tilde.club
|
||||
see [git-send-email.io](https://git-send-email.io) for more info on how to use
|
||||
it. if you're working locally on tilde.club, you won't have to configure
|
||||
anything; git will use the system's sendmail to handle the email.
|
||||
|
||||
1. profit???
|
||||
4. profit???
|
||||
|
||||
ask on irc if you have questions!
|
||||
ask on [irc](chat.html#irc) if you have questions!
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,9 @@ $highlighting-css$
|
|||
</nav>
|
||||
<hr>
|
||||
$endif$
|
||||
$body$
|
||||
<!-- unindent body so that code blocks don't have extra indents. See
|
||||
https://stackoverflow.com/questions/42773587/code-block-formatting-issues-with-bootstrap-and-pandoc -->
|
||||
$body$
|
||||
$for(include-after)$
|
||||
$include-after$
|
||||
$endfor$
|
||||
|
|
|
|||
Loading…
Reference in New Issue