Xibo where is settings.php

File: oauth. File: statusdashboard. File: forecastio. File: maintenance. Please refresh. File: datemanager. Otherwise assume input is already Gregorian. File: schedule. If set the event will be show in preference to other events. File: File: content. File: index. You may now login with these details. File: kit. File: twitter. File: services. Error Code: '. File: File. File: display. File: media. I use Xibo digital signage 1. The security alert from CentOS7 is very helpfull.

It asks what you wanna do, in this case I wanted to have write and read access. And it gives you the 'ausearch' solution. From Xibo v1. Installing it on Windows of any flavour is an absolute pain in the backside. Have a look here for the requirements on a manual install and consider either deploying it via a webserver on CentOS 7 or via docker on Ubuntu. Thank you for your reply.

I also tried this on centos7, but my file permissions for write access on settings. I set everything open as I also tried other commands such as But nothing is working for me. You should be fine if you follow the instructions. It's not overly complicated. Although, ever since they did this, trying to get a manual install working is nothing but trouble. It's the main reason my organisation stopped using it as they didnt want to have to support some random docker orphaned system when there are alternatives that are easier to maintain.

A shame because Xibo is a good product otherwise. Also if you're doing this you generally want on folders and on files. But for the sake of testing will work. If you still had permissions issues perhaps your syntax was not applying them correctly? I'd navigate to the folder that contains your Xibo parent folder then type chmod -R Xibo or whatever the folder is called.

I didnt say the product was nothjing but trouble, Xibo works really well at what it does. Star New issue. Jump to bottom. Linked pull requests. Copy link. Is this a fresh install? Thanks FETommy. My problem is solved it IIS 7. Sign up for free to join this conversation on GitHub. Already have an account?

Sign in to comment. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.