Anmol Sharma

Ghost for YunoHost updated to version 3.41.8

Anmol Sharma

Sat, 06 Mar 2021 11:50:59 -0800 last edited: Sun, 07 Mar 2021 18:32:43 -0800

@YunoHost (yunohost@mastodon.social)
#ghost package for #yunohost has been updated to version 3.41.8.
Ghost: https://ghost.org/

To install from command-line :

$ yunohost app install https://github.com/YunoHost-Apps/ghost_ynh

To update from command-line :

$ yunohost app upgrade -u https://github.com/YunoHost-Apps/ghost_ynh ghost

Anmol Sharma

Sat, 06 Mar 2021 11:55:30 -0800

This do not render well on #Mastodon. I don't understand, why people use it, when it can't handle rich text.

Osada package for YunoHost

Anmol Sharma

Fri, 12 Feb 2021 08:36:07 -0800

@YunoHost (yunohost@mastodon.social)

#Osada package for #YunoHost has been fixed and updated. Osada uses #zot protocol.

https://github.com/YunoHost-Apps/osada_ynh

Yunohost zot

anmol

Fri, 12 Feb 2021 08:42:37 -0800

🔁 Repeated @Anmol Sharma's Note

Adminer pacakge Updated for Yunohost

Anmol Sharma

Fri, 12 Feb 2021 07:04:50 -0800

@YunoHost (yunohost@mastodon.social)
#Adminer package for #Yunohost is updated to version 4.7.8

https://github.com/YunoHost-Apps/adminer_ynh

anmol

Fri, 12 Feb 2021 08:42:54 -0800

🔁 Repeated @Anmol Sharma's Note

Signal to stay away from Signal

Anmol Sharma

Tue, 09 Feb 2021 11:06:30 -0800

Meanwhile here is the reason, one might want to stay away from the #Signal too.
https://github.com/net4people/bbs/issues/63

privacy IM

show all 8 comments

Anmol Sharma

Wed, 10 Feb 2021 08:45:34 -0800

@Jean-Baptiste (jibec@mamot.fr)
I personally don't use Signal(though it may be better solution than WA,Telegram,etc). Every few months there is a wave when people starts finding other alternatives to these semi or partially closed sourced social media services.

I don't know what you answer when people ask you "why are you not on FB,Insta, etc?", but I usually divert the question by asking them why #FB is better then Insta, #Twitter etc. Its amusing to listen to people trying to convince that one thing is better than other, when both have same goals and objectives. This have now started to happen in open source community too.

Anyways, the problem here is same as people of #China face. #Government has banned a service, which has made developers to think for a solution. Signal has introduced a #proxy service which is leaking the Ip's and Government can know whats happening under the hood. The way #TLS to #TLS proxy has been implemented by the project is to be blamed(being blamed by the experts). Further they have blocked all the other services and only access is given to #Signal. When one would make a proxy service why he/she should be limited to use only particular service.

The Nginx files tell us about this.(see the last deny command)

