Skip to content

nextcloud

How to Install OnlyOffice Document Server For Nextcloud, Fast & Easy

I’ve wasted a ridiculous amount of time trying to get the Collabora / LibreOffice / CODE platform integrated with my Nextcloud 11 server.  I wanted to have Google Docs-style editing, but it was turning out to be a massive headache.  One day, on accident, I stumbled on an OnlyOffice plugin for OwnCloud.  After a little digging, I found out it worked with NextCloud as well.  Less than 15 minutes later, I had the OnlyOffice Document Server packages installed on a second Ubuntu 16.04 server and it was fully integrated with my NextCloud server.

 

What You Need

 

For this guide, you will ultimately need the following:

  • A 2nd Ubuntu 16.04 or 16.10 Server
  • A Valid SSL Certificate (A FREE LetsEncrypt Certificate Will Do)
  • A Valid DNS Entry for Both Servers (for this guide, you are required to use onlyoffice.yourdomain.tld, custom OnlyOffice domains are out of the scope of this guide)

 

Installing Dependencies

 

OnlyOffice requires a few dependencies.  Mainly, nodejs, postgresql, and nginx.  In addition, we’ll need to enable a repo for up-to-date ttf-mscorefonts-installer packages.

 

First, let’s go ahead and add the needed repo’s.

 

echo "deb http://archive.ubuntu.com/ubuntu precise main universe multiverse" | sudo tee -a /etc/apt/sources.list
curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -

 

Next, install postgresql.

Click Here to Keep Reading!

Goodbye ownCloud, Hello Nextcloud! The Aftermath of Disrupting Open Source Cloud Storage

If you are vaguely familiar with ownCloud, you may have noticed quite a bit of ruckus on the tech blogs back in July when their US business entity was essentially gutted.  The Chief Executive Office and cofounder, Frank Karlitschek, announced he was resigning.  Within a few weeks, most of the core development team followed suit.  This left many long time ownCloud users, such as myself, completely puzzled.  Here we are a few months later and a few questions still linger, but many have been answered.  First, let’s briefly review what the ownCloud platform provides and why this matters.

 

What is ownCloud?

 

ownCloud is an Open Source cloud platform that closely mimics the functionality of Dropbox, Box, Google Drive, and all the other big guys.  There is an ownCloud server, that runs on a simple LAMP stack (Linux, Apache, MySQL, PHP), and then there’s a client(s).  The client is an application that can be installed on Linux, Windows, OSX, iOS, Android and pretty much everything else.  Each user has a folder full of files that magically stays synchronized on the server and each device the client has the software installed on.  Then users can share files and folders with other users, collaborate, and the list goes on.  Functionality has expanded quite a bit over the years, in way of apps.  Apps have integrated mail, calendar, contacts, music, photo galleries and so much more into the ownCloud ecosystem.  The main difference between ownCloud, and the big guys mentioned earlier, is it’s completely free.  Well, it started out free.  Needless to say, with thousands of developers contributing code, and tens of thousands of installations later, it grew.  So, when did things go sour?

 

What happened?

 

A couple years ago, things started to change.  Instead of the community being the driving force behind development decisions and what direction the project was heading (the core principle of Open Source software) venture capital had another idea.  Less attention was being given to community submitted bugs and feature requests, and a divide was being formed between the community and ownCloud’s business entities, ownCloud GmbH (Germany) and ownCloud Inc (USA).  The business makes money by charging for support, but that started to expand into other areas.  The list of complaints from the Open Source community is pretty long, so I’ll give you the headlines.

 

  • ownCloud developers were ignoring feedback and hoarding functionality for their paying “enterprise” customers.
  • User interfaces were mutilated for many of the core services, such as the contacts and calendar apps.
  • Any attempt to give construction criticism was taken as a personal attack and/or just ignored.
  • Major defects in the code were being released, such as broken updater utilities.
  • ownCloud GmbH/Inc was not sharing future road maps and maintained a veil of secrecy.
  • Lack of real innovation and development of the platform as a whole.

Click Here to Keep Reading!