Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi

JaredBusch

I tweaked the SSL config section as well and tested again.

Emad R

@JaredBusch

Hehe no surprise there.

Emad R

Hi,

I can confirm it is working, and it is alive ...

Thanks for the fix, and sorry for the delay.

however If i can nitpick, I am unable to enable memory cache and file locking.

0_1489785287758_2017-03-17 23_09_34-2008_R2_SP1_113 on localhost.localdomain.png

Look at the screenshots and I dont know really where to put those lines:

'memcache.locking' => '\OC\Memcache\Redis',
'memcache.local' => '\OC\Memcache\Redis',
'redis' => array(
'host' => 'localhost',
'port' => 6379,
),

I tried putting them in 3 places, yet everytime it failed after saving and restarting the server, the webserver no longer boots up.

I know those are more of an optional stuff, but if you have quick fix or suggestion, I will be much in your debt.

JaredBusch

@msff-amman-Itofficer it goes anywhere.

[root@nctest ~]# cat /var/www/html/nextcloud/config/config.php 
<?php
$CONFIG = array (
  'instanceid' => 'occ4c7flycgy',
  'passwordsalt' => 'IUShFaONjlpGP+xy6WHG3SkZmXw1u/',
  'secret' => 'SLC9EUO468SLissy5w4NnqYbKHWZyZ7Tj4zAjco/WCp2IoBr',
  'trusted_domains' => 
  array (
    0 => 'nctest.bundystl.com',
  ),
  'datadirectory' => '/var/www/html/nextcloud/data',
  'overwrite.cli.url' => 'http://nctest.bundystl.com',
  'htaccess.RewriteBase' => '/',
  'dbtype' => 'mysql',
  'version' => '11.0.2.7',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'ncuser',
  'dbpassword' => 'ncuserpassword',
  'logtimezone' => 'UTC',
  'installed' => true,
  'memcache.locking' => '\OC\Memcache\Redis',
  'memcache.local' => '\OC\Memcache\Redis',
    'redis' => array(
    'host' => 'localhost',
    'port' => 6379,
  ),
);

Emad R

@JaredBusch

I simply didn't copy the
),
with the rest of the commands.
cause I already saw it in the file, but after a second look of your config, I realized it was in the file as
);

Emad R

@msff-amman-Itofficer

Sorry, all working 100%

Thank you very much

I should sleep now, its way too late thus making those small mistakes

theozsnowman

Im wondering if anyone can help i have followed this great guide but now find that i cannot login to the admin of my nextcloud and im getting repeated errors of Uncaught ReferenceError: OCA is not defined

I am running Nexcloud 12.0.3

can anyone advise please?

JaredBusch

I have no idea. It would need more detail, or time to attempt to replicate.

scottalanmiller

@theozsnowman said in Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi:

Im wondering if anyone can help i have followed this great guide but now find that i cannot login to the admin of my nextcloud and im getting repeated errors of Uncaught ReferenceError: OCA is not defined

I am running Nexcloud 12.0.3

can anyone advise please?

I have not seen that error yet. This is on a fresh install?

zachary715

I just completed this guide on Vultr using Nextcloud 12.0.4 and CentOS 7. No issues here. Thanks as these guides are getting me more familiar with Linux vs the appliance install.

zachary715

I installed this VM in the NJ datacenter because I had a free 50GB promotional block storage available from a while back waiting to give this a go. I attached the block storage to the VM prior to install, however at the installation screens where you select disks, I wasn't sure how to go about it so I only selected the 25GB disk that came with the $5 instance.

Now that I have everything setup, running df-h is only showing the 25GB storage so I apparently should have chosen both disks. Is there a way to attach the block storage to this nextcloud instance now that it's up and running without having to redo the whole thing? Ideally, I would like to have the 25GB + 50GB block storage for a total of 75GB if possible.

scottalanmiller

You can, using LVM to span them. Not an ideal way to use your storage, but it will work. Same as doing it on Windows, really.