stream {
    map $ssl_preread_server_name $name {
        textsecure-service.whispersystems.org    signal-service;
    storage.signal.org            storage-service;
    cdn.signal.org                signal-cdn;
    cdn2.signal.org                signal-cdn2;
    api.directory.signal.org        directory;
    contentproxy.signal.org            content-proxy;
    uptime.signal.org            uptime;
    api.backup.signal.org                   backup;
        sfu.voip.signal.org                     sfu;
        updates.signal.org                      updates;
        updates2.signal.org                     updates2;
  [b]      default                    deny;[/b]
    }

The people on the thread are pointing venerability to the developers. These people are experts in their work. They maintain the projects like #V2Fly maintains #V2Ray which helps to bypass the GFC. Its totally on the developers where to take the project, but if somethings can be fixed easily with help its nothing wrong in taking it. The hard core users of the project will not see alternatives as an option and will favor to use the option which projects has to offer.

You can see the repo here: https://web.archive.org/web/20210208074012/https://github.com/signalapp/Signal-TLS-Proxy

Look at this article: https://web.archive.org/web/20210208015243/https://www.bleepingcomputer.com/news/security/signal-ignores-proxy-censorship-vulnerability-bans-researchers/

You may want to read this tread too, where @HansWolters (hanswolters@federate.hopto.org) has shown his concerns. https://federate.hopto.org/channel/hanswolters?mid=b64.aHR0cHM6Ly9mZWRlcmF0ZS5ob3B0by5vcmcvaXRlbS82YzA5NzRiNy03YTgxLTRkMmItODcyMS0wODUwMjhkMDA2ZDM

Now its good time to tell about #proxy and #VPN solutions #YunoHost has to offer.
There is #Wiregard.
https://github.com/YunoHost-Apps/wireguard_ynh

#Squid3 proxy(It works, but will have to fix few things to bring good numbers on CI)
https://github.com/YunoHost-Apps/squid3_ynh

There is #ShadowSocks too.
https://github.com/YunoHost-Apps/shadowsocks_ynh

I tried to implemented #V2ray on Shadowsocks. But was taking lot of time, so I kept it in todo list.
https://mast.datamol.org/@anmol/105082418509252162

HansWolters

Sat, 06 Mar 2021 14:03:58 -0800

always check links before you post something, my entry has already expired

HansWolters

Sat, 06 Mar 2021 14:01:22 -0800

An oldie, we already had the discussion.

tofeo

Sat, 02 Oct 2021 03:44:47 -0700

🔁 Repeated @Anmol Sharma's Note

Zap for YunoHost updated

Anmol Sharma

Sun, 07 Feb 2021 08:04:59 -0800

@YunoHost (yunohost@mastodon.social)
#Zap for #YunoHost has been updated to its latest PR that was merged on 21.02.05.

https://github.com/YunoHost-Apps/zap_ynh
IF you want to decide which one to use between #Hubzilla and #Zap see Marks reply here.

anmol

Sun, 07 Feb 2021 08:05:25 -0800

🔁 Repeated @Anmol Sharma's Note

Hubzilla YunoHost package updated to 5.2.1

Anmol Sharma

Fri, 05 Feb 2021 08:17:18 -0800

Hubzilla YunoHost package updated to version 5.2.1.

#yunohost #hubzilla #SelfHosting

Yunohost Hubzilla

Anmol Sharma

Fri, 05 Feb 2021 08:17:59 -0800

@Hubzilla Support Forum (support@zotadel.net)

anmol

Fri, 05 Feb 2021 08:18:25 -0800

🔁 Repeated @Anmol Sharma's Note

Zap for Yunohost

Anmol Sharma

Fri, 13 Nov 2020 11:19:17 -0800

!Hubzilla Support Forum

#Zap for #Yunohost has been updated to latest version 2020-11-11.

https://github.com/YunoHost-Apps/zap_ynh

Zap (Zot6 protocol based) is a #decentralized #social #network supporting #Mastodon , #Pleroma , #Pixelfed , #PeerTube, #Funkwhale , #Friendica , #Hubzilla , and many more.

Zap

show all 5 comments

Anmol Sharma

Sat, 14 Nov 2020 10:23:24 -0800

@LPS
#Friendica has a #PR with latest release but the ldap is broken with latest update. Till its not fixed, it can't be merged.
See this and this.

If you want to try #Friendica without #Ldap support you can try this branch.
https://github.com/SpencerDub/friendica_ynh

Anmol Sharma

Sat, 14 Nov 2020 10:16:19 -0800

@LPS
Goal is to provide the easy installation of #decentralize #platforms, so users who are migrating from other platform can test these platforms and settle for one.

Why not use #git?
Yunohost don't use that philosophy. When many people decide something, you actually can't go against them. Personally I have experimented to provide git benefit for update app. Every time you hit update it would run normal procedure to update an app from git. But this has not worked because of various reasons. Sometime user will run the update too often, other time new version will require a particular version specific things to be done like in Hubzilla version 5.0.0 its required to run php util/z6convert.php after update.
One major benefit is the backup on each update. Every few months a new #update is expected. With each update a backup is made for the app. This has great advantage because if something went bad you can get back to previous backup by restoring it. As users are not bots and by nature they will not backup every time they update an app, which can lead to losing of stuff if some thing bad happen while update. I recently lost my #hub like this and lost my two years posts. The last backup I did was two year ago.
Other advantage is few checks which keep the installation and update process safe. Checks like #php version check, keeping #logs file at proper place, #fail2ban and #ldap support.

Installing Linux inside Linux

Anmol Sharma

Fri, 06 Nov 2020 11:34:48 -0800 last edited: Sun, 07 Mar 2021 18:33:34 -0800

Chroot and installing Debian inside base Linux

Installing a Linux inside a Linux and giving the access through ssh to an user along with providing some services through the main server is a very specific requirement, and an interesting one to have in your admin skills.

I assume you will be installing an app my_webapp__1 through Yunohost that gives a empty container for PHP use. But if you want try this on normal Debian system, then you must have an web server installed like Nginx, Apache etc. A folder and user with user having access to that folder. Lastly a ssh server to connect remotely.
If your installation is ready go to step 2. Assume my_webapp__1 as your folder and user. Change the names according to your configurations.

Install my_webapp on yunohost.
# yunohost app install https://github.com/YunoHost-Apps/my_webapp_ynh/
Remove force sftp for the app from ssh
# nano /etc/ssh/sshd_config
Remove ForceCommand internal-sftp from the my_webapp__1 or the what ever your my_webapp instance number is.
Allow the user to have ssh permission by adding the line AllowUsers my_webapp__1
Restart ssh
# service ssh restart
Install debootstrap. Read more about chroot and debootstrap here
# apt-get install debootstrap
Install the choice of os in chroot directory.
# debootstrap stable /var/www/my_webapp__1 http://deb.debian.org/debian/
You can login to the root of the new installed os by chroot
# chroot /var/www/my_webapp__1
Install the required packages like ssh,sudo
# apt-get install ssh sudo
Exit the chroot
# exit
The uid of users should be same for both users in the real os and the chroot os. So we put the real os uid of the my_webapp__1 user to the chroot my_webapp__1 after creating it.
# cat /etc/passwd
Check the uid of the my_webapp__1 and copy it.
Again login to chroot directory by step 7 and create a user my_webapp__1 in chroot OS.
# adduser my_webapp__1
Give it the same password as real OS user.
Make the uid of the real os same with the chroot os by coping the uid of real os to chroot os.
# nano /etc/passwd
Copy the uid to the my_webapp__2
Now you can ssh to the chroot folder with the my_webapp__1 user.

Try it
$ ssh my_webapp__1@domain.tld
Enter password and you will be in the shell as my_webapp__1 user of chroot os.

Sometimes the my_webapp__1 will require root privileges. For this either you can give my_webapp__2 as root privileges or login as root by su. Other way is giving user privilege to run sudo without password and with root access by editing /etc/sudoers.
Login to the chroot root by step 7 again and add the user to have sudo privieges.
# nano /etc/sudoers
Add this line under Allow members of group sudo to execute any command
my_webapp__1 ALL=(ALL) NOPASSWD: ALL

Now you can ssh to the chroot by ssh my_webapp__1@domain.tld and run any command which require by sudo.

#server #yunohost #ssh #Debian #chroot #debootstrap #linux

Server Yunohost how-to

FourOh-LLC

Mon, 08 Mar 2021 03:33:22 -0800

You need to be born to be able to deal with this much abstraction and complexity, there is no way to master this by training alone. Your brain must be wired in a compatible way. I do not mean like this is something incredibly special - its not. But "learn to code" is also an illusion, a few people are people born with exceptional natural aptitudes and this is one of them.

The rest of us who do not have anything special may only envy or admire these talents, but sadly there is no way to learn them.

At one point in my life I spoke four languages - Hungarian my native, Russian I had to learn in school, German while I was living in Austria waiting for my Visa to the US - and English, since I live in the USA. Today I can speak only one - I lost Russian and English in years, and I am losing my mother-tongue.

Most of us people are not particularly bright, and it takes a lot of effort and repetition to learn and retain what we know - or believe to know.

So, I am reading this, and I know it would take me hours to even attempt to do this. This is why I could never figure out Virtualmin / Cloudmin, and this is why YunoHost is such a wonderful service stack to me.

Papa Dragon

Mon, 08 Mar 2021 14:12:35 -0800

Clever. Could be useful for those who want to have the latest possible versions of Zap, Misty & co running within a regular Yunohost install.

Reminds me of LXC containers without the networking stuff you have to deal with.

Anmol Sharma

Wed, 10 Mar 2021 04:26:47 -0800

At one point in my life I spoke four languages

That is so cool. I have faced same problem. I learn new things and if I don't find someone to talk to, I forget it. I have a problem to forget things very quickly if I loose interest in something. If I come across things which I have learnt and forgotten, I feel like deja vo, and I have to put more effort to learn it again compared to effort I put in first time.

@Papa Dragon (dragondaddy@zap.omtc.fr)
We can install Zap and other zot6 protocols on different domains on Yunohost.
Yunohost has now LXC container package too.

Install Django on Yunohost

Anmol Sharma

Tue, 20 Oct 2020 17:41:30 -0700 last edited: Sun, 07 Mar 2021 18:34:30 -0800

Yunohost is a self hosting solution for users who want to run there own servers without have knowledge of the server administration. To know more about Yunohost see here.

I am using custom web app for the installation of the Django because Yunohost do not have an official package for installing Django.

Install the custom web app:

$ yunohost app install https://github.com/YunoHost-Apps/my_webapp_ynh --debug

In-order to have Django within virtual environment we need to execute virtualenv command. We can install virtualenv through pip. First we install pip and then trough pip install virtualenv.
```
$ sudo apt-get install python-pip  
$ sudo pip install virtualenv
```
We have our virtualenv ready, so we can go to our project directory to execute it.

$ cd /var/www/my_webapp/www/

Remove the index.html in the project directory.

$ rm index.html

Within this project directory, create a Python virtual environment for Python by typing:

$ virtualenv myproject_env

By executing this command a folder named myproject_env will be created in the directory. It will be used to install and configure different python environments.

Now to activate this virtual environment, execute following command:

$ source myproject_env/bin/activate

With your virtual environment activated. We can move forward and install, Gunicorn.

$ pip install django gunicorn

Now with virtual environment been activated. Start Django project using Django management command.

$ django-admin.py startproject myproject .
Note: Don't ignore the trailing dot in the end.

Now we edit the settings.py file located inside myproject folder. We use Nano to do it.
```
$ cd myproject 
$ nano  settings.py
```
Replace the following code inside settings.py.

ALLOWED_HOSTS = ['domain_where_custom_web_app_installed.tld',] STATIC_URL = '/static/' STATIC_ROOT = os.path.join(BASE_DIR, 'static/')

Use ctrl+x to close the Nano. Save the file by typing "y" when asked.

We will need to install the Python and MySQL development headers and libraries:

$ sudo apt-get install python-dev libmysqlclient-dev      
$ pip install mysqlclient

Open again settings.py file located under myproject folder.
Enter your database details which are available in /var/www/my_webapp/db_access.txt

$ cat /var/www/my_webapp/db_access.txt

Copy the database password from here.

Open the settings.py again.

$ sudo nano settings.py

Replace the password which you got from above command at the place of PASSWORD.
DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'my_webapp', 'USER': 'my_webapp', 'PASSWORD': 'password in db_access.txt', 'HOST': 'localhost', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", }, 'PORT': '', } }

Run commands:

$ ./manage.py makemigrations ./manage.py migrate ./manage.py createsuperuser ./manage.py runserver 0.0.0.0:8000

For testing in web browser, enter example.com:8000 and press enter or in command line do:

$ curl example.com:8000

Once you had finished exploring recently created project, hit ctrl+c.

Now let’s test Gunicorn interface.

$ gunicorn --bind 0.0.0.0:8000 myproject.wsgi:application

This will start Gunicorn on same interface on which our earlier development server was working.Test the Gunicorn as described in step 13.

Now type this command to deactivate the virtual environment:

$ deactivate

Now we have to create Gunicorn systemd service file.This service file will be used to start or stop our application server. Open the gunicorn systemd service file using this command.

$ sudo nano /etc/systemd/system/gunicorn.service

Add these lines to the service file.

[Unit]
Description=gunicorn daemon
After=network.target

[Service]
User=root
Group=www-data
WorkingDirectory=/var/www/my_webapp/www
ExecStart=//var/www/my_webapp/www/myproject_env/bin/gunicorn --workers 3 --bind unix:/var/www/my_webapp/www/myproject.sock myproject.wsgi:application

[Install]
WantedBy=multi-user.target

Save and close the file. Start the Gunicorn service using following command.
```
$ sudo systemctl start gunicorn  
$ sudo systemctl enable gunicorn
```
This will create socket file inside your project directory. Always check that the socket file has www-data group and this group should have ownership for the group.

Edit etc/nginx/conf.d/domain_where_custom_web_app_installed.tld.d/my_webapp.conf

location / { 
                  include proxy_params;

                    proxy_pass http://unix:/var/www/my_webapp/www/myproject.sock;

              # Prevent useless logs

                location = /favicon.ico {

                    log_not_found off;

                    access_log off;

                }

                  location /static/ {

                    root /var/www/my_webapp/www;

                }

                location = /robots.txt {

                    allow all;

                    log_not_found off;

                    access_log off;

                }



              #Deny access to hidden files and directories

            # location ~ ^/(.+/|)\.(?!well-known\/) {

              #  deny all;

            }

        # Include SSOWAT user panel.

            include conf.d/yunohost_panel.conf.inc;

        }

Test Nginx configuration for syntax errors by typing:

$ sudo nginx -t

If no error is found, restart Nginx by typing:

$ sudo systemctl restart nginx

That's it!
Now you should have a running instance of the Django on Yunohost.

Note: Components which are installed under virtual environment are isolated from other os global environments. After adding each static file in your app migrate it with:

$ sudo python manage.py collectstatic
$ sudo service gunicorn restart

I have not tested the backup and restore script. So backup manually all your project before trying the web app backup and restore.

#yunohost #Django #Python #Hosting

Yunohost