syncloud / platform Goto Github PK

Fails from TC: http://build.syncloud.org:8111/viewLog.html?buildId=8&buildTypeId=Image_Package&tab=buildLog#_state=30&focus=141

But works in the shell:
cd /syncloud/image
sudo ./build.sh

We need sam which supports copy deployment. It should be standalone and easy to install.

From @vsapronov on January 6, 2015 5:40

In Ubuntu it could be found in /lib/jvm/ - not in /opt. update-alternatives commands should be fixed.

Copied from original issue: syncloud-old/image-base#1

From @vsapronov on March 31, 2015 15:50

null

Copied from original issue: syncloud/image-ci#7

From @vsapronov on November 10, 2014 16:13

This is client side of this: https://github.com/syncloud/apps/issues/13

Copied from original issue: syncloud/android#13

From @cyberb on September 23, 2014 8:38

Copied from original issue: syncloud/apps#10

From @cyberb on March 27, 2015 21:30

For example:
http://docs.buildbot.net/current/tutorial/firstrun.html

Copied from original issue: syncloud/image-ci#6

From @cyberb on November 29, 2014 15:28

Clients use avahi events to request identification using ssh. Ssh server may start after avahi, clients will get no identification.
Maybe we can somehow innform users that device is booting up.
Or we can force avahi start after ssh.

Copied from original issue: syncloud-old/image-tools#1

From @vsapronov on December 29, 2014 22:24

Any board with Wi-Fi could be a Wi-Fi access point. It's very useful when travelling to some random places. You can just plug Syncloud into Ethernet and have Wi-Fi and your local server all-in-one!

Copied from original issue: syncloud/apps#18

Exposing device on Internet should be optional. Small server at home with zero-scripting for setup is good enough to be offered as a product. It also will help users with crappy routers.

From @vsapronov on October 19, 2014 3:59

We need good mail list with proper subscription requirements and would be cool to have some web UI too.

So far we consider MailMan List and discourse.

Copied from original issue: syncloud/syncloud.github.com#4

when it comes out we should use their command line installation feature

From @vsapronov on March 17, 2015 11:49

There should be a way to delete domain from web UI.

Copied from original issue: syncloud/redirect#19

Currently you have to use a partition manager to format your disk (erase all data) to create at least one partition with ext4 filesystem.
Having just filesystem without partition table will not work.
It is a Linux file system, so you need to use Linux based tools. GParted Live USB is a good option for that.
https://github.com/syncloud/platform/wiki/External-Disk
Always check what you are erasing/formatting to not erase your primary disk!

From @cyberb on February 14, 2015 0:36

After receiving several disk issues emails I think we need some form of health check on a device. I would start with adding simple notification message on device main web ui.
For example "Disk error, more info" plus advice "restart device, format disk, send reports to support ..."

Copied from original issue: syncloud-old/server#1

From @cyberb on December 5, 2014 22:21

ownCloud's trusted domains is not regenerated as we do not reactivate ownCloud on second time device activation.

One crazy thing is instead of adding domain name we can add php code to get domain name from insider for example as ownCloud config is php file.

Ex: /var/www/owncloud/config/config.php

<?php
$CONFIG = array (
  'trusted_domains' => array(passthru("insider ...")),
);

Copied from original issue: syncloud/android#17

We need to move router check from phone to web UI. This will allow us to do real check and will give us this feature for all platforms.

From @vsapronov on February 24, 2015 12:42

They take long time. Anything to reduce them would help a lot.

Copied from original issue: syncloud/image#46

Device Info:
root@Cubian:# syncloud-id name
{
"message": null,
"data": "cubieboard",
"success": true
}
root@Cubian:# syncloud-id id
{
"message": null,
"data": {
"title": "Cubieboard",
"name": "cubieboard",
},
"success": true
}

Fix:
add
127.0.0.1 localhost
to /etc/hosts

From @vsapronov on March 31, 2015 15:55

Check each step in instruction
Add Router Check step to the beginning
All screenshots should be updated - we changed design a lot

Copied from original issue: syncloud/syncloud.github.com#8

From @cyberb on February 22, 2015 0:24

null

Copied from original issue: syncloud-old/server#2

From @vsapronov on July 14, 2014 18:34

It should be possible to internationalize this instruction.

