Scheduled Job at reboot

Why don't you write out all you did so far to get it working. Maybe we make a plugin.

Ben, just want to let you know I took a loot at this. I would not need the nginx plugin to have it hosted by nginx. Also, I saw that it seems to run fasster with PostgreSQL. I think we need a news reader. There are some things I want to finish before I come back to this though. Give it some time.

You are running a job at reboot and don't want to use root???? correct??? Did you make ben the owner of the job??? You are trying to use the ben owner?

Well the update daemon at this location is owned by www-data:
/media/uuid/www-data/tt-rss/update_daemon2.php

Try to use the "www-data" user for your update job. See if that works.

Let me know if that user works...

Does it work with rooot??? It may be because it needs to be on a disk that is not mounted noexec. And/or perms on the php command. Give me results of the stat command:

cd /media/uuid/www-data/tt-rss (put in whatever your uid is)
stat update_daemon2.php

I checked and other people are using www-data as the user to update the news feeds.

so use this user:
www-data

enter the command like this though:
/usr/bin/php /media/uuid/www-data/tt-rss/update.php --feeds --quiet

I am thinking you need the path to php, which is a runaround symlink to php5

Install Tiny Tiny RSS with PostgreSQL plugin:

1) Install openmediavault-postgresql plugin

2) enable the plugin and put check sql management site. Then click on Save.

3) Now put in new password and click on reset password

3.1) You can now login to the MyWebSQL site using:
id: postgres
pass: the password you just set
Server: localhost PostgreSQL
Then click on login. This is just infromational. I am going to setup the database for Tiny Tiny RSS in command line.

4) In command line do the following from root ssh session:
su - postgres
psql
CREATE USER "www-data" WITH PASSWORD 'yourpasshere'; (use password you want for the database)
CREATE DATABASE ttrss WITH OWNER "www-data";
\quit
exit

5) Go to data drive you want the Tiny Tiny RSS reader on. So UUID will be the UUID number of the drive you want:

cd /media/UUID/
wget -O ttrss.tar.gz https://github.com/gothfox/Tiny-Tiny-RSS/archive/1.15.3.tar.gz
tar -xvzf ttrss.tar.gz
rm ttrss.tar.gz
mv Tiny-Tiny-RSS* ttrss
chown -R www-data:www-data ttrss

Started working on it....

Notes:
Use method to grab latest version.

Add: php5-curl php-apc php5-gd (after check config good)

Enough for tonight...

@ben-nl I setup an hourly job in this format with the www-data user and it is working fine.

/usr/bin/php /media/uuid/ttrss/update.php --feeds --quiet

If anyone is interested here is my preliminary nginx conf and fpm file.

The UUID in this file would be changed to your own.
/etc/nginx/openmediavault-webgui.d/openmediavault-ttrss.conf

location /ttrss/ {
    alias /media/118a45c0-2f2b-4e1c-91c7-eaca09d75737/ttrss/;
    index index.php;
    access_log /var/log/ttrss_access.log;
    error_log /var/log/ttrss_error.log info;
    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php5-fpm-openmediavault-ttrss.sock;
        fastcgi_index index.php;
        include fastcgi_params;
    }
    location /ttrss/ {
        try_files $uri $uri/ /ttrss/index.php;
    }
    location ~* /ttrss/\.(js|css|png|jpg|jpeg|gif|ico)$ {
        expires max;
        log_not_found off;
    }
}

/etc/php5/fpm/pool.d/openmediavault-ttrss.conf

[openmediavault-ttrss]
listen = /var/run/php5-fpm-openmediavault-ttrss.sock
listen.owner = www-data
listen.group = www-data
listen.mode = 0600


user = www-data
group = www-data


pm = dynamic
pm.max_children = 5
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3


php_value[post_max_size] = 25M
php_value[upload_max_filesize] = 25M

There will be some adjustments. But you get the idea. I've never used the nginx plugin.

Ben, there are a lot of different ways this can be setup. I think the PostgreSQL was a good move. It is running really fast and nice with it. But then there is this update feed thing. They suggest to run it as a daemon instead of a cron job. Running it as daemon would work better with the design of OMV too, the way the apply config works. We set lots of things up as a subdirectory to however your domain/subdomain may be set up. This is why when I login I have:
http:/omvaddress/ttrss/
or
https:/omvaddress/ttrss/
Using this method you can get SSL via OMV instead of setting it up separately. I don't open port 80 to the net. If you open port 443 to the net and have it forwarded by your router to your OMV you can reach TTRSS by:
https://wanip(or domain, or ddns address)/ttrss/

Anyway, I need to use this for a week, or so, before I decide on how to treat SSL and some other things. I have decided daemon is better for the updates. A lot of the guides I see are not that great and none of them take into consideration how OMV works. I am leaning towards not having SSL on all the time and someone wants to use it through the internet they use OMV's SSL. But I have not tried the mobile apps. They could change my mind. If someone has opinions say something.

With a plugin you will never use the nginx plugin to create the website files for the site that needs to be hosted. There will be a nginx and fpm config file installed by the plugin. The nginx plugin is just to make it easy for you guys to host a website.