Cloud Sync No longer works, owner changed - Revision history

Bacchas at 15:08, 25 April 2024

2024-04-25T15:08:23Z

Bacchas at 15:06, 25 April 2024

2024-04-25T15:06:13Z

← Older revision		Revision as of 15:06, 25 April 2024
Line 6:		Line 6:
	<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>		<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>
	<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>		<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>
	<li>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>		<li>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code class="yellowbackground">id -g new_user_name</code>. lets assume these return 1033 and 100</li>
	<li>now we can run an sqlite shalle for the config database by doing <code>sqlite3 config.sqlite</code></li>		<li>now we can run an sqlite shalle for the config database by doing <code class="yellowbackground">sqlite3 config.sqlite</code></li>
	<li>To see all the existing connections you can do a `select * from connection_table;`</li>		<li>To see all the existing connections you can do a <code class="yellowbackground">select * from connection_table;</code></li>
	<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>		<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>
	<li>The actual update is then done similar to this command using the right user id and local user name</li>		<li>The actual update is then done similar to this command using the right user id and local user name</li>
	<li> ` update connection_table set uid=~~1033~~, gid=100, local_user_name="~~new_user_name~~" where id=3;` the last id will indicate in which row you want to update this</li>		<li> <code class="yellowbackground"> update connection_table set uid=1030, gid=100, local_user_name="new_username" where id=1;</code> the last id will indicate in which row you want to update this</li>
	<li>.quit to exit</li>		<li>.quit to exit</li>
	<li>start your cloudsynch package again</li>		<li>start your cloudsynch package again</li>
	</ul>		</ul>

Bacchas at 15:03, 25 April 2024

2024-04-25T15:03:29Z

← Older revision		Revision as of 15:03, 25 April 2024
Line 1:		Line 1:
	~~<style>~~
	~~code{~~
	~~font-weight: bold;~~
	~~background-color: yellow;~~
	}
	~~</style>~~

	===The settings are stored in an SQLite database and can be modified there. I took the following steps.===		===The settings are stored in an SQLite database and can be modified there. I took the following steps.===

Line 13:		Line 6:
	<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>		<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>
	<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>		<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>
	<li>You can do this by running <code>id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>		<li>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>
	<li>now we can run an sqlite shalle for the config database by doing <code>sqlite3 config.sqlite</code></li>		<li>now we can run an sqlite shalle for the config database by doing <code>sqlite3 config.sqlite</code></li>
	<li>To see all the existing connections you can do a `select * from connection_table;`</li>		<li>To see all the existing connections you can do a `select * from connection_table;`</li>

Bacchas at 15:01, 25 April 2024

2024-04-25T15:01:38Z

← Older revision		Revision as of 15:01, 25 April 2024
Line 1:		Line 1:
	The settings are stored in an SQLite database and can be modified there. I took the following steps.		<style>
			code{
			font-weight: bold;
			background-color: yellow;
			}
			</style>

			===The settings are stored in an SQLite database and can be modified there. I took the following steps.===

	<ul>		<ul>
Line 7:		Line 14:
	<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>		<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>
	<li>You can do this by running <code>id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>		<li>You can do this by running <code>id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>
	<li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li>		<li>now we can run an sqlite shalle for the config database by doing <code>sqlite3 config.sqlite</code></li>
	<li>To see all the existing connections you can do a `select * from connection_table;`</li>		<li>To see all the existing connections you can do a `select * from connection_table;`</li>
	<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>		<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>

Bacchas at 14:59, 25 April 2024

2024-04-25T14:59:43Z

← Older revision		Revision as of 14:59, 25 April 2024
Line 6:		Line 6:
	<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>		<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>
	<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>		<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>
	<li>You can do this by running <code>`id -u new_user_name` and `id -g new_user_name`</code>. lets assume these return 1033 and 100</li>		<li>You can do this by running <code>id -u new_user_name</code> and <code>id -g new_user_name</code>. lets assume these return 1033 and 100</li>
	<li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li>		<li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li>
	<li>To see all the existing connections you can do a `select * from connection_table;`</li>		<li>To see all the existing connections you can do a `select * from connection_table;`</li>

Bacchas at 14:58, 25 April 2024

2024-04-25T14:58:42Z

← Older revision		Revision as of 14:58, 25 April 2024
Line 6:		Line 6:
	<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>		<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>
	<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>		<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>
	<li>You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100</li>		<li>You can do this by running <code>`id -u new_user_name` and `id -g new_user_name`</code>. lets assume these return 1033 and 100</li>
	<li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li>		<li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li>
	<li>To see all the existing connections you can do a `select * from connection_table;`</li>		<li>To see all the existing connections you can do a `select * from connection_table;`</li>

Bacchas at 14:57, 25 April 2024

2024-04-25T14:57:36Z

