Giter VIP home page Giter VIP logo

odrive's Introduction

Sync your files and folders simply

ODrive

Clone and run for a quick way to see ODrive (OpenSource Drive) in action.

Supported Operating Systems

Snap Status Travis Status Dependencies Status devDependency Status Code Status

To Use

To clone and run this repository you'll need Git and Node.js (which comes with npm) installed on your computer.

The first thing you need is the source code, in your command line:

# Clone this repository
git clone https://github.com/liberodark/ODrive

This will download all the source code in a "ODrive" folder in the current directory. Alternatively, you can download and extract the zip from github's interface.

The steps below (Setup, Build, Run) are to execute in order to ready everything.

Setup

This step is only needed once, in order to install the necessary environment on your computer for ODrive to run.

# Needed for electron 1.7+ to run, as it's based on chrome
sudo apt install libgconf-2-4

Note: If you're using Linux Bash for Windows, see this guide or use node from the command prompt.

Build

This step is to execute every new version of the source code.

In the project directory:

npm install

Note: If you're using Ubuntu and you get an error message about a missing node binary, you may want to try this:

sudo ln -s `which nodejs` /usr/bin/node

If you are working on the code yourself and editing some files in app/assets/, you will need to run npm run webpack (or npm install) for those changes to have an impact on the application.

Run

In the project directory:

npm start

On Windows, you can make a .bat file with start cmd /k npm start that then you can double click to launch the program.

The launch-on-startup functionality is only available on bundled releases. See the Deployment section.

Testing

To make sure the code is ok and run some sanity checks on it:

npm test

Deployment

Releases

There are currently three "release" formats supported: nsis (Windows installer) for Windows, AppImage for Linux, and DMG for Mac. You can generate them like this:

npm run release-windows
npm run release-linux
npm run release-mac

To create a different format, like a deb or rpm package for example:

For DEB

npm run release-linux deb

For RPM

sudo yum install rpm-build -y
npm run release-linux rpm

The releases are generated in the dist folder.

All formats supported by electron-builder are available, such as 7z, zip, tar.gz, deb, rpm, freebsd, pacman, p5p, apk, dmg, pkg, mas, nsis, appx, msi...

Permissionless deployment

An appimage on linux already runs permissionless. Anyway, you can just do:

# Permissonless deployment
npm run release-windows dir # or zip, 7zip, tar.xz, tar.7z, ...

This will create a folder in dist that you can just copy to a Windows machine.

License

GPL v3

odrive's People

Contributors

chris533 avatar code-factor avatar coyotte508 avatar dionaditya avatar djmemo avatar gvelchuru avatar liberodark avatar no92 avatar perigk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

odrive's Issues

File in sub-directory not being updated

I have a file stored in a sub-directory and this file doesn't seem to be updated when it is modified elsewhere.

Steps to reproduce:

I used two machines A and B. A is a macbook using the official google client, and B is a linux machine using odrive.

  1. create a folder test in google drive via drive.google.com, the test folder appears on both A and B
  2. on A, do: echo 1 > test/x
  3. on B, test/x appears and contains 1
  4. on A, do: echo 2 >> test/x
  5. test/x remains unchanged on B
  6. on A, do: cp test/x test/y
  7. on B, test/y appears and contains the two lines 1 and 2, but test/x still contains only 1

Final state on B:

$ ls -la
total 16
drwxrwxr-x  2 xxx xxx 4096 Nov 17 11:37 ./
drwxrwxr-x 10 xxx xxx 4096 Nov 17 11:23 ../
-rw-rw-r--  1 xxx xxx    2 Nov 17 11:25 x
-rw-rw-r--  1 xxx xxx    4 Nov 17 11:34 y
$ cat x
1
$ cat y
1
2

New icon.

Felt like a new, modern flat design icon could suit this better.
So have one ๐Ÿ˜‰ ๐Ÿ˜‹

Error when compiling

When try to run npm start i get this error

> [email protected] start /root/ODrive
> electron main

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `electron main`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-05-27T21_10_33_016Z-debug.log

and log /root/.npm/_logs/2018-05-27T21_10_33_016Z-debug.log have this

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/n$
9 verbose lifecycle [email protected]~start: CWD: /root/ODrive
10 silly lifecycle [email protected]~start: Args: [ '-c', 'electron main' ]
11 silly lifecycle [email protected]~start: Returned: code: 1  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `electron main`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/n$
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/n$
13 verbose stack     at ChildProcess.emit (events.js:182:13)

