Posts made by Donahue

@DustinB3403 said in Random Thread - Anything Goes:

https://i.imgur.com/subbON6l.png

How come I can't upvote this more than once?

@travisdh1 said in What Are You Doing Right Now:

Cursing a former MSP. This AD we inherited has no security groups, just user permissions set for everything. It hurts us.

I've regretted every single time I have done that for a user because I was being too lazy to create a group for one person. I've learned my lesson.

Veeam leverages too many windows technologies currently. Hence, I run it on Server 2012r2

@scottalanmiller said in Random Thread - Anything Goes:

https://thechive.files.wordpress.com/2019/01/daily-afternoon-randomness-49-photos-25-41.jpg?quality=85&strip=info&w=600

The predecessor to too many tabs open

@JaredBusch will you be willing to write up a guide for getting open office working with NC, specifically behind nginx? I can try and fumble through it, but you make things look so easy.

@scottalanmiller said in How to Migrate NextCloud Data Location:

So if you are like me, your NC data is stored in /data. This is the directory that will explode in size as you store things there.

So what we need to do is make a new place for the data to go, first of all. We will assume that your new block storage is already created and mounted as /extblock. If you are unsure how to mount the new storage in the first place, that's a good topic for a fresh post as it is not directly related to NextCloud and more just Linux general block mounting.

So now /data has the current data and /extblock has the big empty space.

1. Shut down NextCloud

2. cp -rp /data/ /extblock/

3. mv /data /data-old
   This step preserves the old data just in case something has gone wrong.

4. ln -s /extblock /data
   And in theory that is it. You've copied everything from the old space to the new one, then made a link to make the new one look like the old one so that NC doesn't need to know that any of this happened. Of course, you can cd /data once all this is done and verify that it looks correct.

5. Start NextCloud

@scottalanmiller, I found this post while researching. It was very helpful, but you missed a . in step 2. It should be

2. cp -rp /data/. /extblock/

otherwise you get /extblock/data/***

@JaredBusch said in Install Nginx as a Reverse Proxy on Fedora 27:

client_max_body_size 40M;

One thing I just ran into was having to up this limit to be able to sync larger files. I would suggest flagging that in the first post so someone like me would know to change this if they work with larger files. I set mine to 16G. For some reason, this only effected the NC sync client, the browser upload as increased by other means.

So to update this, searches do not seem to work in shared folders, but they will work in group folders which is an optional app. I also had to setup the backup job in NC to be a cron job and not an ajax job, and add it to the crontab for the apache user.

crontab -u apache -e

I couldn't get the fulltextsearch:live to work properly, so I added fulltextsearch:index to the cron job too.

*/15  *  *  *  * php -f /var/www/html/nextcloud/cron.php
*/15  *  *  *  * php -f /var/www/html/nextcloud/occ fulltextsearch:index

It seems the search only works on files that are not shared.

I was able to get it installed using that link and also here: https://www.linode.com/docs/databases/elasticsearch/a-guide-to-elasticsearch-plugins/

After that, I can run the index and it picks up new documents. But it will not search them.

I find it odd that the elasticsearch app is installed in NC, but the package is not on my machine.

@JaredBusch said in Nextcloud and Full Text Search:

sudo dnf provides elasticsearch

[root@Nextcloud ~]# sudo dnf install elasticsearch
Last metadata expiration check: 1:58:59 ago on Tue 08 Jan 2019 09:51:44 AM PST.
Error:
 Problem: conflicting requests
  - nothing provides mvn(org.apache.lucene:lucene-analyzers-common:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-core:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-highlighter:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-join:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-memory:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-queries:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-queryparser:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-sandbox:4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-spatial:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch
  - nothing provides mvn(org.apache.lucene:lucene-suggest:4.10.4) needed by elasticsearch-1.7.1-3.fc24.noarch

@Pete-S said in Local Encryption Scenarios:

@DustinB3403 said in Local Encryption Scenarios:

@Pete-S said in Local Encryption Scenarios:

@DustinB3403 said in Local Encryption Scenarios:

@Pete-S said in Local Encryption Scenarios:

Anyway, in the case of the CPA we are talking about material that is not really sensitive at all.

The data files could be secured the same way as any paper records. Locked in a safe when not in use.

That would be the same as being encrypted, since the lock on a safe = encryption and the physical key = the passphrase to decrypt the drive or data.

Well, in principle only. You can walk away with the encrypted computer but it would be harder with the safe.

In most cases physical security is about delaying. You can smash and grab a laptop from the office window but it would require a lot more time to break in properly and then open a safe before someone shows up.

You have those examples a bit mixed up.

The comparable scenario would be "getting to the data" The physical medium housing that data doesn't matter.

You break the lock, you get the data. If you break the encryption key you get the data.

But a physical lock is likely easier to break and get into whatever than it would to decrypt a encrypted volume.

Reminds me of this classic:

there is ALWAYS a relevant xkcd

I have installed NC as per @JaredBusch's great guide. Now however, I want to enable both full text search and OCR for the files in NC, but I am running into issues, probably because I don't know a whole lot about linux in general and fedora in specific. A lot of the guides that I am finding online seem to be for debian or ubuntu.

So far, I have installed the 4 apps currently in the NC appstore for full text search.

But when I attempt to run the first index, following this guide I get this error:

[root@Nextcloud ~]# sudo -u apache php /var/www/html/nextcloud/occ fulltextsearch:index

In Index.php line 379:

  failed platform test.


fulltextsearch:index [--output [OUTPUT]] [-r|--no-readline] [--] [<options>]

If I run a test, it shows that the platform is down:

[root@Nextcloud ~]# sudo -u apache php /var/www/html/nextcloud/occ fulltextsearch:test

.Testing your current setup:
Creating mocked content provider. ok
Testing mocked provider: get indexable documents. (2 items) ok
Loading search platform. (Elasticsearch) ok
Testing search platform. fail
In Test.php line 300:

  Search platform (Elasticsearch) down ?


fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY]

If I try and enable the elasticsearch service, I get this:

[root@Nextcloud ~]# sudo systemctl enable elasticsearch
Failed to enable unit: Unit file elasticsearch.service does not exist.

All this leads me to believe that the app method of installation does not work right, maybe just on fedora? Other methods of installation have different syntax, and I am struggling to figure out how to translate it to fedora.

Looking at the official install guide here, It looks like I need to add the elastic.co repository, but it is https, and so I need to enable that. If I try and just run sudo dnf install elasticsearch it complains about nothing providing it's requirements, so that leads me to believe it needs that other repository.

the guide shows this for debian:

wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -
sudo apt-get install apt-transport-https
echo "deb https://artifacts.elastic.co/packages/6.x/apt stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-6.x.list
sudo apt-get update && sudo apt-get install elasticsearch

what should this be for fedora?

I just need to figure out how to configure it properly I think

I've already done that, but it does nothing

I want both

@dafyre that's what I am talking about

@scottalanmiller said in What Are You Doing Right Now:

@Donahue said in What Are You Doing Right Now:

I am looking into setting up OCR search with NC. Anyone do that in NC 15?

I don't use OCR anywhere.

what do you use?

I am looking into setting up OCR search with NC. Anyone do that in NC 15?