[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Last revisionBoth sides next revision | |||
howtos:network_services:dropbox [2013/06/12 09:32 (UTC)] – created cmyster | howtos:network_services:dropbox [2013/06/12 19:21 (UTC)] – a few fixes cmyster | ||
---|---|---|---|
Line 10: | Line 10: | ||
===SlackBuild=== | ===SlackBuild=== | ||
This option is easy and more preferred as it creates a package that can be later managed by the Slackware package tools and can be installed system wide. | This option is easy and more preferred as it creates a package that can be later managed by the Slackware package tools and can be installed system wide. | ||
- | The newer versions of the Dropbox client also self upgrades, so there is no need to get the most recent client. | + | The newer versions of the Dropbox client also self upgrades |
The SlackBuild link is at: [[http:// | The SlackBuild link is at: [[http:// | ||
===Manual Installation=== | ===Manual Installation=== | ||
- | To install manually, you can either convert a pre-compiled DEB or RPM or compile from source a client called nautilus-dropbox. This is a wrapper for a few python | + | To install manually, you can either convert a pre-compiled DEB or RPM or compile from source a client called nautilus-dropbox. This is a wrapper for a few scripts and a framework |
The download page is here: [[https:// | The download page is here: [[https:// | ||
Line 21: | Line 21: | ||
===dropbox.py=== | ===dropbox.py=== | ||
Another option to control the Dropbox client via CLI is using the dropbox.py script form this link: [[https:// | Another option to control the Dropbox client via CLI is using the dropbox.py script form this link: [[https:// | ||
- | < | + | < |
To see the script' | To see the script' | ||
- | < | + | < |
Starting the service for the first time is done like so: | Starting the service for the first time is done like so: | ||
- | < | + | < |
This will download a local client for the current user. | This will download a local client for the current user. | ||
====Linking==== | ====Linking==== | ||
- | In order to link a computer to the online service, the client will need to be registered with the user' | + | In order to link a computer to the online service, the client will need to be registered with the online service using the user's account. |
- | When starting the service for the first time, the client will try to start in X, and if it succeeds, the user will be prompt with a GUI dialog that will ask for a username and password. | + | |
When the client links successfully, | When the client links successfully, | ||
- | On X desktop environments, | + | ===GUI=== |
+ | When starting the service for the first time, the client will try to start in X, and if it succeeds, the user will be prompt with a GUI dialog that will ask for a username and password. | ||
+ | |||
+ | On X desktop environments, | ||
If it does not, simply link the dropbox.desktop file from / | If it does not, simply link the dropbox.desktop file from / | ||
+ | ===CLI=== | ||
If the system has no X, it is still possible to link the client. Just run the service and wait for an output: | If the system has no X, it is still possible to link the client. Just run the service and wait for an output: | ||
- | < | + | < |
- | The service will start a login loop and on each link failure (every few seconds) will ask to open a URL. Copy that URL and __while__ the service is still trying to login, | + | The service will start a login loop and on each linking |
- | < | + | < |
After registering on the page, the running service will become linked and will go back to the background. | After registering on the page, the running service will become linked and will go back to the background. | ||
- | |||
- | |||
====== Sources ====== | ====== Sources ====== |