Can someone help me, thank you

SnapCraft

Hello,

The new goal of odrive is to go on snap !
Why ? because solus manjaro and several to the system considers snap as a native integration to perform.
So this easily allows users to use odrive and especially to install it without effort.

The big difference with AppImage is that it is an application that is verified by canonical and can be installed anywhere thereafter.

cordially

Compilation Error

electron-packager . --overwrite --platform=linux --arch=x64 --prune=true --out=release-builds
Packaging app for platform linux x64 using electron v1.7.6
Command failed: npm prune --production
npm WARN [email protected] requires a peer of node-sass@^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of webpack@^2.0.0 || >= 3.0.0-rc.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.

npm ERR! Cannot read property '0' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pc/.npm/_logs/2017-09-22T07_15_38_433Z-debug.log

npm 5.3.0 / 5.4.0

Synchronize button not working

I open a new issue beacuse a different problem.
After building the project i run npm start, the interface opens, I log in with my google account, select folder to which sync my files to and click synchronize button but nothing happen.

In the terminal:

[email protected] start /home/emil/ODrive
electron main

/home/emil/ODrive/public
app started on port 16409
Updating account info
Updating tray icon, connected: true
Initial scan complete. Ready for changes
Saving account to db
Saved account!
Get home page
Number of accounts 1
GET / 302 55.198 ms - 62
GET /settings 304 44.092 ms - -
GET /javascript/preload.js 404 18.260 ms - 160
GET /javascript/jquery.min.js 404 20.396 ms - 163
GET /javascript/tether.min.js 404 17.734 ms - 163
GET /stylesheets/styles.css 404 17.710 ms - 161
GET /javascript/frontend.js 404 21.730 ms - 161
GET /javascript/settings.js 404 21.363 ms - 161`

If I run npm test I get this:

[email protected] test /home/emil/ODrive
npm run lint

[email protected] lint /home/emil/ODrive
eslint app main.js

/home/emil/ODrive/app/assets/javascript/settings.js
32:25 error 'sender' is defined but never used no-unused-vars
52:19 error 'sender' is defined but never used no-unused-vars
`
โœ–๏ธ 2 problems (2 errors, 0 warnings)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] lint: eslint app main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! Test failed. See above for more details.

Any idea also for this?

Files list done! (first synchronization) ends with ETIMEDOUT

Files list done!
Files list done!
Files list done!
Files list done!
Files list done!
Files list done!
syncing false
Updated syncing status
Updating tray icon, connected: true syncing: false
{ Error: connect ETIMEDOUT 216.58.201.74:443
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14)
code: 'ETIMEDOUT',
errno: 'ETIMEDOUT',
syscall: 'connect',
address: '216.58.201.74',
port: 443 }

My system is ArchLinux, kernel 4.19.8. I tried both the snap package odrive-unofficial and cloning repo and running npm i and then npm start. Both resulted in this error occurring after 5+ minutes of Getting files info.... I ran this app from terminal and this is the tail of the terminal log.

I have good knowledge of node.js and electron, I know how to debug node.js apps in Chrome Dev Tools, so I can provide any information to debug this.

I also tried to open drive.google.com in web browser while Getting files info... to somehow help with keeping the connection alive or something. It didn't help.

My Google Drive storage is around 10GB used.

Systray icon not appearing in Kubuntu

Hello

The systray icon of OpenDrive is not being showed in Kubuntu 18.04. There is a space, that act as the icon when mouse right-button pressed.

Any ideas of what is going on?

Thank you
Best
Mauro Henrique

Packaging error

Currently we can no longer compile the project.

electron-packager . --overwrite --platform=linux --arch=x64 --prune=true --out=release-builds
Packaging app for platform linux x64 using electron v1.7.6
Command failed: npm prune --production
npm WARN [email protected] requires a peer of popper.js@^1.11.0 but none was installed.
npm WARN [email protected] requires a peer of node-sass@^4.0.0 but none was installed.
npm WARN [email protected] requires a peer of webpack@^2.0.0 || >= 3.0.0-rc.0 || ^3.0.0 but none was installed.

npm ERR! May not delete: /tmp/electron-packager/linux-x64/odrive-linux-x64/resources/app/node_modules/.bin

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pc/.npm/_logs/2017-09-09T17_56_56_807Z-debug.log

