mirror of https://github.com/tildeclub/site.git
import more wiki articles, and exclude unmodified users from listing
This commit is contained in:
parent
29fc72c85f
commit
c5671542a0
11
index.php
11
index.php
|
@ -3,7 +3,7 @@
|
|||
<h1>$ welcome to tilde.club</h1>
|
||||
<p><a href="/wiki/faq.html">Questions? See the official FAQ.</a></p>
|
||||
|
||||
<p class="advisory">SERVICE ADVISORY: New Server, New Owners, New lease on life for tilde.club. Welcome!.<br> The Expected SSH Hostkey is SHA256:duamOATgnGcfRFFkotCwrAWzZtRjwxm64WAhq5tQRwE.</p>
|
||||
<p class="advisory">SERVICE ADVISORY: New Server, New Owners, New lease on life for tilde.club. Welcome back ~clubbers!!.<br> The Expected SSH Hostkey is SHA256:duamOATgnGcfRFFkotCwrAWzZtRjwxm64WAhq5tQRwE.</p>
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
|
@ -20,9 +20,18 @@
|
|||
</p>
|
||||
|
||||
<h3>here are the home pages of our users</h3>
|
||||
<p>if you're not seeing yourself listed here, change your page from the default.</p>
|
||||
|
||||
<ol>
|
||||
<?php foreach (glob("/home/*") as $user) {
|
||||
$index = "$user/public_html/index.html";
|
||||
if (!file_exists($index) ||
|
||||
in_array(sha1_file($index),
|
||||
// these are the hashes of previous and current default pages
|
||||
["0eb53dab435e2e6e401921146bed85a80e9ad3a1",
|
||||
"61eff8202777bae134ac4b11f1e16ec23dfc97d3",
|
||||
"e9d41eab6edb7cd375c63ecb4a23bca928992547",
|
||||
"13af6898f536265af7dbbe2935b591f5e2ee0d7d"])) continue;
|
||||
$user = basename($user); ?>
|
||||
<li><a href="/~<?=$user?>/">~<?=$user?></a></li>
|
||||
<?php } ?>
|
||||
|
|
|
@ -0,0 +1,38 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>Editing your index.html file</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">Editing your index.html file</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>Type: <code>nano</code> index.html to open your index.html file and begin editing</p>
|
||||
<figure>
|
||||
<img src="http://tilde.club/~annika/static/nano.png" alt="screenshot of the nano editor" /><figcaption>screenshot of the nano editor</figcaption>
|
||||
</figure>
|
||||
<p>Edit your file, willy nilly</p>
|
||||
<p>When done editing, use <code>CTRL+X</code> to close the file</p>
|
||||
<p>You’ll be asked if you want to save; say y and [return] to return to the command line</p>
|
||||
<p>Refresh your tilde page in your browser to see your new website</p>
|
||||
<p>Note: If at any time you feel you made a mistake in editing, you can exit and n to not save.</p>
|
||||
<p>There’s more info here about the [[nano]] editor; if you’re familiar with [[emacs]] or [[vim]] they are here too.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>Finding your index.html file</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">Finding your index.html file</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>There are some basic command line commands you’ll want to Google and learn, but for this tutorial you only need a few:</p>
|
||||
<p><code>ls</code> = list files and folders in current directory</p>
|
||||
<p><code>cd</code> = change directories</p>
|
||||
<p><code>vim</code>, <code>emacs</code>, <code>nano</code> = a text editor</p>
|
||||
<p>Type: <code>ls</code> to see where you are; you should see a directory called “public_html”</p>
|
||||
<p>Type: <code>cd public_html</code> to browse into that folder</p>
|
||||
<p>Type: <code>ls</code> to see where you are; you should see your index.html file</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,33 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>JSON</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">JSON</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>JSON is the “Javascript Object Notation”, basically a file format for data that’s suitable for easy processing by most modern web-based tools.</p>
|
||||
<p>Several tilde.club programs expose APIs essentially by spitting out JSON as their output, including e.g. the list of recently updated home pages at</p>
|
||||
<p>http://tilde.club/~delfuego/tilde.24h.json</p>
|
||||
<p>If you’re looking to parse JSON from the command line with a minimum of code, the <code>jq</code> program may be your thing. <code>jq</code> is a filter that takes JSON on standard input and produces JSON on standard output. Along the way in the middle you can do various standard sorts of file munging on a field by field basis.</p>
|
||||
<p><a href="http://stedolan.github.io/jq/manual/">Documentation for <code>jq</code> is in its manual.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>Resetting your editor view when chat interrupts</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">Resetting your editor view when chat interrupts</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>You may have been caught off guard while editing and had some random chat messages muss up your view. It didn’t actually edit your HTML page but you need to reset your editor view.</p>
|
||||
<p><code>CTRL+L</code> will reset your view</p>
|
||||
<p><code>mesg n</code> at the command prompt will turn off chat messages in that window.</p>
|
||||
<p>If you don’t ever want to see wall messages on your screen, put <code>mesg n</code> into your startup file (details of how to do that needed here).</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
---
|
||||
title: safe scripting the tilde way
|
||||
author: michaelcoyote
|
||||
---
|
||||
|
||||
Welcome to tilde.club. For many of you this may be your first multi-user host and for even more of you this may be your *first* host. Welcome to all of you.
|
||||
|
||||
Whether you are used to Unix, Linux and programming or a complete beginner please consider this an invitation to create and build new things.
|
||||
|
||||
It's important when creating however that we respect the shared environment and that we respect the boundaries of others.
|
||||
|
||||
As Paul says:
|
||||
|
||||
> no drama. be respectful. have fun.
|
||||
|
||||
What does that mean with respect to scripting and programming on a shared host?
|
||||
|
||||
- DOs
|
||||
- Respect shared CPU/Disk/Network resources
|
||||
- Keep things that require a tilde.club login local to the server (don't post publicly) :
|
||||
- Finger info
|
||||
- local home directory files such as `~/.plan` and `~/.profile` files
|
||||
- Note that exceptions could include an opt-in file or special permissions from the user.
|
||||
- Respect `robots.txt` when writing web crawlers
|
||||
|
||||
In short use your common sense and consider how your actions may affect others.
|
||||
|
||||
If you are unsure if something is a good idea or not, head to irc or message using the `wall` command and ask others what they think.
|
||||
|
||||
If you want a conclusive answer, contact one of the system operators.
|
||||
|
||||
##### Thinking privacy
|
||||
|
||||
Consider the source of the data.
|
||||
|
||||
E.g. We know that finger data might contain personal data such as phone numbers, and other identifying information and is not generally available without a tilde.club login.
|
||||
|
||||
Before exposing data such as this to the world, it should check for an opt in file such as the .public file file test before presenting info to the outside world.
|
||||
|
||||
#### Shared Resources
|
||||
|
||||
- In general
|
||||
- Consider executing long running processes during overnight hours when fewer users are on the system
|
||||
- CPU
|
||||
- Use the `nice` command to keep intensive processes from affecting others
|
||||
- The `nice -n19 -p$$` placed in a script will make sure it runs at the lowest priority.
|
||||
- Run a long command at the lowest CPU priority: `nice -n 19 ~/bin/command`
|
||||
- Change the priority of process 923 (also known as "re-nicing a process") : `renice -17 -p923`
|
||||
- Disk
|
||||
- On any commands that will heavily use disk, consider using the `ionice` command so that scripts will not affect interactive users
|
||||
- By adding the `ionice -c3 -p$$` command to any script, it will only use disk when idle.
|
||||
- You can also run a command or script: `ionice -c3 -t ~/bin/command`
|
|
@ -0,0 +1,31 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>VPN Gate</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">VPN Gate</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p><code>VPN Gate</code> is a project from U Tsukuba in Japan that allows you to evade censorship and filtering by setting up VPN tunnels. It was designed with the Great Firewall of China in mind.</p>
|
||||
<p>http://www.vpngate.net/en/</p>
|
||||
<p>You may need client side software to make this work; [[tunnelblick]] is one such service on the Mac.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,29 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>archive.org</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">archive.org</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>archive.org has an archive of tilde.club at http://web.archive.org/web/*/http://tilde.club</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -6,7 +6,7 @@
|
|||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<meta name="author" content="emv" />
|
||||
<meta name="author" content="benharri" />
|
||||
<title>Socializing</title>
|
||||
<title>Socializing and chat</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
|
@ -21,7 +21,7 @@ div.column{display: inline-block; vertical-align: top; width: 50%;}
|
|||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">Socializing</h1>
|
||||
<h1 class="title">Socializing and chat</h1>
|
||||
|
||||
<p>authors:</p>
|
||||
<p class="author"><a href="/~emv/">~emv</a></p>
|
||||
|
|
|
@ -0,0 +1,64 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>git usage</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">git usage</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p><code>git</code> 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.</p>
|
||||
<p>This tutorial is pretty good: http://git-scm.com/docs/gittutorial</p>
|
||||
<p>The best way to learn <code>git</code> is to find someone who knows <code>git</code> really well and sort out issues with them. Ask on [[IRC]] if you get stuck. (There should be a better buddy system for this, but until there is, we do what we can.)</p>
|
||||
<p>A good introduction to <code>git</code> is to create a repository for your <code>public_html</code> directory. This will allow you to back up your public web directory.</p>
|
||||
<p>First thing you will want to do is set up git.</p>
|
||||
<p>If you don’t have a <a href="http://github.com">GitHub</a> account, you will want one for this exercise. If you choose another Git host, you will need to work out some parts of this setup on your own.</p>
|
||||
<p>Once you have a git account, you will want to set up <code>git</code> for your tilde.club account. Use the email address that you used to create your GitHub account. You can register multiple accounts with GitHub if needed.</p>
|
||||
<pre><code>git config --global user.name "Your Name Here"
|
||||
git config --global user.email youremail@example.org</code></pre>
|
||||
<p>You will also want to create a <code>.gitignore</code> file. This file defines what things you want git to ignore, such as editor temporary files or directories you may not want to keep in <code>git</code> such as generated files or private files you upload to a public repository. The <code>.gitignore</code> file can be created in your home directory, but I like to create it in the project directory.</p>
|
||||
<p>Here is an example <code>.gitignore</code> file:</p>
|
||||
<pre><code># files being edited
|
||||
*~
|
||||
*swp
|
||||
# Generated files
|
||||
tilde_graphs
|
||||
# Private files
|
||||
diary.txt</code></pre>
|
||||
<p>Now go create a repository on GitHub. In our examples we are using mytildeweb as the repo name, but you can choose whatever name works for you. If you do change the repository name be sure to update the commands with the proper one.</p>
|
||||
<p>Now we should be ready to create and upload the repository.</p>
|
||||
<pre><code>cd public_html/
|
||||
# This will initialize public_html as a repository
|
||||
git init
|
||||
# Adds all files to the repo. "." means "the current directory" (public_html, in this case)
|
||||
# Note: you can also add files one at a time
|
||||
git add .
|
||||
# Commits files to local repo
|
||||
git commit -m "first commit of tildeweb"
|
||||
# Tells git where your remote repo is
|
||||
git remote add origin https://github.com/<yourgithubuser>/mytildeweb.git
|
||||
# Uploads to the remote repo
|
||||
git push -u origin master</code></pre>
|
||||
<p>Your files should now be on GitHub. If you make a change and you want to update, do the following after making your edits:</p>
|
||||
<pre><code>git add index.html
|
||||
git commit -m "updated blog"
|
||||
git push origin master</code></pre>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,30 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>Leafnode</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">Leafnode</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p><code>leafnode</code> is a news client suitable for “leaf” nodes, that is nodes that have no downstream feeds.</p>
|
||||
<p>http://leafnode.sourceforge.net/</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
title: Editing your index.html file
|
||||
---
|
||||
|
||||
Type: `nano` index.html to open your index.html file and begin editing
|
||||
|
||||

|
||||
|
||||
Edit your file, willy nilly
|
||||
|
||||
When done editing, use `CTRL+X` to close the file
|
||||
|
||||
You'll be asked if you want to save; say y and [return] to return to the command line
|
||||
|
||||
Refresh your tilde page in your browser to see your new website
|
||||
|
||||
Note: If at any time you feel you made a mistake in editing, you can exit and n to not save.
|
||||
|
||||
There's more info here about the [[nano]] editor; if you're familiar with
|
||||
[[emacs]] or [[vim]] they are here too.
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
title: Finding your index.html file
|
||||
---
|
||||
|
||||
There are some basic command line commands you'll want to Google and learn, but for this tutorial you only need a few:
|
||||
|
||||
`ls` = list files and folders in current directory
|
||||
|
||||
`cd` = change directories
|
||||
|
||||
`vim`, `emacs`, `nano` = a text editor
|
||||
|
||||
Type: `ls` to see where you are; you should see a directory called "public_html"
|
||||
|
||||
Type: `cd public_html` to browse into that folder
|
||||
|
||||
Type: `ls` to see where you are; you should see your index.html file
|
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
title: JSON
|
||||
---
|
||||
|
||||
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
|
||||
pages at
|
||||
|
||||
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
|
||||
JSON on standard input and produces JSON on standard output. Along the
|
||||
way in the middle you can do various standard sorts of file munging on
|
||||
a field by field basis.
|
||||
|
||||
[Documentation for `jq` is in its manual.](http://stedolan.github.io/jq/manual/)
|
|
@ -0,0 +1,12 @@
|
|||
---
|
||||
title: Resetting your editor view when chat interrupts
|
||||
---
|
||||
|
||||
You may have been caught off guard while editing and had some random chat messages muss up your view. It didn't actually edit your HTML page but you need to reset your editor view.
|
||||
|
||||
`CTRL+L` will reset your view
|
||||
|
||||
`mesg n` at the command prompt will turn off chat messages in that window.
|
||||
|
||||
If you don't ever want to see wall messages on your screen, put `mesg n`
|
||||
into your startup file (details of how to do that needed here).
|
|
@ -0,0 +1,12 @@
|
|||
---
|
||||
title: VPN Gate
|
||||
---
|
||||
|
||||
`VPN Gate` is a project from U Tsukuba in Japan that allows you to
|
||||
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/
|
||||
|
||||
You may need client side software to make this work; [[tunnelblick]] is one
|
||||
such service on the Mac.
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
title: archive.org
|
||||
---
|
||||
|
||||
archive.org has an archive of tilde.club at http://web.archive.org/web/*/http://tilde.club
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Socializing
|
||||
title: Socializing and chat
|
||||
author:
|
||||
- emv
|
||||
- benharri
|
||||
|
|
|
@ -0,0 +1,56 @@
|
|||
---
|
||||
title: git usage
|
||||
---
|
||||
|
||||
`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
|
||||
|
||||
The best way to learn `git` is to find someone who knows `git` really well and sort out issues with them. Ask on [[IRC]] if you get stuck. (There should be a better buddy system for this, but until there is, we do what we can.)
|
||||
|
||||
A good introduction to `git` is to create a repository for your `public_html` directory. This will allow you to back up your public web directory.
|
||||
|
||||
First thing you will want to do is set up git.
|
||||
|
||||
If you don't have a [GitHub](http://github.com) account, you will want one for this exercise. If you choose another Git host, you will need to work out some parts of this setup on your own.
|
||||
|
||||
Once you have a git account, you will want to set up `git` for your tilde.club account. Use the email address that you used to create your GitHub account. You can register multiple accounts with GitHub if needed.
|
||||
|
||||
git config --global user.name "Your Name Here"
|
||||
git config --global user.email youremail@example.org
|
||||
|
||||
You will also want to create a `.gitignore` file. This file defines what things you want git to ignore, such as editor temporary files or directories you may not want to keep in `git` such as generated files or private files you upload to a public repository. The `.gitignore` file can be created in your home directory, but I like to create it in the project directory.
|
||||
|
||||
Here is an example `.gitignore` file:
|
||||
|
||||
# files being edited
|
||||
*~
|
||||
*swp
|
||||
# Generated files
|
||||
tilde_graphs
|
||||
# Private files
|
||||
diary.txt
|
||||
|
||||
Now go create a repository on GitHub. In our examples we are using mytildeweb as the repo name, but you can choose whatever name works for you. If you do change the repository name be sure to update the commands with the proper one.
|
||||
|
||||
Now we should be ready to create and upload the repository.
|
||||
|
||||
cd public_html/
|
||||
# This will initialize public_html as a repository
|
||||
git init
|
||||
# Adds all files to the repo. "." means "the current directory" (public_html, in this case)
|
||||
# Note: you can also add files one at a time
|
||||
git add .
|
||||
# Commits files to local repo
|
||||
git commit -m "first commit of tildeweb"
|
||||
# Tells git where your remote repo is
|
||||
git remote add origin https://github.com/<yourgithubuser>/mytildeweb.git
|
||||
# Uploads to the remote repo
|
||||
git push -u origin master
|
||||
|
||||
Your files should now be on GitHub. If you make a change and you want to update, do the following after making your edits:
|
||||
|
||||
git add index.html
|
||||
git commit -m "updated blog"
|
||||
git push origin master
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
title: Leafnode
|
||||
---
|
||||
|
||||
`leafnode` is a news client suitable for "leaf" nodes, that is nodes that have no downstream feeds.
|
||||
|
||||
http://leafnode.sourceforge.net/
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
title: SSHFS
|
||||
---
|
||||
|
||||
With `sshfs` you can mount your tilde directory as a drive.
|
||||
|
||||
See http://tilde.club/~jeffbonhag/sshfs.txt for a tutorial.
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
title: tmux
|
||||
---
|
||||
|
||||
TMUX IS THE BEST. Here's a super basic primer.
|
||||
|
||||
to start a new session, type `tmux new -s tildemux`.
|
||||
|
||||
A yellow bar will appear at the bottom of your terminal. You're now in TMUX!
|
||||
|
||||
TMUX has sessions, windows, and panes. Each of these things will have a terminal in it. If you actually typed what I told you to earlier, you'll be in a session named `tildemux`. That session has one window, `0`. That window has one pane, also named `0`. (Computers start counting at 0, not 1.)
|
||||
|
||||
## windows
|
||||
|
||||
Your tmux bar should look like:
|
||||
|
||||
`[tildemux] 0:bash*`
|
||||
|
||||
…which means that you're in a session named `tildemux`, which has a window `0`, running the command `bash`. `*` means that window 0 is active, and the pane running bash is currently active.
|
||||
|
||||
To create a new window within this session, type `PREFIX c`. PREFIX?!? By default, it's `control-b`. Now you should see:
|
||||
|
||||
`[tildemux] 0:bash- 1:bash*`
|
||||
|
||||
`1:bash*` means you're in a pane running `bash` inside window 1. To change back to pane 0, type `PREFIX 0`. The `*` should be back on `0:bash`.
|
||||
|
||||
Run a cool interactive command, such as `htop` (to see how many of system resources we're eating up) or `vim` (to write some awesome webpages). Your tmux status bar should update to `0:<name of the current process>`. So now instead of saying `bash` it will say `htop` or `vim`.
|
||||
|
||||
## panes
|
||||
|
||||
Panes are great. TMUX panes let you run more than one terminal inside your one, actual terminal. To "split" a new pane, `PREFIX "`. That makes a horizontal split. You'll notice there are now two panes open one on top of the other. `PREFIX %` makes a vertical split, for side-by-side panes. Did I mention that panes are great?
|
||||
|
||||
To move between panes in the current window, use `PREFIX <up,down,left,right>`. That's right, the arrow keys.
|
||||
|
||||
## more
|
||||
|
||||
I not the best writer or teacher. Just google anything that doesn't make sense.
|
||||
|
||||
[Or take a look at this tmux guide](http://robots.thoughtbot.com/a-tmux-crash-course)
|
||||
|
||||
But definitely use tmux.
|
|
@ -0,0 +1,13 @@
|
|||
---
|
||||
title: Tunnelblick
|
||||
---
|
||||
|
||||
`tunnelblick` is an application for your Mac that allows you to configure
|
||||
and manage VPN sessions. You can use this e.g. if you are connecting to
|
||||
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/
|
||||
|
||||
To find a VPN endpoint, see the [[VPN Gate]] project.
|
|
@ -0,0 +1,18 @@
|
|||
---
|
||||
title: .vimrc file
|
||||
---
|
||||
|
||||
The file `.vimrc` in your home directory has instructions for [[vim]]
|
||||
to load every time it runs. Customizations go there.
|
||||
|
||||
For instance, you might want to use [[Markdown]] to edit files that
|
||||
end in `.md`. The system default for some reason is to treat these as
|
||||
[[Modula-2]] files, though we don't have a Modula-2 compiler running
|
||||
(yet). So the contents of `.vimrc` should read
|
||||
|
||||
``
|
||||
au BufRead,BufNewFile *.md set filetype=markdown
|
||||
``
|
||||
|
||||
For more suggestions in deep depth on how to set up your `.vimrc` please read
|
||||
[this tutorial from Doug Black](http://dougblack.io/words/a-good-vimrc.html).
|
|
@ -0,0 +1,30 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>SSHFS</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">SSHFS</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>With <code>sshfs</code> you can mount your tilde directory as a drive.</p>
|
||||
<p>See http://tilde.club/~jeffbonhag/sshfs.txt for a tutorial.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,47 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>tmux</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">tmux</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>TMUX IS THE BEST. Here’s a super basic primer.</p>
|
||||
<p>to start a new session, type <code>tmux new -s tildemux</code>.</p>
|
||||
<p>A yellow bar will appear at the bottom of your terminal. You’re now in TMUX!</p>
|
||||
<p>TMUX has sessions, windows, and panes. Each of these things will have a terminal in it. If you actually typed what I told you to earlier, you’ll be in a session named <code>tildemux</code>. That session has one window, <code>0</code>. That window has one pane, also named <code>0</code>. (Computers start counting at 0, not 1.)</p>
|
||||
<h2 id="windows">windows</h2>
|
||||
<p>Your tmux bar should look like:</p>
|
||||
<p><code>[tildemux] 0:bash*</code></p>
|
||||
<p>…which means that you’re in a session named <code>tildemux</code>, which has a window <code>0</code>, running the command <code>bash</code>. <code>*</code> means that window 0 is active, and the pane running bash is currently active.</p>
|
||||
<p>To create a new window within this session, type <code>PREFIX c</code>. PREFIX?!? By default, it’s <code>control-b</code>. Now you should see:</p>
|
||||
<p><code>[tildemux] 0:bash- 1:bash*</code></p>
|
||||
<p><code>1:bash*</code> means you’re in a pane running <code>bash</code> inside window 1. To change back to pane 0, type <code>PREFIX 0</code>. The <code>*</code> should be back on <code>0:bash</code>.</p>
|
||||
<p>Run a cool interactive command, such as <code>htop</code> (to see how many of system resources we’re eating up) or <code>vim</code> (to write some awesome webpages). Your tmux status bar should update to <code>0:<name of the current process></code>. So now instead of saying <code>bash</code> it will say <code>htop</code> or <code>vim</code>.</p>
|
||||
<h2 id="panes">panes</h2>
|
||||
<p>Panes are great. TMUX panes let you run more than one terminal inside your one, actual terminal. To “split” a new pane, <code>PREFIX "</code>. That makes a horizontal split. You’ll notice there are now two panes open one on top of the other. <code>PREFIX %</code> makes a vertical split, for side-by-side panes. Did I mention that panes are great?</p>
|
||||
<p>To move between panes in the current window, use <code>PREFIX <up,down,left,right></code>. That’s right, the arrow keys.</p>
|
||||
<h2 id="more">more</h2>
|
||||
<p>I not the best writer or teacher. Just google anything that doesn’t make sense.</p>
|
||||
<p><a href="http://robots.thoughtbot.com/a-tmux-crash-course">Or take a look at this tmux guide</a></p>
|
||||
<p>But definitely use tmux.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,31 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>Tunnelblick</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">Tunnelblick</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p><code>tunnelblick</code> is an application for your Mac that allows you to configure and manage VPN sessions. You can use this e.g. if you are connecting to 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.</p>
|
||||
<p>https://code.google.com/p/tunnelblick/</p>
|
||||
<p>To find a VPN endpoint, see the [[VPN Gate]] project.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
<!DOCTYPE html>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
||||
<head>
|
||||
<meta charset="utf-8" />
|
||||
<meta name="generator" content="pandoc" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
||||
<title>.vimrc file</title>
|
||||
<link rel="stylesheet" href="/style.css">
|
||||
<style type="text/css">
|
||||
code{white-space: pre-wrap;}
|
||||
span.smallcaps{font-variant: small-caps;}
|
||||
span.underline{text-decoration: underline;}
|
||||
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
||||
</style>
|
||||
<!--[if lt IE 9]>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
|
||||
<![endif]-->
|
||||
</head>
|
||||
<body>
|
||||
<a href="/wiki/">< back to wiki home</a>
|
||||
<header>
|
||||
<h1 class="title">.vimrc file</h1>
|
||||
|
||||
|
||||
</header>
|
||||
<p>The file <code>.vimrc</code> in your home directory has instructions for [[vim]] to load every time it runs. Customizations go there.</p>
|
||||
<p>For instance, you might want to use [[Markdown]] to edit files that end in <code>.md</code>. The system default for some reason is to treat these as [[Modula-2]] files, though we don’t have a Modula-2 compiler running (yet). So the contents of <code>.vimrc</code> should read</p>
|
||||
<p><code>au BufRead,BufNewFile *.md set filetype=markdown</code></p>
|
||||
<p>For more suggestions in deep depth on how to set up your <code>.vimrc</code> please read <a href="http://dougblack.io/words/a-good-vimrc.html">this tutorial from Doug Black</a>.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
Loading…
Reference in New Issue