Install ownCloud stable (currently 9.0.2) on CentOS 7
-
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
So Vultr has SELinux disabled by default. I attempted to check how to enable it here. It has you edit /etc/sysconfig/selinux but when I go to it it's empty. I entered all of the information, essentially creating a new document but SELinux is still disabled. I'm guessing this probably isn't accurate?
Why are you trying to enable it? While it is certainly best to have it enabled, by being disabled, there would be no impact on your install.
You said in your guide that you disagree with SELinux being put into permissive mode or disabled. I want everything to be JB best practice
-
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
So Vultr has SELinux disabled by default. I attempted to check how to enable it here. It has you edit /etc/sysconfig/selinux but when I go to it it's empty. I entered all of the information, essentially creating a new document but SELinux is still disabled. I'm guessing this probably isn't accurate?
Why are you trying to enable it? While it is certainly best to have it enabled, by being disabled, there would be no impact on your install.
You said in your guide that you disagree with SELinux being put into permissive mode or disabled. I want everything to be JB best practice
Then you should not start from a system that has it permanently gone.
-
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
So Vultr has SELinux disabled by default. I attempted to check how to enable it here. It has you edit /etc/sysconfig/selinux but when I go to it it's empty. I entered all of the information, essentially creating a new document but SELinux is still disabled. I'm guessing this probably isn't accurate?
Why are you trying to enable it? While it is certainly best to have it enabled, by being disabled, there would be no impact on your install.
You said in your guide that you disagree with SELinux being put into permissive mode or disabled. I want everything to be JB best practice
Then you should not start from a system that has it permanently gone.
I wasn't sure if that was the case or not. There is no way for me to enable it? I thought it might just come disabled by default but not permanently.
-
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
So Vultr has SELinux disabled by default. I attempted to check how to enable it here. It has you edit /etc/sysconfig/selinux but when I go to it it's empty. I entered all of the information, essentially creating a new document but SELinux is still disabled. I'm guessing this probably isn't accurate?
Why are you trying to enable it? While it is certainly best to have it enabled, by being disabled, there would be no impact on your install.
You said in your guide that you disagree with SELinux being put into permissive mode or disabled. I want everything to be JB best practice
Then you should not start from a system that has it permanently gone.
I wasn't sure if that was the case or not. There is no way for me to enable it? I thought it might just come disabled by default but not permanently.
I have never tried. I do not have any production systems on Vultr. I have only used it for testing FreePBX to date.
-
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
So Vultr has SELinux disabled by default. I attempted to check how to enable it here. It has you edit /etc/sysconfig/selinux but when I go to it it's empty. I entered all of the information, essentially creating a new document but SELinux is still disabled. I'm guessing this probably isn't accurate?
Why are you trying to enable it? While it is certainly best to have it enabled, by being disabled, there would be no impact on your install.
You said in your guide that you disagree with SELinux being put into permissive mode or disabled. I want everything to be JB best practice
Then you should not start from a system that has it permanently gone.
I wasn't sure if that was the case or not. There is no way for me to enable it? I thought it might just come disabled by default but not permanently.
You could get around it by not using their default CentOS image and load your own from an uploaded ISO.
-
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@JaredBusch said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
@wirestyle22 said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
So Vultr has SELinux disabled by default. I attempted to check how to enable it here. It has you edit /etc/sysconfig/selinux but when I go to it it's empty. I entered all of the information, essentially creating a new document but SELinux is still disabled. I'm guessing this probably isn't accurate?
Why are you trying to enable it? While it is certainly best to have it enabled, by being disabled, there would be no impact on your install.
You said in your guide that you disagree with SELinux being put into permissive mode or disabled. I want everything to be JB best practice
Then you should not start from a system that has it permanently gone.
I wasn't sure if that was the case or not. There is no way for me to enable it? I thought it might just come disabled by default but not permanently.
You could get around it by not using their default CentOS image and load your own from an uploaded ISO.
That makes sense. Thanks!
-
Followed the instructions to the letter except for Remi PHP 5.6 (will do next week), and worked flawlessly. Thanks. Quick question. Under Admin File Handling, the default is 513MB. Changing is greyed out with message of "Missing permissions to edit from here." Did quick google and see a few that have that issue and a couple of workarounds that, TBH, confuse. Care to note how to change that?
-
@DenisKelley said in Install ownCloud stable (currently 9.0.2) on CentOS 7:
Followed the instructions to the letter except for Remi PHP 5.6 (will do next week), and worked flawlessly. Thanks. Quick question. Under Admin File Handling, the default is 513MB. Changing is greyed out with message of "Missing permissions to edit from here." Did quick google and see a few that have that issue and a couple of workarounds that, TBH, confuse. Care to note how to change that?
I have not looked at changing that setting as I generally use the sync client for almost all users. The one time I did tinker with it, I ran into issues with my Nginx proxy in front of ownCloud.
That time, I followed the 8.0 instructions located here.
Those instructions do note that the box in the admin is not available depending on security settings for file permissions, but does not clearly state which.
-
@DenisKelley Looking around, I found this github wiki article was updated in January.
https://github.com/owncloud/documentation/wiki/Uploading-files-up-to-16GB -
This post is deleted!
