mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-26 21:30:55 +08:00
shipsw
commit
896b66504b
@ -1,3 +1,5 @@
|
||||
Translating by shipsw
|
||||
|
||||
Ubuntu 14.04 LTS: Major Application Updates
|
||||
================================================================================
|
||||
Over the last few weeks, we have been talking about the first new LTS version from Ubuntu in two years and some of the major changes to the operating system that you can expect to see once you take the plunge. Today, we are going to list some of the major applications available from the Ubuntu Software Center and the upgrades they have undergone since the last update to Ubuntu’s LTS OS.
|
||||
@ -37,4 +39,4 @@ via:https://linuxacademy.com/blog/linux/ubuntu-14-04-lts-major-application-updat
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
@ -1,3 +1,5 @@
|
||||
alim0x translating
|
||||
|
||||
Ubuntu on Surface Pro 3 – not smooth yet but promising
|
||||
================================================================================
|
||||
|
||||
@ -21,4 +23,4 @@ via: http://www.muktware.com/2014/05/ubuntu-surface-pro-3-smooth-yet-promising/2
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.microsoft.com/surface/en-us/products/surface-pro-3
|
||||
[2]:https://www.youtube.com/watch?v=mRH-c2_kDA4
|
||||
[2]:https://www.youtube.com/watch?v=mRH-c2_kDA4
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
Command Line Tuesdays – The Introductory
|
||||
================================================================================
|
||||
**Hi Geekos!**
|
||||
|
||||
Today we’re introducing a new series, called ‘Command Line Tuesdays‘. Why command line Tuesdays? Because in this series, everyday computer enthusiasts like yours truly, will try to step a little out of bounds of the Graphical User Interface (GUI) Culture, which is today synonymous to ‘making stuff easier for the masses‘.
|
||||
|
||||
Of course, if you visited any of the GNU/Linux related community forums, you’ve probably read, and this is an assumption, a very fiery debate over which is actually easier. Using GUI for everything, or simply learning and enjoying the Command-line Interface (CLI).
|
||||
|
||||
|
||||
Terminal
|
||||
|
||||
There are many arguments for or against the use of GUI tools. One of the most commonly referred pros is that we’ve been brought up in the point-and-click computing paradigm, so it’s basically a form of a language, or culture if you may, in which we interact with our machine. The patterns are mostly recurring, with big button clicking doing everything we need it to do.
|
||||
|
||||
On the other side, one of the most interesting comments I’ve read about the pros of command-line was: you can simply do more via the command-line much quicker, easier and faster than when using GUI tools. But there’s a catch: you have to learn the commands. Yes, learn them, as if learning a poem.
|
||||
Now, since to us, the semi-indoctrinated clueless users, it all sounds like some useless geek overreaching and overdoing, let me humanize it with a fable:
|
||||
|
||||
### The Fable ###
|
||||
|
||||
I’ve been using Linux for more then 3 years now. I’m a 27 year old literature major, who never held much of an interest in technology of any sort. I didn’t even own a computer until I was in high-school, so let’s say somewhere around 17. That’s barely ten years of computer usage. The only three programs I ever ran were BS Player, Winamp and Football Manager, with occasional usage of MS Word. Three and bit years ago, a colleague at a precarious job I was performing at the time was talking to another coworker, saying there’s a new edition of something which immediately occupied my attention, as it looked different. It was Ubuntu’s Natty Narwhal, I think. After discussing it with him, he pointed out the usual pros we gospel to the newcomers, no antivirus necessary, faster boot, better security, software center blah blah blah, and the peak of it: Free and Open Source (FOSS) philosophy behind it. And he did it in a very non-invasive, non fanboyish manner.
|
||||
|
||||
I decided to give it a go, and I never turned back since then. How I got into openSUSE around the 11.4 release, shortly after trying out Ubuntu for the first time is going to have to fit in another time, and how I find it to be the perfect sweet spot is a whole different story. The point is, I finally entered the Linux realm. It was fun, it was different, it made my computer run better, it was more stable. I barely had issues with it (seems I not-knowingly purchased fairly orthodox hardware). It seems that Linux came really far regarding the desktop, so I barely had to use the terminal. But let’s just say it was one of the most dreadful, terrifying and horrific tools to use in Linux. If there wasn’t a GUI for a specific operation, I immediately became nervous as I didn’t know what I was getting into when copy/pasting commands from the forums.
|
||||
After time, things changed. As opposed to other consumer-oriented systems, what happened to me was maybe somewhat of a human reverse-engineering. Instead of me consuming the system, I feel that in three years, the system consumed me. I learned how to search for basic issues, file bug reports, properly ask questions on forums. With every issue I had, I learned how to be better at providing the information needed for someone more competent to help me with my problem.
|
||||
|
||||
A short while ago, my girlfriend commented how she can’t believe I’m using my computer mostly for the sake of using the computer, rather than doing anything else. ‘You use it only for your music collection and Linux thingies, Nenad. Gaawd.’ It made me think, and think hard. Linux, specifically the openSUSE distro has become a hobby of mine. Not at an expert level, by any means, which is reasonable since it isn’t my area of expertise. But I know enough to get around, fix minor issues, play around with some configuration files etc. But what I came to know, is that with my increasing playing and tinkering around the system, I really need to get familiar with CLI. I learned that I’m playing around without knowing of the basics under the hood. What for crying out loud is ETC?!?!? What’s BIN? Why is there .sh at the end? Why is this file here, and this file there? Why do I have to click through gazillion of folders to find the right file to modify? Then I read you can easily list all the files somewhere with a single command. It became interesting. I suddenly felt an urge to try it out.
|
||||
|
||||
### So Let’s Do It! ###
|
||||
|
||||
…and here we are. As a new openSUSE news contributor, I’ll try to contribute in a way I see productive for what I suppose is a large portion of the community. It’s time to plant the banner and start learning the command-line together. If philosophy is what attracted you to Linux and openSUSE, like me, it got you this far. Now it’s time to take a step further.
|
||||
|
||||
|
||||
|
||||
Look, I know there’s a bunch of you like me out there. I know you maybe don’t see the point in all that 90′s geeky black-screen-green-letters-quick-typing-make-everything-go-boom thing. But it’s useful in many aspects. We’ll learn in a fun and communal way which directories are for what, what files are located where, most commonly used terminal commands. It will make our lives easier when we learn to perform tasks through the console, make it even more rewarding when we run into issues. It will also make the lives of bug-squashers easier when they receive proper information from our end, and it will make our hobby infinitely more fun.
|
||||
I mean, for crying out loud, you’ve already made a transition to a phase where Dilbert and xkcd are actually funny. It’s time for the terminal!
|
||||
|
||||
P.S.:
|
||||
|
||||
Reference material that will be used: William Shotts – The Linux Command Line and a short tutorial on most commonly used commands by a Croatian hacker Velimir Baksa aka Lutherus. Requirements on your part:
|
||||
- An hour or two of spare time weekly
|
||||
– A pint of cold beer or any other beverage
|
||||
– Someone already pointed out that using [Gedit][1], or a manual notepad (you know, pen and paper hehe) would be good for easier learning.
|
||||
|
||||
The book by Mr Shotts is exquisite. But there’s probably an issue of time/will-power etc. This way, I’ll try to humanize the lessons a bit more, take some time off your hands, and what’s most important – I count on us learning together, helping each other together (Comments and Forums, people!!) and tying a close-knit openSUSE community! This time next week (it will be June already!), we’ll learn our first commands. And remember…
|
||||
|
||||
**…have a lot of fun!**
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://news.opensuse.org/2014/05/27/command-line-tuesdays-the-introductory/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://software.opensuse.org/package/gedit
|
||||
@ -0,0 +1,375 @@
|
||||
Install RainLoop Webmail (A Web Based Email Client) using ‘Nginx and Apache’ in Arch Linux
|
||||
================================================================================
|
||||
Rainloop is a free Open Source web application written in PHP which provides a fast modern web interface to access your emails on all major domain mail providers like Yahoo, Gmail, Outlook and many others as well as your own local mail servers, and, also, acts as a MUA (Mail User Agent) by accessing domain mail servers through IMAP and SMTP protocols.
|
||||
|
||||
#### RainLoop Demo ####
|
||||
|
||||
Have a quick look at the demo page setup by the author at [http://demo.rainloop.net/][1].
|
||||
|
||||
|
||||
Install RainLoop in Arch Linux
|
||||
|
||||
Once you have deployed Rainloop on your servers the only thing remaining to do is to access your Rainloop domain through a web browser and provide credentials for your enabled domain mail server.
|
||||
|
||||
This tutorial covers **Rainloop** webmail installation process on **Arch Linux** from both point of view configuration files for **Apache** and **Nginx**, using a virtual local domain configured through local hosts file, without a DNS server.
|
||||
|
||||
If you also need references on installing Rainloop on **Debian** and **Red Hat** systems visit the previous RainLoop Webmail article at.
|
||||
|
||||
- [Install RainLoop Webmail on Debian and Red Hat based Systems][2]
|
||||
|
||||
### Requirements ###
|
||||
|
||||
#### For Nginx ####
|
||||
|
||||
- [Install LEMP (Nginx, PHP, MySQL with MariaDB engine and PhpMyAdmin) in Arch Linux][3]
|
||||
- [Create Virtual Hosts in Nginx Web Server][4]
|
||||
|
||||
#### For Apache ####
|
||||
|
||||
- [Install LAMP (Linux, Apache, MySQL/MariaDB, and PHP/PhpMyAdmin) in Arch Linux][5]
|
||||
|
||||
### Step 1: Create Virtual Hosts for Nginx or Apache ###
|
||||
|
||||
**1.** Assuming that you have configured your servers (**Nginx** or **Apache**) as described in upper presentations links, the first thing you need to do is to create a rudimentary **DNS** entry on local **hosts** file that points to **Arch Linux** system IP.
|
||||
|
||||
On Linux system edit **/etc/hosts** file and include your Rainloop virtual domain after localhost entry.
|
||||
|
||||
127.0.0.1 localhost.localdomain localhost rainloop.lan
|
||||
192.168.1.33 rainloop.lan
|
||||
|
||||
|
||||
Add Domain Host Entry
|
||||
|
||||
On Windows system edit **C:\Windows\System32\drivers\etc\hosts** and add the following line at the bottom.
|
||||
|
||||
192.168.1.33 rainloop.lan
|
||||
|
||||
**2.** After you verify local domain using **ping** command, create the necessary **Virtual Hosts** and **SSL** configurations for **Apache** or **Nginx**.
|
||||
|
||||
#### Nginx Virtual Hosts ####
|
||||
|
||||
Create a file named **rainloop.lan** in **/etc/nginx/sites-available/** path with the following configuration.
|
||||
|
||||
$ sudo nano /etc/nginx/sites-available/rainloop.conf
|
||||
|
||||
Add the following file content.
|
||||
|
||||
server {
|
||||
listen 80;
|
||||
server_name rainloop.lan;
|
||||
|
||||
rewrite ^ https://$server_name$request_uri? permanent;
|
||||
access_log /var/log/nginx/rainloop.lan.access.log;
|
||||
error_log /var/log/nginx/rainloop.lan.error.log;
|
||||
root /srv/www/rainloop/;
|
||||
|
||||
# serve static files
|
||||
location ~ ^/(images|javascript|js|css|flash|media|static)/ {
|
||||
root /srv/www/rainloop/;
|
||||
expires 30d;
|
||||
}
|
||||
|
||||
location / {
|
||||
index index.html index.htm index.php;
|
||||
autoindex on;
|
||||
autoindex_exact_size off;
|
||||
autoindex_localtime on;
|
||||
}
|
||||
|
||||
location ^~ /data {
|
||||
deny all;
|
||||
}
|
||||
|
||||
location ~ \.php$ {
|
||||
#fastcgi_pass 127.0.0.1:9000; (depending on your php-fpm socket configuration)
|
||||
fastcgi_pass unix:/run/php-fpm/php-fpm.sock;
|
||||
fastcgi_index index.php;
|
||||
include fastcgi.conf;
|
||||
}
|
||||
}
|
||||
|
||||
Then create the SSL equivalent file content.
|
||||
|
||||
$ sudo nano /etc/nginx/sites-available/rainloop-ssl.conf
|
||||
|
||||
Add the following file content.
|
||||
|
||||
server {
|
||||
listen 443 ssl;
|
||||
server_name rainloop.lan;
|
||||
|
||||
ssl_certificate /etc/nginx/ssl/rainloop.lan.crt;
|
||||
ssl_certificate_key /etc/nginx/ssl/rainloop.lan.key;
|
||||
ssl_session_cache shared:SSL:1m;
|
||||
ssl_session_timeout 5m;
|
||||
ssl_ciphers HIGH:!aNULL:!MD5;
|
||||
ssl_prefer_server_ciphers on;
|
||||
|
||||
access_log /var/log/nginx/rainloop.lan.access.log;
|
||||
error_log /var/log/nginx/rainloop.lan.error.log;
|
||||
|
||||
root /srv/www/rainloop/;
|
||||
|
||||
# serve static files
|
||||
location ~ ^/(images|javascript|js|css|flash|media|static)/ {
|
||||
root /srv/www/rainloop/;
|
||||
expires 30d;
|
||||
}
|
||||
|
||||
location ^~ /data {
|
||||
deny all;
|
||||
}
|
||||
|
||||
location / {
|
||||
index index.html index.htm index.php;
|
||||
autoindex on;
|
||||
autoindex_exact_size off;
|
||||
autoindex_localtime on;
|
||||
}
|
||||
|
||||
location ~ \.php$ {
|
||||
#fastcgi_pass 127.0.0.1:9000; (depending on your php-fpm socket configuration)
|
||||
fastcgi_pass unix:/run/php-fpm/php-fpm.sock;
|
||||
fastcgi_index index.php;
|
||||
include fastcgi.conf;
|
||||
}
|
||||
}
|
||||
|
||||
On the next step generate **Certificate** file and **Keys** for **SSL Virtual Host** and add your virtual domain name (**rainloop.lan**) on Certificate **Common Name**.
|
||||
|
||||
$ sudo nginx_gen_ssl.sh
|
||||
|
||||
|
||||
Generate Certificate and Keys
|
||||
|
||||
After the Certificate and SSL keys are generated, create Rainloop **root** webserver file path ( place where Rainloop PHP files reside), then enable Virtual Hosts and restart Nginx daemon to apply configurations.
|
||||
|
||||
$ sudo mkdir -p /srv/www/rainloop
|
||||
$ sudo n2ensite rainloop
|
||||
$ sudo n2ensite rainloop-ssl
|
||||
$ sudo systemctl restart nginx
|
||||
|
||||
|
||||
Create RainLoop Web Director
|
||||
|
||||
#### Apache Virtual Hosts ####
|
||||
|
||||
Create a new file named **rainloop.conf** in **/etc/httpd/conf/sites-available/** with the following content.
|
||||
|
||||
$ sudo nano /etc/httpd/conf/sites-available/rainloop.conf
|
||||
|
||||
Add the following file content.
|
||||
|
||||
<VirtualHost *:80>
|
||||
ServerName rainloop.lan
|
||||
DocumentRoot "/srv/www/rainloop/"
|
||||
ServerAdmin you@example.com
|
||||
ErrorLog "/var/log/httpd/rainloop-error_log"
|
||||
TransferLog "/var/log/httpd/rainloop-access_log"
|
||||
|
||||
<Directory />
|
||||
Options +Indexes +FollowSymLinks +ExecCGI
|
||||
AllowOverride All
|
||||
Order deny,allow
|
||||
Allow from all
|
||||
Require all granted
|
||||
</Directory>
|
||||
|
||||
</VirtualHost>
|
||||
|
||||
|
||||
Create Apache Virtual Host
|
||||
|
||||
Then create the SSL equivalent file content for Apache.
|
||||
|
||||
$ sudo nano /etc/httpd/conf/sites-available/rainloop-ssl.conf
|
||||
|
||||
Add the following file content.
|
||||
|
||||
<VirtualHost *:443>
|
||||
ServerName rainloop.lan
|
||||
DocumentRoot "/srv/www/rainloop/"
|
||||
ServerAdmin you@example.com
|
||||
ErrorLog "/var/log/httpd/rainloop-ssl-error_log"
|
||||
TransferLog "/var/log/httpd/rainloop-ssl-access_log"
|
||||
|
||||
SSLEngine on
|
||||
SSLCertificateFile "/etc/httpd/conf/ssl/rainloop.lan.crt"
|
||||
SSLCertificateKeyFile "/etc/httpd/conf/ssl/rainloop.lan.key"
|
||||
|
||||
<FilesMatch "\.(cgi|shtml|phtml|php)$">
|
||||
SSLOptions +StdEnvVars
|
||||
</FilesMatch>
|
||||
|
||||
BrowserMatch "MSIE [2-5]" \
|
||||
nokeepalive ssl-unclean-shutdown \
|
||||
downgrade-1.0 force-response-1.0
|
||||
|
||||
CustomLog "/var/log/httpd/ssl_request_log" \
|
||||
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
|
||||
|
||||
<Directory />
|
||||
Options +Indexes +FollowSymLinks +ExecCGI
|
||||
AllowOverride All
|
||||
Order deny,allow
|
||||
Allow from all
|
||||
Require all granted
|
||||
</Directory>
|
||||
|
||||
</VirtualHost>
|
||||
|
||||
The next step is to create **SSL Certificate** file and **Keys** for **SSL Virtual Host** and add put your virtual domain name (**rainloop.lan**) on Certificate **Common Name**.
|
||||
|
||||
$ sudo apache_gen_ssl
|
||||
|
||||
|
||||
Create SSL Certificate and Keys
|
||||
|
||||
|
||||
Enter Organization Details
|
||||
|
||||
After the Certificate and SSL keys are created, add Rainloop **DocumentRoot** path, then enable Virtual Hosts and restart Apache daemon to apply configurations.
|
||||
|
||||
$ sudo mkdir -p /srv/www/rainloop
|
||||
$ sudo a2ensite rainloop
|
||||
$ sudo a2ensite rainloop-ssl
|
||||
$ sudo systemctl restart httpd
|
||||
|
||||
|
||||
Enable Virtual Hosts
|
||||
|
||||
### Step 2: Add necessary PHP Extensions ###
|
||||
|
||||
**3.** Whether you are using **Apache** or **Nginx** webserver, you need to enable the following PHP extensions on **php.ini** file and, also, include the new webserver **DocumentRoot** path to open_basedir directive.
|
||||
|
||||
$ sudo nano /etc/php/php.ini
|
||||
|
||||
Locate and uncomment the following PHP extensions.
|
||||
|
||||
extension=iconv.so
|
||||
extension=imap.so
|
||||
extension=mcrypt.so
|
||||
extension=mssql.so
|
||||
extension=mysqli.so
|
||||
extension=openssl.so ( enables IMAPS and SMTP SSL protocols on mail servers)
|
||||
extension=pdo_mysql.so
|
||||
|
||||
Also open_basedir statement should look like this.
|
||||
|
||||
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/etc/webapps/:/srv/www/
|
||||
|
||||
**4.** After the **php.ini** file was modified restart your server than check **phpinfo** file to see if **SSL** protocols are enabled.
|
||||
|
||||
----------On Apache Web Server----------
|
||||
$ sudo systemctl restart httpd
|
||||
|
||||
----------
|
||||
|
||||
----------On Nginx Web Server----------
|
||||
$ sudo systemctl restart nginx
|
||||
$ sudo systemctl restart php-fpm
|
||||
|
||||
|
||||
Check PHP Information
|
||||
|
||||
### Step 3: Download and Install RainLoop Webmail ###
|
||||
|
||||
**5.** Now it’s time to download and extract Rainloop application from official website to Document Root directory but first install **wget** and **unzip** system utilities.
|
||||
|
||||
$ sudo pacman -S unzip wget
|
||||
|
||||
**6.** Download latest source package Rainloop zip archive using **wget** command or by using a browser to navigate to [http://rainloop.net/downloads/][6].
|
||||
|
||||
$ wget http://repository.rainloop.net/v1/rainloop-latest.zip
|
||||
|
||||
|
||||
Download RainLoop Package
|
||||
|
||||
**7.** After the download process finishes, extract Rainloop archive to Virtual Host Document Root path ( **/srv/www/rainloop/** ).
|
||||
|
||||
$ sudo unzip rainloop-latest.zip -d /srv/www/rainloop/
|
||||
|
||||
|
||||
Extract Rainloop Archive
|
||||
|
||||
**8.** Then set the following permissions on application default path.
|
||||
|
||||
$ sudo chmod -R 755 /srv/www/rainloop/
|
||||
$ sudo chown -R http:http /srv/www/rainloop/
|
||||
|
||||
|
||||
Set Permission on RainLoop
|
||||
|
||||
### Step 4: Configure Rainloop via Web Interface ###
|
||||
|
||||
**9.** Rainloop application can be configured in two ways: using a system shell of via browser. If you want to configure over terminal open and edit **application.ini** file located in **/srv/www/rainloop/data/_data_da047852f16d2bc7352b24240a2f1599/_default_/configs/**.
|
||||
|
||||
**10.** To access Admin Interface from browser, use the following URL address **https://rainloop.lan/?admin**, then provide the default application credentials.
|
||||
|
||||
User= admin
|
||||
Password= 12345
|
||||
|
||||
|
||||
Rainloop Web Interface
|
||||
|
||||
**11.** After initial login you will be warn to change the default password, so I advise you to do it.
|
||||
|
||||
|
||||
Change Default Password
|
||||
|
||||
|
||||
Set New Admin Password
|
||||
|
||||
**12.** If you want to enable **contacts** login to MySQL database and create a new database with a privileged user on it, then provide database credentials on **Contacts** fields.
|
||||
|
||||
mysql -u root -p
|
||||
create database if not exists rainloop;
|
||||
create user rainloop_user@localhost identified by “password”;
|
||||
grant all privileges on rainloop.* to rainloop_user@localhost;
|
||||
flush privileges;
|
||||
exit;
|
||||
|
||||
|
||||
Enable Contacts in RainLoop
|
||||
|
||||
|
||||
Enter Contact Database Details
|
||||
|
||||
**13.** By default Rainloop provides **Gmail**, **Yahoo** and **Outlook** domains mail server configuration files, but you can add other mail server domains if you like.
|
||||
|
||||
|
||||
Default Mail Domains
|
||||
|
||||
|
||||
Add New Domain
|
||||
|
||||
**14.** To login on your mail server point your browser to **https://rainloop.lan** and provide your domain server credentials.
|
||||
|
||||
|
||||
Login to Mail Domain
|
||||
|
||||
|
||||
Login to Gmail Domain
|
||||
|
||||
|
||||
RainLoop Email Interface
|
||||
|
||||
For further configurations please visit official Rainloop documentation page at [http://rainloop.net/docs/][7].
|
||||
|
||||
With Rainloop you can access mail servers from any device that has a browser as long as your server has Internet connectivity, the only minus of using Rainloop application in Arch Linux so far is the lack of poppassd plugin package needed to change email account password.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.tecmint.com/install-rainloop-webmail-in-arch-linux/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://demo.rainloop.net/
|
||||
[2]:http://www.tecmint.com/rainloop-webmail-a-modern-fast-web-based-email-client-for-linux/
|
||||
[3]:http://www.tecmint.com/install-nginx-php-mysql-with-mariadb-engine-and-phpmyadmin-in-arch-linux/
|
||||
[4]:http://www.tecmint.com/create-virtual-hosts-using-nginx-on-arch-linux/
|
||||
[5]:http://www.tecmint.com/install-lamp-in-arch-linux/
|
||||
[6]:http://rainloop.net/downloads/
|
||||
[7]:http://rainloop.net/docs/
|
||||
Loading…
Reference in New Issue
Block a user