After Hibernation...

Hello,

ODrive dont reconnect after hibernation just stay in grey color.
And don't sync anything.
Waiting for reproduce this bug on other linux os !

Cordialy

No Sync in tray

I found that once launched, if the window is open you can sync.
But if it is reduced down right it will not sync anymore.

Error after run "sudo npm install -g electron webpack eslint"

Hello, I'm has problem to install, after run the command cited on subject terminal return this following error:

`npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm ERR! Linux 4.8.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! [email protected] install: node scripts/install.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script 'node scripts/install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/kerberosti/ODrive/npm-debug.log`

npm-debug.log

Do you have idea how to solve this? hahaha

First Launch Next Button not work

Unable to click next for the first configuration :

ReferenceError: config is not defined
at router.get (/home/pc/Bureau/ODrive-master/app/routes/settings.js:8:31)
at Layer.handle [as handle_request] (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/layer.js:95:5)
at next (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/layer.js:95:5)
at /home/pc/Bureau/ODrive-master/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/index.js:335:12)
at next (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/index.js:275:10)
at Function.handle (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/index.js:174:3)
at router (/home/pc/Bureau/ODrive-master/node_modules/express/lib/router/index.js:47:12)

Error on Sync Button

TypeError: core.accountById is not a function
at EventEmitter.ipc.on (/home/pc/Bureau/ODrive-master/app/routes/settings.js:42:30)
at emitTwo (events.js:106:13)
at EventEmitter.emit (events.js:194:7)
at WebContents. (/home/pc/Bureau/ODrive-master/node_modules/electron/dist/resources/electron.asar/browser/api/web-contents.js:247:13)
at emitTwo (events.js:106:13)
at WebContents.emit (events.js:194:7)

ODrive Validity Check Error in Manjaro from AUR..!!

Sorry my bad english, I'm from Brazil..!!

I'm trying to install odrive in Manjaro from AUR.

I getting the following error:

Validating source files with sha256sums...
odrive-0-3.py ... FAIL
odriveagent.sh ... Passed
odrive.service ... Passed
[email protected] ... Passed
ERROR: One or more files did not pass the validity check!

Any ideia..??

Thank you so much..!!

Local to Remote sync not working under a FUSE mount

Hi, I have a FUSE mount inside which I would like to use this awesome app, but the local-to-remote sync doesn't work. In depth details:

  • OS: Ubuntu 18.10
  • /etc/fuse.conf: option user_allow_other enabled
  • Volume created and mounted with gocryptfs installed through PPA version 1.4.3-5build1
  • Volume mounted with allow_other flag (full mount output: /XXX on /YYY type fuse.gocryptfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions,allow_other,max_read=131072))
  • NodeJS v10.13.0
  • NPM 6.4.1
  • ODrive 65ba3e3 23 Aug 2018
  • Output of main npm start command is same of equal instance outside FUSE mount, until new file created locally: under FUSE mount the output remains empty

Remote-to-Local works flawlessly.
Outside the gocryptfs FUSE mount, both synchronizations work flawlessly.

Browsing this project source code, I think it is very likely an issue of chokidar or Node fs API, but since I've encountered this issue here, this is the starting point for debugging it.

Could you help me investigate the issue further?

Please provide an AppImage for download

Providing an AppImage would have, among others, these advantages:

  • Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
  • One app = one file = super simple for users: just download one AppImage file, make it executable, and run
  • No unpacking or installation necessary
  • No root needed
  • No system libraries changed
  • Works out of the box, no installation of runtimes needed
  • Optional desktop integration with appimaged
  • Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
  • Can optionally GPG2-sign your AppImages (inside the file)
  • Works on Live ISOs
  • Can use the same AppImages when dual-booting multiple distributions
  • Can be listed in the AppImageHub central directory of available AppImages
  • Can double as a self-extracting compressed archive with the --appimage-extract parameter

Here is an overview of projects that are already distributing upstream-provided, official AppImages.

If you have questions, AppImage developers are on #AppImage on irc.freenode.net.

Stuck on 'Files list done!'

Hi,

I've been looking for a Google Drive GUI client for Linux and stumbled upon this. I'm running the AppImage so that I can get everything synchronized, but it seems to get hung up on 'Files list done!'. I don't think it's able to download any of my files for some odd reason. I did allow it to manage my Drive, the only thing I've done is change it from ~/Google Drive to ~/Drive