Copied from original issue: syncloud/syncloud.github.com#2

Sometimes ISPs block popular ports like 80, 443...
Probably insider should check if mapped port is actually accessible.

NAT-PMP is an alternative to UPnP used by Apple in AirPort routers.
It seems that NAT-PMP libs and tools are already in Debian: https://packages.debian.org/sid/net/natpmp-utils
Insider could try to detect NAT-PMP in case of failure with UPnP and map ports either way. There's separate question what to do with router check - we will need to find reliable NAT-PMP library in Java...

From @vsapronov on March 13, 2015 14:28

1. Run syncloud on Ubuntu Core.
2. Build Ubuntu Core root partition image on emulator.
3. Join ODROID-XU3 boot partition and root partition into one working image.
4. Try to apply approach to other boards.

Copied from original issue: syncloud/image#49

From @cyberb on November 20, 2014 9:19

1. Show mounted disk info
2. Migrate internal data to external disk
3. Format/clean

Copied from original issue: syncloud/apps#14

From @cyberb on March 2, 2015 6:43

Copied from original issue: syncloud-old/image-boot#1

From @vsapronov on March 15, 2015 22:5

We need to keep ownCloud binaries in our S3 storage to control what we are installing into image.

Copied from original issue: syncloud/owncloud#1

Include check of port 80 availability into router check.
If not available then suggest user to free it.

Develop simple iOS app which should be able to discover and activate devices

From @vsapronov on March 15, 2015 22:58

Copied from original issue: syncloud/image#50

From @cyberb on August 26, 2014 22:16

The main advantage is secure phisical location of a device.
Ultimate device location security requires all its services to be accessd through tor.

One of the java libs:
https://github.com/hoijui/JTor

Copied from original issue: syncloud/android#4

We should probably make domain lowercase at the early stage of device activation.

We can use pagekite instead of drilling ports through insider.

From @vsapronov on March 18, 2015 13:38

Imagine you had the device off for a while. Then you plug it and it will be shown online on the web only in 5 mins after booting. If internal IP changed then public domain address update takes up to 10 mins.
To fix this we probably need to sync insider to redirect at the end of boot.

Copied from original issue: syncloud/image#51

From @cyberb on November 28, 2014 20:28

We need to improve connection performance as I was told it is slow by random user.
I personally think it is.

Maybe http rpc would be faster, need to try.

Copied from original issue: syncloud/apps#16

From @cyberb on October 12, 2014 19:8

Copied from original issue: syncloud/apps#11

From @cyberb on August 25, 2014 23:46

Copied from original issue: syncloud/android#3

From @vsapronov on March 17, 2015 11:49

We already display external IP-address. It would be good to show:
Internal IP-address
Name of board

Copied from original issue: syncloud/redirect#18

Users reported having public IPv6 from their ISP (WAN) and still having IPv4 on LAN

From @vsapronov on November 10, 2014 16:11

This is a way to fix problem of not reliable mDNS libraries for Android. We do not have to use mDNS because we control both server and client.
The idea is just to emit multicast packets (from emiiter - Syncloud device) and detect them client (detector - Android device).
The test for this is located here (emitter is in python, detector is in Java-Android): https://github.com/syncloud/multicast-test

Here's some proposal for how emitter should look like.
The emitter should be configurable. The message it emits should be stored in configuration. There should be possibility to set some system variables into message. Here's example of message:
{
"ip": "#{ip_address}",
"host": "#{host_name}",
"some_data": "#{env.VARIABLE}",
"some_more_data": "Some static data"
}

In this example ip_address and host_name are variables substituted by emitter. env.VARIABLE is an environment variable.

Copied from original issue: syncloud/apps#13

From @cyberb on September 23, 2014 8:37

Copied from original issue: syncloud/apps#9

From @cyberb on February 22, 2015 1:10

User should be able to enter login/pass on device activation once and reuse it for all installed services.

Options:

1. Plain text master login/password.
   Problems:
   1.1. Pain text
   1.2. Password change is a problem
2. LDAP server.
   Problems:
   2.1. App servers may not support LDAP.

LDAP support:
ownCloud: natively
Gitlab: natively
Diaspora: through ldap plugin for Device (their auth backend)
Gitbucket: natively

Copied from original issue: syncloud-old/server#3