mirror of
https://github.com/YunoHost/doc.git
synced 2024-09-03 20:06:26 +02:00
translation of certain articles to english
This commit is contained in:
parent
7e11e96da8
commit
16200b87c3
3 changed files with 153 additions and 0 deletions
36
dns.md
Normal file
36
dns.md
Normal file
|
@ -0,0 +1,36 @@
|
|||
# DNS
|
||||
|
||||
DNS configuration is a crucial stage for rendering your server accessible to the wider Internet. If your DNS is poorly configured, you are liable to have a lot of problems in connecting to your server via your domain name.
|
||||
|
||||
*Even though this page appears long and complex, it is very important to understand the implications of Internet domain names, which are necessary for the proper function of your Yunohost server.*
|
||||
|
||||
### What is it?
|
||||
|
||||
DNS stands for "Domain Name Server", and is often used for the configuration of your domain names. Your domain names must point at a specific identifier (generally at an IP address.)
|
||||
|
||||
**For example**: `yunohost.org` points to the server at `88.191.153.110`.
|
||||
|
||||
This system was created to more easily keep track of server addresses. There are DNS registries for Internet names that you must register with. They are called "registrars", which will let you rent certain domain names for a price (between $5 or a few hundred, depending on the root domain and the chosen name). These registrars are private entities authorised by [ICANN](http://fr.wikipedia.org/wiki/ICANN), such as [Gandi](http://gandi.net), [NameCheap](http://namecheap.com) or [BookMyName](http://bookmyname.com).
|
||||
|
||||
It is important to note that subdomains do not necessarily have to send you to wherever the principal domain is pointing. If `yunohost.org` sends to `88.191.153.110`, that doesn't mean that `backup.yunohost.org` has to point at the same IP. You must therefore configure **all** of the domains and subdomains that you want to use.
|
||||
|
||||
There are also different **types** of DNS records, which means that a domain can point at something other than an IP address.
|
||||
|
||||
**For example**: `www.yunohost.org` will send you to `yunohost.org`
|
||||
|
||||
### How to (properly) set up a DNS name?
|
||||
|
||||
You have several choices here. Note that you can mix and match solutions if you have multiple domains: for example, you can have `my-server.nohost.me` using solution **1.**, et `my-server.org` using solution **2.**, both leading to the same Yunohost server.
|
||||
|
||||
1. You can use YunoHost's DNS service, which will automatically configure your DNS for you. You must choose a domain that ends with `.nohost.me` or `noho.st` for this, which may be inconvenient for you (you would then only be able to use an email address like `john@my-server.noho.st`).
|
||||
**This is the recommended option if you are just starting out with self-hosting.**
|
||||
|
||||
2. You can use the DNS service offered by your **registrar** (Gandi, NameCheap, BookMyName or others) to configure your domain name. Check out these pages for specific documentation:
|
||||
* [OVH](#/OVH)
|
||||
* [Gandi](#/Gandi)
|
||||
* [BookMyName](#/BookMyName)
|
||||
<br><br>**Warning**: If you choose this option, you will have more configuration possibilities, but nothing will be done for you. For example, if you want to use `webmail.my-server.org`, you must add it manually to the DNS records with your registrar.
|
||||
|
||||
3. Your YunoHost instance has its own DNS service, which means it will automatically configure its own DNS records, and that you can leave the setup to the instance itself. To do this, you must explain to your **registrar** that your YunoHost instance is the authoritative DNS server for your domain name.
|
||||
|
||||
<br><br>**Warning**: If you choose this option, all configuration options will be dome automatically, you will retain a good deal of flexibility, but if your server gets knocked offline you will run into many problems. **Choose this only if you are certain.**
|
30
history.md
Normal file
30
history.md
Normal file
|
@ -0,0 +1,30 @@
|
|||
# Histoire
|
||||
|
||||
YunoHost was created in February 2012 after something like this:
|
||||
|
||||
<blockquote><p>"Shit, I'm too lazy to reconfigure my mail server... Beudbeud, how were you able to get your little server running with LDAP?"</p>
|
||||
<small>Kload, February 2012</small></blockquote>
|
||||
|
||||
All that was needed was an administration interface for Beudbeud's server to make something usable, so Kload decided to develop one. Finally, after automating several configurations and packaging in some web apps, YunoHost v1 was finished.
|
||||
|
||||
Noting the growing enthusiasm around YunoHost and around self-hosting in general, the original developers along with new contributors decided to start work on version 2, more extensible, more powerful, more easy-to-use, and one that makes a nice cup of fair-trade coffee for the elves of Lapland.
|
||||
|
||||
|
||||
### Goal
|
||||
|
||||
YunoHost's goal is to make installing and administering a server accessible to as many people as possible, without taking away from the quality and reliability of the software.
|
||||
|
||||
Everything is done with the goal of simplifying deployment on as many different kinds of hardware as possible, and in any condition (at home, on a dedicated server or on a VPS).
|
||||
|
||||
|
||||
### Name
|
||||
|
||||
**YunoHost** comes from the jargon "Y U NO Host". The [Internet meme](https://en.wikipedia.org/wiki/Internet_meme) should illustrate it:
|
||||
<div class="text-center"><img src="http://cdn.memegenerator.net/instances/500x/43427997.jpg"></div>
|
||||
|
||||
|
||||
### Development
|
||||
|
||||
YunoHost is developed to be as **simple** and minimally-intrusive as possible, to retain compatibility with Debian. It merely proposes a package of automatic configurations for existing software, and is configurable via simple interfaces.
|
||||
|
||||
YunoHost is **entirely** a free software project. The philosophy of self-hosting is, to us, incompatible with any other model of software development.
|
87
install_on_cubieboard.md
Normal file
87
install_on_cubieboard.md
Normal file
|
@ -0,0 +1,87 @@
|
|||
# Installing YunoHost on CubieBoard
|
||||
|
||||
### Requirements
|
||||
* CubieBoard & µ-SD of at least 4GB
|
||||
* Internet access
|
||||
* Access to server administration
|
||||
|
||||
### Images for Debian 7 Wheezy adapted for CubieBoard 1 and 2:
|
||||
|
||||
* [Cubian](http://cubian.org/)
|
||||
* [Cubieez](http://www.cubieforums.com/index.php?topic=442.0)
|
||||
|
||||
### Copy the Image to the µ-SD
|
||||
#### via the graphical interface (recommended)
|
||||
With the "Disks" application in Debian and its derivatives, select the µ-SD and choose "Restore Disk Image".
|
||||
|
||||
#### via the command line
|
||||
Get the device name of the µ-SD (/dev/...) with :
|
||||
```bash
|
||||
df -h
|
||||
```
|
||||
Write the image to disk from the folder you downloaded it to:
|
||||
```bash
|
||||
(sudo) dd if=/image/debian/ of=/dev/<µ-SD> bs=1M && sync
|
||||
```
|
||||
### Expand the Partition
|
||||
Expand the Partition using GParted.
|
||||
|
||||
### Start
|
||||
Put the µ-SD in the CubieBoard and start it up.
|
||||
|
||||
### Get the local IP address of your CubieBoard
|
||||
```bash
|
||||
nmap 192.168.0.0/24 or nmap 192.168.1.0/24
|
||||
```
|
||||
### Redirect your domain name to the local IP address of the CubieBoard
|
||||
Edit /etc/hosts on your local computer:
|
||||
```bash
|
||||
(sudo) nano /etc/hosts
|
||||
```
|
||||
Add a line in the following format:
|
||||
```bash
|
||||
ip_address_of_cubieboard your_domain.org
|
||||
```
|
||||
### SSH connection
|
||||
```bash
|
||||
ssh root@votre_domaine.org
|
||||
```
|
||||
### Installing YunoHost
|
||||
|
||||
1. Install git
|
||||
```bash
|
||||
apt-get install git
|
||||
```
|
||||
|
||||
2. Clone the installation script repository
|
||||
```bash
|
||||
git clone https://github.com/YunoHost/install_script /tmp/install_script
|
||||
```
|
||||
|
||||
3. Execute the script
|
||||
```bash
|
||||
cd /tmp/install_script && ./install_yunohostv2
|
||||
```
|
||||
|
||||
### Post-installation
|
||||
|
||||
Once the installation is complete, the script will ask you to proceed to the post-install configuration. This will ask you for a few options:
|
||||
|
||||
1. **Domain name**: You must choose a domain name that will point at the IP address of your YunoHost instance. If you choose a name that ends with **.nohost.me** or **.noho.st**, the DNS configuration stage will be completed automatically and you will only need to wait for about 3 minutes for the installation to complete. If you opt for another domain name, you will need to have one purchased and [configured](#/dns) so it points at your **IP address**.
|
||||
|
||||
2. **Administrator password**: This is the password that you will need to administer your YunoHost instance, **choose it carefully**, it should not be given out or easily guessed, or else you might lose control of your system.
|
||||
|
||||
The post-install configuration will take place after this, and you will be able to access your administration interface with **https://your-domain.org/ynhadmin**
|
||||
|
||||
### Updating YunoHost
|
||||
```bash
|
||||
apt-get update && apt-get upgrade && apt-get dist-upgrade
|
||||
```
|
||||
### Opening Ports
|
||||
uPnP doesn't work just yet, so you will need to manually open the ports on your firewall or router.
|
||||
|
||||
To see the ports that need to be opened:
|
||||
|
||||
```bash
|
||||
yunohost firewall list
|
||||
```
|
Loading…
Reference in a new issue