OS: Fedora 28
Kernel: 4.18.14-200

If you need any further information, let me know and I'd be happy to help :)

How to contribute?

Hi @liberodark,

I'd like to contribute to the project. I personally don't find good alternatives of Google Drive for linux, so I want to build one too using electron + nautilus integration + app indicator. Could you add me in? Or how can I contribute otherwise?

Thanks.

Detect changes to local files at launch

Keep the file tree in the database to detect at launch if files were added locally since last run.

Pay caution to missing or empty root folder (do not destroy remote drive folder because of that...).

Dependencies Updates !

Have new updates of dependencies !

Most Important :

electron ^1.6.6 โ†’ ^1.7.8
googleapis ^19.0.0 โ†’ ^22.2.0
eslint ^3.19.0 โ†’ ^4.8.0
file-loader ^0.11.1 โ†’ ^1.1.4
md5-file ^3.1.1 โ†’ ^3.2.3

Others :

fs-extra ^3.0.1 โ†’ ^4.0.2
extract-text-webpack-plugin ^2.1.0 โ†’ ^3.0.1
style-loader ^0.17.0 โ†’ ^0.19.0
url-loader ^0.5.8 โ†’ ^0.6.2
webpack ^2.5.1 โ†’ ^3.6.0
body-parser ^1.17.1 โ†’ ^1.18.2
chokidar ^1.6.1 โ†’ ^1.7.0
command-line-args ^4.0.4 โ†’ ^4.0.7
ejs ^2.5.6 โ†’ ^2.5.7
express ^4.15.2 โ†’ ^4.16.1
morgan ^1.8.1 โ†’ ^1.9.0
sass-loader ^6.0.3 โ†’ ^6.0.6
copy-webpack-plugin ^4.0.1 โ†’ ^4.1.0
css-loader ^0.28.1 โ†’ ^0.28.7
node-sass ^4.5.2 โ†’ ^4.5.3
resolve-url-loader ^2.0.2 โ†’ ^2.1.0

Database system

Currently the database system (nebd) writes a duplicate of the sync object each save. Although autocompaction is enabled every 30 seconds, a better way to update storage would be good (for example separate file entries), or use local storage, anyway something that doesn't increase the storage too much.

Multiple accounts

I really think that be able to use multiple google accounts in that app will be a great addition!

Frontend Roadmap

  • Minimize to tray icon
  • Notifications when files are remotely changed
  • Change tray icon when connection is lost
  • Change folder functionality
  • Possibility to close account

Start App not work correctly

Unable to launch the application at this time.

$ webpack
Hash: c2fea09400ce0e29955e
Version: webpack 2.7.0
Time: 4944ms
Asset Size Chunks Chunk Names
javascript/frontend.js 116 kB 0 [emitted] frontend
javascript/frontend.js.map 136 kB 0 [emitted] frontend
javascript/jquery.min.js 86.7 kB [emitted]
javascript/tether.min.js 25 kB [emitted]
javascript/preload.js 274 bytes [emitted]
javascript/settings.js 1.09 kB [emitted]
[0] /home/asuse/Bureau/ODrive-master//bootstrap/dist/js/bootstrap.js 111 kB {0} [built]
[1] ./stylesheets/main.scss 1.4 kB {0} [built] [failed] [1 error]
[2] ./javascript/index.js 55 bytes {0} [built]
[4] /home/asuse/Bureau/ODrive-master/
/css-loader!/home/asuse/Bureau/ODrive-master//resolve-url-loader!/home/asuse/Bureau/ODrive-master//sass-loader/lib/loader.js?sourceMap!./stylesheets/main.scss 412 bytes [built] [failed] [1 error]
[5] /home/asuse/Bureau/ODrive-master//style-loader/addStyles.js 9.15 kB [built]
[6] /home/asuse/Bureau/ODrive-master/
/style-loader/fixUrls.js 3.01 kB [built]
+ 1 hidden modules

ERROR in /home/asuse/Bureau/ODrive-master//css-loader!/home/asuse/Bureau/ODrive-master//resolve-url-loader!/home/asuse/Bureau/ODrive-master/~/sass-loader/lib/loader.js?sourceMap!./stylesheets/main.scss
Module build failed:
@extend .form-control-static;
^
".settings #synchronize-status" failed to @extend ".form-control-static".
The selector ".form-control-static" was not found.
Use "@extend .form-control-static !optional" if the extend should be able to fail.
in /home/asuse/Bureau/ODrive-master/app/assets/stylesheets/main.scss (line 35, column 13)
@ ./stylesheets/main.scss 4:14-188
@ ./javascript/index.js