zachary715

@scottalanmiller When you say "not an ideal way to use your storage", are you referring to adding the block storage on top of the storage already provided in the instance, or trying to manually expand things after the fact?

I guess my question then is if I wanted this to be done right, am I better off just destroying this instance and going through it again, adding the block storage initially from the CentOS install menu? Or is adding the block storage to make the usable space larger not an ideal setup for nextcloud period?

scottalanmiller

@zachary715 said in Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi:

@scottalanmiller When you say "not an ideal way to use your storage", are you referring to adding the block storage on top of the storage already provided in the instance, or trying to manually expand things after the fact?

I mean creating a span.

scottalanmiller

@zachary715 said in Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi:

@scottalanmiller When you say "not an ideal way to use your storage", are you referring to adding the block storage on top of the storage already provided in the instance, or trying to manually expand things after the fact?

I guess my question then is if I wanted this to be done right, am I better off just destroying this instance and going through it again, adding the block storage initially from the CentOS install menu? Or is adding the block storage to make the usable space larger not an ideal setup for nextcloud period?

Having two types of storage merged in a span. Either fails, both fail. It's like RAID 0 without the performance benefits. Not ideal in any sense.

zachary715

I'm mainly doing this for personal learning and testing so I'll operate it as a span for the time being. If I decide if I want to get more serious with it, I'll look to grab some SATA storage instances if they come available or run it elsewhere. Thanks

scottalanmiller

@zachary715 said in Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi:

I'm mainly doing this for personal learning and testing so I'll operate it as a span for the time being. If I decide if I want to get more serious with it, I'll look to grab some SATA storage instances if they come available or run it elsewhere. Thanks

Spanning is fine for your own learning. SATA instances pop up all the time, but only last a day or so as everyone has alerts on them.

JaredBusch

@zachary715 said in Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi:

I just completed this guide on Vultr using Nextcloud 12.0.4 and CentOS 7. No issues here. Thanks as these guides are getting me more familiar with Linux vs the appliance install.

That is why I write my guides the way I do.

It would be simple to post a big string or shell script to execute that would perform all the steps like magic. But that does not help the person following the guide to know WTF they just did.

zachary715

In a scenario where you might want the additional storage capacity in SSD therefore want to add a lot of block storage to an instance, would it make sense to install Nextcloud to the 25GB drive and then relocate the /var/www/html/nextcloud/data directory to the larger block storage space?

Would there be benefits to this setup from a migration standpoint in the future or in case of boot drive failure?
Not fully understanding yet what all of these steps are accomplishing during installation and setup, would creating this setup from the get-go be as easy as pointing some of these commands to the directory of the block storage, or more complicated than that? (Not asking you to necessarily show these steps, just inform me)
Could I migrate to this setup while running? It may be easier to do during installation, but again just trying to learn.

scottalanmiller

@zachary715 said in Install NextCloud 11.0.2 on CentOS 7 with PHP 7.1 from Remi:

In a scenario where you might want the additional storage capacity in SSD therefore want to add a lot of block storage to an instance, would it make sense to install Nextcloud to the 25GB drive and then relocate the /var/www/html/nextcloud/data directory to the larger block storage space?

Would there be benefits to this setup from a migration standpoint in the future or in case of boot drive failure?

Not fully understanding yet what all of these steps are accomplishing during installation and setup, would creating this setup from the get-go be as easy as pointing some of these commands to the directory of the block storage, or more complicated than that? (Not asking you to necessarily show these steps, just inform me)

Could I migrate to this setup while running? It may be easier to do during installation, but again just trying to learn.

For production, typically yes. You would normally either use the local space for a tiny instance, use a storage instance for something in the middle, or go to the additional block storage for something really large or performant. In that case, you'd normally not put any data on the local disks, only the OS and apps, as the additional space that you'd get from that would be totally trivial anyway once you were at any size.