Hello.
I noticed that the media folder is growing a lot lately.
when checking I found several files like this:
“ticker_25ed31a9274c22ab6b62792fcd3d4306”
They have no extension, some have more than 7MB.
01 - What exactly are these files?
02 - Will they increase infinitely?
03 - Is it possible to delete or do something that reduces these files?
They’re images embedded in tickers that you’re using in the CMS.
They will be deleted when they’re no longer required. There were some bugs around this though in older versions, so if you’re not already on 1.8.9 then I’d suggest you upgrade to avoid those.
You also need to ensure XTR is running properly otherwise nothing will clean those up and they will continue to grow indefinitely. If you’re using Docker, XTR is setup and configured for you already. If you did a custom install, you need to arrange that it’s run regularly yourself.
With manual instillation on a web server it needs to be configured as per the manual page Alex has linked.
Which pretty much means you need to have a task like cron / windows scheduled task that will run the xtr.php.
XTR will then run all CMS tasks ie maintenance tasks, fetch remote DataSet, emails notification etc.
On Docker installations that’s all configured and running without the need for any manual configuration changes.
I can’t tell you exactly what to put there because I don’t know how your server is setup.
Broadly, you need to run as frequently as possible
/path/to/php /path/to/xibo/bin/xtr.php
as shown in the article I linked you to, where /path/to/php is the path to your PHP command line executable, and /path/to/xibo is the fully qualified path to your Xibo CMS install.
Xibo is really not suitable for shared hosting. If you have web in the URL you’re using to access the CMS then you’re going to keep hitting issues with the install. To avoid that, you need to make changes to the webserver configuration that you can’t normally make on shared hosting environments.
Unfortunately for now I can only use xibo this way, but I’ll start to study a way to deploy to a dedicated server soon.
01 - So if I look for the support of the hosting and ask to guide me on how to program the execution of this file “/ path / to / php /path/to/xibo/bin/xtr.php” Unnecessary Ticker RSS files will be deleted right?
02 - How often do you suggest scheduling the execution?
03 - In the server’s instructions, there is an address for each version of PHP.
I’m using “5.6” Should I use this? or should I use a specific version for the XTR.PHP file?
The system can’t release files that are in use somewhere.
This directly correlates to your questions about database. All your usage sounds fairly minimal to me from your description. If you’re trying to run Xibo on shared hosting, then you’re fighting a battle you won’t win. It doesn’t work well there, and most shared hosting providers will start to complain about the load it puts on the server fairly quickly. Switch to something supportable please!
Our recommendation is an Ubuntu 16.04 LTS 64 bit VPS with DigitalOcean or Vultr, and then running the CMS inside Docker. We have a complete end to end guide on installation.
Old items which are no longer going to be shown are removed automatically assuming you are running XTR.
In terms of quantity, only what is needed is downloaded, so you directly determine that. If you have an RSS feed with 100 items in it and you only want to show 1, then limit the Ticker widget to 1 item!
Compression is an interesting idea and we will consider it, however, it doesn’t fit all use cases, and in many cases the images in ticker feeds are very small to start with so it wouldn’t be sensible to further compress those.
Here you can see the Format tab:
Note: Each widget layout has a duration of 10 seconds and displays only one news item at a time.
In Quantity I set “1”, and I selected Randomise.
Thus, each time the layout is displayed, a new random news is displayed.
If I disable Randomise, the last news will always be displayed, and no other and I do not want this, I need to display new news with each loop, but I would limit the amount of different news, for example: only the last 10, but this option does not exist.
03 - By End, About Compaction.
In the code I created, it checks the image size, and only reduces those that are larger than 800px wide.
and compression is done on all, but can also be modified to see if it needs to be compacted.
Anyway, I’m happy to be helping.
But I want to reaffirm the need to define a way to limit the amount of news to be downloaded.
In my tests this is not happening.
I’m in version 1.8.9.
If you’re telling it to show 1 random item, then by definition it has to download all the items in that feed.
If the feed keeps old items in it for a long time then you will have very old items associated with those widgets in the library, because you’ve selected to be able to show any random one of those items.
The system is doing exactly what you’ve configured it to do.