← Older revision		Revision as of 14:57, 25 April 2024
Line 1:		Line 1:
	The settings are stored in an SQLite database and can be modified there. I took the following steps.		The settings are stored in an SQLite database and can be modified there. I took the following steps.

	<p>Stop the cloud sync service from the package manager</p>		<ul>
	Connect through ssh to your diskstation or open a terminal console window		<li>Stop the cloud sync service from the package manager</li>
	go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`		<li>Connect through ssh to your diskstation or open a terminal console window</li>
	before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100		<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>
	now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`		<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>
	To see all the existing connections you can do a `select * from connection_table;`		<li>You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100</li>
	Note down the ids of the configurations that need a change. This is the first number in each row.		<li>now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`</li>
	The actual update is then done similar to this command using the right user id and local user name ` update connection_table set uid=1033, gid=100, local_user_name="new_user_name" where id=3;` the last id will indicate in which row you want to update this		<li>To see all the existing connections you can do a `select * from connection_table;`</li>
	~~press Ctrl+C multiple times~~ to exit ~~the sqlite shell~~		<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>
	start your cloudsynch package again		<li>The actual update is then done similar to this command using the right user id and local user name</li>
			<li> ` update connection_table set uid=1033, gid=100, local_user_name="new_user_name" where id=3;` the last id will indicate in which row you want to update this</li>
			<li>.quit to exit</li>
			<li>start your cloudsynch package again</li>
			</ul>

Bacchas at 14:54, 25 April 2024

2024-04-25T14:54:38Z

← Older revision		Revision as of 14:54, 25 April 2024
Line 1:		Line 1:
	The settings are stored in an SQLite database and can be modified there. I took the following steps.		The settings are stored in an SQLite database and can be modified there. I took the following steps.

	1*Stop the cloud sync service from the package manager		<p>Stop the cloud sync service from the package manager</p>
	Connect through ssh to your diskstation or open a terminal console window		Connect through ssh to your diskstation or open a terminal console window
	go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`		go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`

Bacchas: Created page with "The settings are stored in an SQLite database and can be modified there. I took the following steps. 1*Stop the cloud sync service from the package manager Connect through ssh to your diskstation or open a terminal console window go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db` before we open the sqlite database to modify it we need to look up what the user id and group id of our new u..."

2024-04-25T14:53:54Z

Created page with "The settings are stored in an SQLite database and can be modified there. I took the following steps. 1*Stop the cloud sync service from the package manager Connect through ssh to your diskstation or open a terminal console window go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db` before we open the sqlite database to modify it we need to look up what the user id and group id of our new u..."

New page

The settings are stored in an SQLite database and can be modified there. I took the following steps.

1*Stop the cloud sync service from the package manager
Connect through ssh to your diskstation or open a terminal console window
go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`
before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. You can do this by running `id -u new_user_name` and `id -g new_user_name`. lets assume these return 1033 and 100
now we can run an sqlite shalle for the config database by doing `sqlite3 config.sqlite`
To see all the existing connections you can do a `select * from connection_table;`
Note down the ids of the configurations that need a change. This is the first number in each row.
The actual update is then done similar to this command using the right user id and local user name ` update connection_table set uid=1033, gid=100, local_user_name="new_user_name" where id=3;` the last id will indicate in which row you want to update this
press Ctrl+C multiple times to exit the sqlite shell
start your cloudsynch package again

← Older revision		Revision as of 15:08, 25 April 2024
Line 1:		Line 1:
	===The settings are stored in an SQLite database and can be modified there. I took the following steps.===		===The settings are stored in an SQLite database and can be modified there. I took the following steps.===

	~~<ul>~~
	<li>Stop the cloud sync service from the package manager</li>		<p>Stop the cloud sync service from the package manager</p>
	<li>Connect through ssh to your diskstation or open a terminal console window</li>		<p>Connect through ssh to your diskstation or open a terminal console window</p>
	<li>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</li>		<p>go to the volume where the configure for cloudSync sits. and there into the config folder. for me that was `cd /volume1/@cloudsync/db`</p>
	<li>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </li>		<p>before we open the sqlite database to modify it we need to look up what the user id and group id of our new user will be. </p>
	<li>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code class="yellowbackground">id -g new_user_name</code>. lets assume these return 1033 and 100</li>		<p>You can do this by running <code class="yellowbackground">id -u new_user_name</code> and <code class="yellowbackground">id -g new_user_name</code>. lets assume these return 1033 and 100</p>
	<li>now we can run an sqlite shalle for the config database by doing <code class="yellowbackground">sqlite3 config.sqlite</code></li>		<p>now we can run an sqlite shalle for the config database by doing <code class="yellowbackground">sqlite3 config.sqlite</code></p>
	<li>To see all the existing connections you can do a <code class="yellowbackground">select * from connection_table;</code></li>		<p>To see all the existing connections you can do a <code class="yellowbackground">select * from connection_table;</code></p>
	<li>Note down the ids of the configurations that need a change. This is the first number in each row.</li>		<p>Note down the ids of the configurations that need a change. This is the first number in each row.</p>
	<li>The actual update is then done similar to this command using the right user id and local user name</li>		<p>The actual update is then done similar to this command using the right user id and local user name</p>
	<li> <code class="yellowbackground"> update connection_table set uid=1030, gid=100, local_user_name="new_username" where id=1;</code> the last id will indicate in which row you want to update this</li>		<p> <code class="yellowbackground"> update connection_table set uid=1030, gid=100, local_user_name="new_username" where id=1;</code> the last id will indicate in which row you want to update this</p>
	<li>.quit to exit</li>		<p>.quit to exit</p>
	<li>start your cloudsynch package again</~~li>~~		<p>start your cloudsynch package again</p>
	~~</ul~~>