Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Armbian APT upload process

Featured Replies

@Igor Could we imagine another mechanism than to use git as an "upload front-end" ?

 

Using git as some kind of spool folder is really not ideal.  For instance if I clone today the armbian upload git project the size of the objects is already reaching 1.2 GB for a project that is essentially just a structure of empty folders. I even see the following error during cloning

 

Cloning into 'upload'...
remote: Enumerating objects: 75, done.
remote: Counting objects: 100% (75/75), done.
remote: Compressing objects: 100% (61/61), done.
kex protocol error: type 7 seq 49316022.52 MiB | 6.67 MiB/s    
remote: Total 844 (delta 33), reused 40 (delta 14), pack-reused 769
Receiving objects: 100% (844/844), 1.22 GiB | 6.03 MiB/s, done.
Resolving deltas: 100% (251/251), done.

 

The easier would be to provide a FTP service with the same structure and limited access to people you grant right to upload.

 

 

 

 

 

12 hours ago, gprovost said:

@Igor Could we imagine another mechanism than to use git as an "upload front-end" ?

 

Using git as some kind of spool folder is really not ideal.  For instance if I clone today the armbian upload git project the size of the objects is already reaching 1.2 GB for a project that is essentially just a structure of empty folders. I even see the following error during cloning

 


Cloning into 'upload'...
remote: Enumerating objects: 75, done.
remote: Counting objects: 100% (75/75), done.
remote: Compressing objects: 100% (61/61), done.
kex protocol error: type 7 seq 49316022.52 MiB | 6.67 MiB/s    
remote: Total 844 (delta 33), reused 40 (delta 14), pack-reused 769
Receiving objects: 100% (844/844), 1.22 GiB | 6.03 MiB/s, done.
Resolving deltas: 100% (251/251), done.

 

The easier would be to provide a FTP service with the same structure and limited access to people you grant right to upload.

Is it for long term storage, or just for exchanging data....  I could setup some object storage.. i think there's even an official SFTP gateway fro s3 now.

Edited by Tido
fixed quote

On 3/14/2019 at 9:38 AM, gprovost said:

The easier would be to provide a FTP service with the same structure and limited access to people you grant right to upload.


Prepared. Anyone needs a (s)ftp access to repository incoming directory should send me a public key. Structure is the same as from the build script.

  • Author
3 hours ago, Igor said:

Prepared. Anyone needs a (s)ftp access to repository incoming directory should send me a public key. Structure is the same as from the build script.

 

Great ! Just sent you my pub key by PM ;-)

  • Author

Sure, no rush... on my side I don't have any package to push.

 

BTW what will be the sftp address ?

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.