ERROR in ./stylesheets/main.scss
Module build failed: ModuleBuildError: Module build failed:
@extend .form-control-static;
^
".settings #synchronize-status" failed to @extend ".form-control-static".
The selector ".form-control-static" was not found.
Use "@extend .form-control-static !optional" if the extend should be able to fail.
in /home/asuse/Bureau/ODrive-master/app/assets/stylesheets/main.scss (line 35, column 13)
at runLoaders (/home/asuse/Bureau/ODrive-master/node_modules/webpack/lib/NormalModule.js:192:19)
at /home/asuse/Bureau/ODrive-master/node_modules/webpack/node_modules/loader-runner/lib/LoaderRunner.js:364:11
at /home/asuse/Bureau/ODrive-master/node_modules/webpack/node_modules/loader-runner/lib/LoaderRunner.js:230:18
at context.callback (/home/asuse/Bureau/ODrive-master/node_modules/webpack/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at Object.asyncSassJobQueue.push [as callback] (/home/asuse/Bureau/ODrive-master/node_modules/sass-loader/lib/loader.js:55:13)
at Object. (/home/asuse/Bureau/ODrive-master/node_modules/sass-loader/node_modules/async/dist/async.js:2244:31)
at Object.callback (/home/asuse/Bureau/ODrive-master/node_modules/sass-loader/node_modules/async/dist/async.js:906:16)
at options.error (/home/asuse/Bureau/ODrive-master/node_modules/node-sass/lib/index.js:294:32)
Child extract-text-webpack-plugin:
[0] /home/asuse/Bureau/ODrive-master//css-loader!/home/asuse/Bureau/ODrive-master//resolve-url-loader!/home/asuse/Bureau/ODrive-master/~/sass-loader/lib/loader.js?sourceMap!./stylesheets/main.scss 412 bytes {0} [built] [failed] [1 error]

ERROR in /home/asuse/Bureau/ODrive-master/~/css-loader!/home/asuse/Bureau/ODrive-master/~/resolve-url-loader!/home/asuse/Bureau/ODrive-master/~/sass-loader/lib/loader.js?sourceMap!./stylesheets/main.scss
Module build failed: 
    @extend .form-control-static;
           ^
      ".settings #synchronize-status" failed to @extend ".form-control-static".
The selector ".form-control-static" was not found.
Use "@extend .form-control-static !optional" if the extend should be able to fail.
      in /home/asuse/Bureau/ODrive-master/app/assets/stylesheets/main.scss (line 35, column 13)

Mac build Error

npm run release-mac

[email protected] release-mac /home/pc/Documents/Github/ODrive
electron-builder --mac

โ€ข electron-builder version=19.55.2
โ€ข loaded configuration file=package.json ("build" field)
โ€ข writing effective config file=dist/electron-builder.yaml
โ€ข rebuilding native production dependencies platform=darwin arch=x64
โ€ข packaging platform=darwin arch=x64 electron=1.8.4 appOutDir=dist/mac
Downloading tmp-27142-0-electron-v1.8.4-darwin-x64.zip
[============================================>] 100.0% of 48.34 MB (1.37 MB/s)
โ€ข skipped macOS application code signing reason=supported only on macOS
โ€ข building target=DMG arch=x64 file=dist/Open Drive-0.1.3.dmg
Error: spawn hdiutil ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)
at onErrorNT (internal/child_process.js:379:16)
at process._tickCallback (internal/process/next_tick.js:114:19)
From previous event:
at spawn (/home/pc/Documents/Github/ODrive/node_modules/builder-util/src/util.ts:200:3)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/targets/dmg.ts:229:9
at Generator.next ()
From previous event:
at createStageDmg (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/out/targets/dmg.js:25:21)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/targets/dmg.ts:33:27
at Generator.next ()
From previous event:
at DmgTarget.build (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/out/targets/dmg.js:253:11)
at taskManager.addTask.default.map.it (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/platformPackager.ts:120:67)
From previous event:
at MacPackager.packageInDistributableFormat (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/platformPackager.ts:120:23)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/macPackager.ts:92:26
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
From previous event:
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/macPackager.ts:92:10
at Generator.next ()
From previous event:
at MacPackager.pack (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/out/macPackager.js:200:11)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/packager.ts:364:24
at Generator.next ()
at xfs.stat (/home/pc/Documents/Github/ODrive/node_modules/fs-extra-p/node_modules/fs-extra/lib/mkdirs/mkdirs.js:56:16)
at /home/pc/Documents/Github/ODrive/node_modules/graceful-fs/polyfills.js:287:18
at FSReqWrap.oncomplete (fs.js:171:5)
From previous event:
at Packager.doBuild (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/out/packager.js:432:11)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/packager.ts:308:52
at Generator.next ()
at /home/pc/Documents/Github/ODrive/node_modules/graceful-fs/graceful-fs.js:99:16
at /home/pc/Documents/Github/ODrive/node_modules/graceful-fs/graceful-fs.js:43:10
at FSReqWrap.oncomplete (fs.js:153:20)
From previous event:
at Packager._build (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/out/packager.js:376:11)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/src/packager.ts:270:23
at Generator.next ()
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
From previous event:
at Packager.build (/home/pc/Documents/Github/ODrive/node_modules/electron-builder-lib/out/packager.js:332:11)
at /home/pc/Documents/Github/ODrive/node_modules/electron-builder/src/builder.ts:310:40
at Generator.next ()
From previous event:
at _build (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/out/builder.js:61:21)
at build (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/src/builder.ts:280:10)
at then (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/src/cli/cli.ts:48:33)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
From previous event:
at Object.args [as handler] (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/src/cli/cli.ts:48:33)
at Object.runCommand (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/node_modules/yargs/lib/command.js:235:44)
at Object.parseArgs [as _parseArgs] (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/node_modules/yargs/yargs.js:1041:24)
at Object.get [as argv] (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/node_modules/yargs/yargs.js:957:21)
at Object. (/home/pc/Documents/Github/ODrive/node_modules/electron-builder/src/cli/cli.ts:42:15)
at Module._compile (module.js:649:30)
at Object.Module._extensions..js (module.js:660:10)
at Module.load (module.js:561:32)
at tryModuleLoad (module.js:501:12)
at Function.Module._load (module.js:493:3)
at Function.Module.runMain (module.js:690:10)
at startup (bootstrap_node.js:194:16)
at bootstrap_node.js:666:3

