Changes

From Amahi Wiki
Jump to: navigation, search
422 bytes added ,  16:06, 7 December 2014
no edit summary
Work in Progress tag: {{WorkInProgress}}
 
Information provided here may sometimes lean towards a user with "Intermediate" and some "Advanced" computer skills. But don't let that scare you off!
__TOC__
===Removing an ownCloud Application===
 
Even though an ownCloud application is "Disabled" (administration user only) the program code remains in a directory. Sometimes it may be necessary to completely remove the application's program code from the ownCloud instance. Additionally there are some database entries that have to be removed also. In this example the "Who Share" application code will be removed.
 
* Ensure that the application is disabled in Settings => Apps.
* Open a "terminal" window on the host server and "su" to the "root" ID (administrator).
* "cd" in to the "/var/hda/web-apps/owncloud/html/apps" directory. This is where the ownCloud applications are stored.
* Using the "ls" command a directory "files_whoshare" will be displayed. This is the directory that will be removed.
* Using the "rm -fr files_whoshare" command the "Who Share" application code is removed.
* Using the "ls" command again should show that the "files_whoshare" is gone.
* Close the terminal window.
* All entries in the ownCloud MySQL database have to be removed this can done by using Amahi "phpMyAdmin".
* In the database table "oc_appconfig", find all entries having the name of the "files_whoshare" application as "appid".
* Remove those entries.
* Now the "files_whoshare" application is completely removed from ownCloud.
 
===Mounting ownCloud as a File Share===
'''Example Scenario:'''
In this example IP addresses will be used to demonstrate the trusted domain domains feature. The server in this example has an
address of "192.168.0.101" on a wired network connection. It has been decided to add a Wifi connection to the server,
which forms a "subnet" with address of "192.168.99.1". The Wifi subnet is a new domain, and is considered as an untrusted
domain by ownCloud.
'''Configure Trusted DomainDomains:'''
* Locate the "config.php" file in the owncloud "config" directory.
* Edit Using an editor open the fileas the "root" user, initially it will have the following entry:
<blockquote>
<pre>
</pre>
</blockquote>
 
* Put a second entry in to the "trusted_domains array" for the Wifi address as follows:
<blockquote>
<pre>
'trusted_domains' =>
array (
0 => '192.168.0.101',
1 => '192.168.99.1',
),
</pre>
</blockquote>
 
''' OR'''
 
* Comment out the "trusted_domains array" as follows:
<blockquote>
<pre>
/* 'trusted_domains' =>
array (
0 => '192.168.0.101',
1 => '192.168.99.1',
), */
</pre>
</blockquote>
'' Is this a security issue? That depends on the system owner or administrator...''
 
* Save the changes and exit the editor.
 
* Any subsequent web browser access via the Wifi address to ownCloud will not be blocked.
 
===ownCloud Logfile Size===
This tid bit was picked up from an ownCloud Blog item. The "owncloud.log" file, lives in the ownCloud "data directory", can reach a rather large file size. In the case of the blog a file size of 5.9 gigabytes big. Yeah, 6318901632 bytes.
 
* ownCloud can keep that file in check, but you have to enable that by adding the following to "config.php":
'log_rotate_size' => '100 MiB',
 
* Using a text editor the config.php file will look like this afer the change:
 
$CONFIG = array (
'instanceid' => '515c94d976c01',
'passwordsalt' => '6144794036e3aabc7d239238266b8e',
'datadirectory' => '/var/hda/files/owncloud7/data',
'dbtype' => 'mysql',
'version' => '7.0.3.4',
'dbname' => 'owncloud7',
'dbhost' => 'localhost',
'dbtableprefix' => 'oc_',
'dbuser' => 'owncloud7',
'dbpassword' => 'owncloud7',
'installed' => true,
'theme' => '',
'maintenance' => false,
'log_rotate_size' => '100 MiB',
);
 
* Reboot the server.
 
* On a regular basis before backups are done make sure to delete any old log files no longer required.
 
<br />