Xubuntu 18.04 .deb not work

I always installed in error, but it stays in synchronization and no file appears, I noticed that there is not occurring network traffic ..

Syncing indicator

Would it be possible to show when ODrive is syncing? (linux)

Maybe a similar icon like Mega does.

mega

Notification icon

The Odrive icon is missing in the notification bubble in elementary OS/Ubuntu.

Currently it looks like this:

screenshot from 2018-10-09 17 49 10

Ideally it should look something like this.

screenshot from 2018-10-09 17 50 31

Ignored files

I had 2 files that were ignored and had to manually double checked on the browser to see which files were missing.

I know I've been making lots of requests (sooo annoying!), but I was wondering if there is a way of providing a list of the files that are being sync and ignored.

screenshot from 2018-04-05 17 49 20

Control notifications

Currently there's no official way of controling Odrive's notification popups.

A quick solution is to add X-GNOME-UsesNotifications=true to the .desktop file for linux. Therefore it can then be configured from the Notification Settings.

When is applied, it looks like this in Ubuntu and elementary OS.
screenshot from 2018-10-09 18-02-37

screenshot from 2018-10-09 17 58 33

Notification Systeme

Hello,

Notification don't notify when you add file or folder on google drive folder.

Cordialy

Start on startup

Under settings there should be an option that allows to "Start on startup" (linux)

Remove your API secret from public source

Actually its not a bug though,
Please consider not sharing api secret, as it can be stolen by anyone and they create a app pretend to be yours?
you can release app binary keeping your api secret private to yourself.

Update files based on timestamp

My files get synchronized but apparently they are not checked for edits / new timestamps. Installed via the Ubuntu Software Center / Snap package

Upload/Download progress bar

First of all, good job developing ODrive!

I don't know how easy this is to implement. But is there a way to add a progress bar or list of the files that are being uploaded/downloaded?

On MEGAsync it looks like this.

screenshot from 2018-04-26 16 50 58

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.