blomp-cloud-storage-docs

Blomp Cloud Storage documentatioin

blomp-cloud-storage-docs

Blomp Cloud Storage documentatioin

Table of content

blomp-cloud-storage-docs

Rclone - Installation and documentation

Repository contains outdated rclone version which lacks on several features where one of them is selfupdate function. You can install from repository.

I suggest to either download latest binaries or compile and install from source. On later points you will upgrade binary directly with rclone selfupdate as well for beta rclone selfupdate --beta for those who want to test latest version.

For installation guides and more info visit official rclone description which is always kept up to date.

Please see the full list of all storage providers and their features

Rclone Features

MD5/SHA-1 hashes checked at all times for file integrity
Timestamps preserved on files
Partial syncs supported on a whole file basis
Copy mode to just copy new/changed files
Sync (one way) mode to make a directory identical
Check mode to check for file hash equality
Can sync to and from network, e.g. two different cloud accounts
Optional large file chunking (Chunker)
Optional transparent compression (Compress)
Optional encryption (Crypt)
Optional FUSE mount (rclone mount)
Multi-threaded downloads to local disk
Can serve local or remote files over HTTP/WebDav/FTP/SFTP/dlna

Rclone Installation & documentation

Please see the rclone website for:

Rclone Downloads

https://rclone.org/downloads/

Create rclone config for Blomp cloud storage (first time install)

As example we will use several rclone modules combined to offer some general use example. For more info about swift, chunker, crypt and compress modules as well as description of mount command can be found at official rclone documentation.

Table of demo remotes

Here is a table of demo configuration remotes and alias.

name	storage type	chunk size*¹	encrypted	compressed	max. file size
`blomp-remote`	`swift`	`1P`	no	no	`5242879K`
`blomp-alias`	`alias`	`1P`	no	no	`5242879K`
`blomp-chunker`	`chunker`	`5242879K`	no	no	unlimited*²
`blomp-trezor`	`crypt`	`5242879K`	yes	no	unlimited*²
`blomp-chunker-archive`	`compress`	`5242879K`	no	yes	unlimited*²
`blomp-trezor-archive`	`compress`	`5242879K`	yes	yes	unlimited*²

*¹ - setting swift to 1P technically disables chunker and only files equal/smaller than max. file size can uploaded.
*² - as long as there is free space and chunk naming allows enough chunks

Table description

blomp-remote is main blomp storage
blomp chunker is chunker overlay which chunks data. This can be used for different purposes, one of them would be for abililty to get error Blomp’s max file size restriction or for users who care about privacy and security and want their files to be chunked into some specific size to hide actual file size. In current demo, we will use max. allowed file size as chunk_size, all files smaller than 5G will not be chunked, only files bigger than 5G
blomp-chunker-archive is compress overlay with max gzip compression using chunker. This is especially usefull for archive purpose as well for storage of disk images which do normally contain free space, compressing such images on the fly.
blomp-trezor is overlay using chunker for ability to upload files bigger than 5G which do require manual chunking or for security purpose to hide real file size.
blomp-trezor-archive is copmress overlay for encrypted and chunked data. Similar to blomp-chunker-archive, this is very usefull for image backups which contain some sensible data and one would like to have it stored encrypted

Start rclone config

to add/edit/encrypt rclone config file, run

rclone --config ~/.config/rclone/blomp-demo.conf config`

Create remote config for Blomp

Add new Blomp remote

<5>NOTICE: Config file "/home/tor/.config/rclone/blomp-demo.conf" not found - using defaults
No remotes found - make a new one
n) New remote
s) Set configuration password
q) Quit config
n/s/q> n

select name for your remote, in our example we use blomp-remote
```
 name> blomp-remote
```
select storage type, choose swift
```
Storage> swift
```
ℹ️ - type either swift or the number from the list, at the time of creation of current document it is 28

See help for swift backend at: https://rclone.org/swift/
```
28 / OpenStack Swift (Rackspace Cloud Files, Memset Memstore, OVH)
\ "swift"
```
For current example we will not use swift credentials from environment variables as we might want use different accounts from same provider. Default value is false, leave it blank or enter false and press enter.
```
env_auth> 
```

Set credentials, your user (demo@mail.com) and password (demopasswd123)

User name to log in (OS_USERNAME).
Enter a string value. Press Enter for the default ("").
user> demo@mail.com
API key or password (OS_PASSWORD).
Enter a string value. Press Enter for the default ("").
key> demopasswd123

Set Authentification URL to https://authenticate.blomp.com
```
auth> https://authenticate.ain.net
```
ℹ️ - you can use 2 different domains, https://authenticate.ain.net is used by blomp rclone app, where https://authenticate.blomp.com is preffered URL and blomp dashboard says it should be used
user_id and user_domain are optional for v3 auth, leave it blank (ℹ️ - Blomp uses v2 auth)
```
user_id> 
domain> 
```
Set tenant name to storage
```
tenant> storage
```
Leave tenant tenant ID blank
```
tenant_id> 
```

leave blank all following options until you get to auth_version, type 2 and press enter

auth_version> 2

ℹ️ - Blank options before you are asked for auth_version

Tenant ID - optional for v1 auth, this or tenant required otherwise (OS_TENANT_ID)
Enter a string value. Press Enter for the default ("").
tenant_id> 
Tenant domain - optional (v3 auth) (OS_PROJECT_DOMAIN_NAME)
Enter a string value. Press Enter for the default ("").
tenant_domain> 
Region name - optional (OS_REGION_NAME)
Enter a string value. Press Enter for the default ("").
region> 
Storage URL - optional (OS_STORAGE_URL)
Enter a string value. Press Enter for the default ("").
storage_url> 
Auth Token from alternate authentication - optional (OS_AUTH_TOKEN)
Enter a string value. Press Enter for the default ("").
auth_token> 
Application Credential ID (OS_APPLICATION_CREDENTIAL_ID)
Enter a string value. Press Enter for the default ("").
application_credential_id> 
Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME)
Enter a string value. Press Enter for the default ("").
application_credential_name> 
Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET)
Enter a string value. Press Enter for the default ("").
application_credential_secret> 
AuthVersion - optional - set to (1,2,3) if your auth URL has no version (ST_AUTH_VERSION)
Enter a signed integer. Press Enter for the default ("0").

Select public Endpoint type
```
endpoint_type> public
```
Keep storage policy blank
```
storage_policy> 
```

Set advanced options (optional)

Edit advanced config? (y/n)
y) Yes
n) No (default)
y/n>

Optional - advanced config

avoid calling abort upload on a failure
```
leave_parts_on_error> true
```
Set above which size files will be chunked into a _segments container
```
chunk_size> 1P
```
ℹ️ - swift default and max size is 5G (5242880K) which currently does not work with blomp with error message Permission denied. Setting it to 1P disables chunking and resolves Permission Error, max file size is 5242880K.
Don’t chunk files during streaming upload.
```
no_chunk> false
```
ℹ️ When doing streaming uploads (e.g. using rcat or mount) setting this flag will cause the swift backend to not upload chunked files.

This will limit the maximum upload size to 5GB. However non chunked files are easier to deal with and have an MD5SUM.

Rclone will still chunk files bigger than chunk_size when doing normal copy operations. Default value is false
Set encoding for backend, leave blank and press enter unless you know what you do.
```
encoding> 
```

Finished, check your config once again and confirm with y if everything is OK

Remote config
--------------------
[blomp-remote]
type = swift
user = demo@mail.com
key = demopasswd123
auth = https://authenticate.ain.net
tenant = storage
auth_version = 2
endpoint_type = public
leave_parts_on_error = true
chunk_size = 1P
no_chunk = false
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote

y/e/d> y

if you are finished, quit config by typing q and press enter, for current guide continue and create new remote alias

Current remotes:

Name    Type
====    ====
blomp-remote         swift

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

e/n/d/r/c/s/q>

Local overlays - chunker, compress and crypt

With blomp you can use overlays directly, but it is not recommended.

Use instead local overlays of chunker, compress and crypt.

Example config for local filesystem, chunker, compress and crypt:

# configure local filesystem, in current case we want to use one_file_system, for more info read https://rclone.org/local/#restricting-filesystems-with-one-file-system
[local]
type = local
nounc = true
one_file_system = true
case_sensitive = true
no_preallocate = true
no_set_modtime = true

# alias for Blomp online storage for easier access
[blomp-alias]
type = alias
remote = blomp-remote:demo@mail.com

# local filesystem alias for easier/simpler access.
# remote in current case is the folder
# ensure that your user is the owner of that folder and has write access
[blomp-local]
type = alias
remote = local:/media/yourusername/blomp-local

# local chunker for Blomp, chunking only files above chunk_size
# norename is used to speed up the process
# max number of chunks is 99999, to change it, edit amount of # in name_format
[blomp-local-chunker]
type = chunker
remote = blomp-local:
chunk_size = 5242879K
name_format = *.#####
start_from = 1
hash_type = md5
meta_format = simplejson
fail_hard = false
transactions = norename

# local compression to gzip with highest compression, level 9 is highest compression
[blomp-local-gzip]
type = compress
remote = blomp-local:
level = 9

# local encrypt/decrypt module. 
# Crypt module should be created with rclone config where your password will be save encrypted to rclone.conf
[blomp-local-trezor]
type = crypt
remote = blomp-local:trezor
filename_encryption = standard
directory_name_encryption = true
password = ***ENCRYPTED-PASS***
password2 = ***ENCRYPTED-PASS***
no_data_encryption = false

overlays over local overlays

Here are few examples of how different local overlays can be combined.

[blomp-local-gzip-chunked]
type = compress
remote = blomp-local-chunker:
level = 9

[blomp-local-chunked-gzip]
type = chunker
remote = blomp-local-gzip:
chunk_size = 5242879K
name_format = *.#####
start_from = 1
hash_type = md5
meta_format = simplejson
fail_hard = false
transactions = norename

[blomp-local-trezor-chunked]
type = crypt
remote = blomp-local-chunker:trezor
filename_encryption = standard
directory_name_encryption = true
password = ***ENCRYPTED-PASS***
password2 = ***ENCRYPTED-PASS***
no_data_encryption = false

[blomp-local-trezor-gzip-chunked]
type = crypt
remote = blomp-local-gzip-chunked:trezor
filename_encryption = standard
directory_name_encryption = true
password = ***ENCRYPTED-PASS***
password2 = ***ENCRYPTED-PASS***
no_data_encryption = false

# do not use
[blomp-local-trezor-chunked-gzip]
type = crypt
remote = blomp-local-chunked-gzip:trezor
filename_encryption = standard
directory_name_encryption = true
password = ***ENCRYPTED-PASS***
password2 = ***ENCRYPTED-PASS***
no_data_encryption = false

Advanced Configuration for Blomp with rclone

Advanced configuration example allows a user combination of mountable remotes for different use case.

In simple words:

Normal usage without file size limit
- Archive, compressed drive with gzip, max compression
Encryption without file size limit
- Encryption archive (compressed with gzip, max compression)

Create alias for remote for blomp-remote

If you quit rclone config, follow Start rclone config to restart config.

We will use alias for easier access in further configuration as well for easier usage in terminal and spare us typing buckett which for blomp is your email address.

rclone --config ~/.config/rclone/blomp-demo.conf config`

Create alias for remote - add new remote alias

which we will call blomp for simple use in future and as last select remote/path to alias blomp-remote

Current remotes:

Name    Type
====    ====
blomp-remote         swift

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> n

name> blomp-alias

Create alias for remote - select storage type
```
Storage> alias
```
Create alias for remote - select remote to alias
```
remote> blomp-remote:demo@mail.com
```

Create alias for remote - Confirm alias settings

Remote config
--------------------
[blomp-alias]
type = alias
remote = blomp-remote:demo@mail.com
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote

y/e/d> y

Create chunker overlay for blomp

At the time of writting this guide, --swift-chunk-size option is not working with Blomp. Currently files bigger than 5242879K can be uploaded with:

web browser on your dashboard
additional chunker overlay in rclone.conf
BlompLive Only BlompSupport could confirm that it works, until the time of creation of current document it never worked for me)
BlompGo

Due to file size restriction, all other overlays will use chunker as their remote. That way we get around file size limit without any loss of time compared to uploads without chunker overlay.

If you quit rclone config, follow Start rclone config to restart config.

Create new chunker remote for blomp-alias

Name                 Type
====                 ====
blomp-alias          alias
blomp-remote         swift

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

e/n/d/r/c/s/q> n
name> blomp-chunker    
Storage> chunker
remote> blomp-alias:
chunk_size> 5242879K
hash_type> none

Optional, advanced chunker settings

Set string format of file names*³
```
name_format> *.#####
```
*³ - * is filename and # stands for max possible amount of chunks, ##### means max 99999 chunks are available, with 5G chunk size, max. file size would be 488T (488.276367188T). Rclone’s default is *.rclone_chunk.###
Set minimum valid chunk number, default is 1
```
start_from> 1
```
Set metadata object format

We will use norename and it requires meta_format not to be none
```
meta_format> simplejson
```
Choose how chunker should handle files with missing or invalid chunks.

For current guide we will use: Warn user, skip incomplete file and proceed.
```
fail_hard> false
```
Choose how chunker should handle temporary files during transactions.

We do not want chunker to rename files as it requires additional copy and delete operation which for Blomp takes very long time and is very slow.
```
transactions> norename
```

Confirm chunker settings

Remote config
--------------------
[blomp-chunker]
type = chunker
remote = blomp-alias:
chunk_size = 5.000G
hash_type = none
name_format = *.#####
start_from = 1
meta_format = simplejson
fail_hard = false
transactions = norename
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote

y/e/d> y

⚠️ - Ensure to change chunk_size from 5.000G to 5242879K, as otherwise chunker will fail. You can set any lower value like 1G.

Create crypt overlay for blomp chunker

Create new crypt remote for blomp-chunker

Current remotes:

Name                 Type
====                 ====
blomp-alias          alias
blomp-chunker        chunker
blomp-remote         swift

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

e/n/d/r/c/s/q> n
name> blomp-trezor
Storage> crypt
remote> blomp-chunker:trezor
filename_encryption> standard
directory_name_encryption> true

Set your password for encryption

Password or pass phrase for encryption.
y) Yes type in my own password
g) Generate random password
y/g> y

Set password for encryption:

password: cryptpass12345

Confirm the password:

password: cryptpass12345

Set password or pass phrase for salt

Password or pass phrase for salt. Optional but recommended.
Should be different to the previous password.
y) Yes type in my own password
g) Generate random password
n) No leave this optional password blank (default)
y/g/n> y

Set password for salt:

password: cryptpassSalt1

Confirm password for salt:

password: cryptpassSalt1

Optional advanced settings

Allow server-side operations (e.g. copy) to work across different crypt configs
```
erver_side_across_configs> false
```
Encrypt file data
```
no_data_encryption> false
```

Confirm crypt settings

Remote config
--------------------
[blomp-trezor]
type = crypt
remote = blomp-chunker:trezor
filename_encryption = standard
directory_name_encryption = true
password = *** ENCRYPTED ***
password2 = *** ENCRYPTED ***
server_side_across_configs = false
no_data_encryption = false
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d> y

Create compress overlay for blomp crypt overlay

Create new crypt overlay over blomp-chunker

Current remotes:

Name                 Type
====                 ====
blomp-alias          alias
blomp-chunker        chunker
blomp-remote         swift
blomp-trezor         crypt

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

e/n/d/r/c/s/q> n
name> blomp-trezor-archive
Storage> compress
remote> blomp-trezor:archive
mode> gzip

Optional advanced settings

Set compression level
```
level> 9
```
GZIP compression level (-2 to 9).
- Generally -1 (default, equivalent to 5) is recommended.
- Levels 1 to 9 increase compressiong at the cost of speed.. Going past 6 generally offers very little return.
- Level -2 uses Huffmann encoding only. Only use if you now what you are doing
- Level 0 turns off compression.
Some remotes don’t allow the upload of files with unknown size.
```
ram_cache_limit> 20M
```

Confirm compress overlay settings

Remote config
--------------------
[blomp-trezor-archive]
type = compress
remote = blomp-trezor:archive
mode = gzip
level = 9
ram_cache_limit = 20M
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote

y/e/d> y

Create compress overlay for blomp chunker overlay

Create new crypt overlay over blomp-chunker

Current remotes:

Name                 Type
====                 ====
blomp-alias          alias
blomp-chunker        chunker
blomp-remote         swift
blomp-trezor         crypt
blomp-trezor-archive compress

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

e/n/d/r/c/s/q> n
name> blomp-chunker-archive
Storage> compress
remote> blomp-chunker:archive
mode> gzip

Optional advanced settings

Set compression level
```
level> 9
```
GZIP compression level (-2 to 9).
- Generally -1 (default, equivalent to 5) is recommended.
- Levels 1 to 9 increase compressiong at the cost of speed.. Going past 6 generally offers very little return.
- Level -2 uses Huffmann encoding only. Only use if you now what you are doing
- Level 0 turns off compression.
Some remotes don’t allow the upload of files with unknown size.
```
ram_cache_limit> 20M
```

Confirm compress overlay settings

Remote config
--------------------
[blomp-chunker-archive]
type = compress
remote = blomp-chunker:archive
mode = gzip
level = 9
ram_cache_limit = 20M
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote

y/e/d> y

Finished, remote overview and quit rclone config

Current remotes:

Name                 Type
====                 ====
blomp-alias          alias
blomp-chunker        chunker
blomp-chunker-archive compress
blomp-remote         swift
blomp-trezor         crypt
blomp-trezor-archive compress

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config

e/n/d/r/c/s/q> q

Demo config (local filesystem) - rclone.conf (recommended)

This configuration is recommended. Chunker should not be required at all, but as swift-chunk-size on blomp does not work for anybody except blomp team, we are forced to use it as workaround.

ℹ️ - I have to mention that in my local example for chunker I use max allowed file size of 5GB - 1KB. If you want to combine your blomp with several other cloud storages in one drive, then choose for chunker the size of storage which offers smallest size, take as example dropbox, onedrive and other which have its own restrictions on max file size. You can set it to small sizes like 3M or 5M if you want.

# configure local filesystem, in current case we want to use one_file_system, for more info read https://rclone.org/local/#restricting-filesystems-with-one-file-system
[local]
type = local
nounc = true
one_file_system = true
case_sensitive = true
no_preallocate = true
no_set_modtime = true

# alias for Blomp online storage for easier access
[blomp-alias]
type = alias
remote = blomp-remote:demo@mail.com

# local filesystem alias for easier/simpler access.
# remote in current case is the folder
# ensure that your user is the owner of that folder and has write access
[blomp-local]
type = alias
remote = local:/media/yourusername/blomp-local

# local chunker for Blomp, chunking only files above chunk_size
# norename is used to speed up the process
# max number of chunks is 99999, to change it, edit amount of # in name_format
[blomp-local-chunker]
type = chunker
remote = blomp-local:
chunk_size = 5242879K
name_format = *.#####
start_from = 1
hash_type = md5
meta_format = simplejson
fail_hard = false
transactions = norename

# local compression to gzip with highest compression, level 9 is highest compression
[blomp-local-gzip]
type = compress
remote = blomp-local:
level = 9

# local encrypt/decrypt module. 
# Crypt module should be created with rclone config where your password will be save encrypted to rclone.conf
[blomp-local-trezor]
type = crypt
remote = blomp-local:trezor
filename_encryption = standard
directory_name_encryption = true
password = ***ENCRYPTED-PASS***
password2 = ***ENCRYPTED-PASS***
no_data_encryption = false

Demo config (using remote only) - rclone.conf (not recommended for use)

[blomp-remote]
type = swift
user = demo@mail.com
key = demopasswd123
auth = https://authenticate.ain.net
tenant = storage
auth_version = 2
endpoint_type = public
leave_parts_on_error = true
chunk_size = 1P
no_chunk = false

[blomp-alias]
type = alias
remote = blomp-remote:demo@mail.com

[blomp-chunker]
type = chunker
remote = blomp-alias:
chunk_size = 5242879K
hash_type = none
name_format = *.#####
start_from = 1
meta_format = simplejson
fail_hard = false
transactions = norename

[blomp-trezor]
type = crypt
remote = blomp-chunker:trezor
filename_encryption = standard
directory_name_encryption = true
password = 8QSBAdBXqPpgQbH1-ri2jsK6t52fgjVPhR79qazL
password2 = uWe6EbZuUOZwjCoOxzj6czp-15xCafDOa9NmjAZ0
server_side_across_configs = false
no_data_encryption = false

[blomp-trezor-archive]
type = compress
remote = blomp-trezor:archive
mode = gzip
level = 9
ram_cache_limit = 20M

[blomp-chunker-archive]
type = compress
remote = blomp-chunker:archive
mode = gzip
level = 9
ram_cache_limit = 20M

Demo Systemd service files

Example how some basic service file mounting drive on system launch could look like. Here are 5 service files which could be enabled, you can test those by simply replacing credentials in rclone.conf.

it is much faster because operations and processes on remote
- in my examples I use norename for chunker simply because I tested one huge file and I wanted to spare uploading unrenamed chunks before huge file is uploaded, for smaller files than 20 gb you can and probably should use rename in chunker config.
requires much less:s
- time
- bandwidth

Using overlays directly on remote was only for testing purpose if it works and it does work, but it should not be used as users will have pretty bad experience compared to local filesystem.

local overlays (recommended)

I recommend to use local overlays for whatever should be done in regard of chunking, compression and encryption/decryption. One of main reasons is that local overlays are much faster, due to very long wait times for copy/move, you would end up wasting a lot bandwidth and time, exceeding in few times the real amount of data which you need to upload.

In configs I used max. allowed file size for blomp which is currently 5Gbyte-1Kbyte.
- Info for union remote:
  - the smaller the chunk size, the better it is in regard of using max available free space.
  - the bigger the chunk size, the better it is in regard of performance but may leave few accounts with <chunk_size amount of free space.
blomp (local remote chunked, shows chunked files)
blomp-local-compress (local remote compress, shows compressed files as one)
blomp-trezor (local remote crypt, shows decrypted files and folders)
non local overlays (not recommended)
blomp
- blomp-chunker
  - blomp-chunker-archive
- blomp-trezor
  - blomp-trezor-archive

How to enable service

Enable service, example with blomp-trezor-archive:

sudo systemctl enable blomp-trezor-archive

Disable service, example with blomp-trezor-archive:

sudo systemctl enable blomp-trezor-archive

How to start/stop/restart service

You can use start to start, stop to stop and restart to restart running service.

All examples with blomp-trezor-archive:

sudo systemctl start blomp-trezor-archive

sudo systemctl stop blomp-trezor-archive

sudo systemctl restart blomp-trezor-archive

Blomp limitations

There are several limits and restrictions on Blomp for now. It is not know to me if there are plans to either update product description or to raise limits to claimed unlimited, however, here are few restrictions

Max file size: using Dashboard upload

By uploading files via browser you are restricted in many points compared to mounting it as a drive. One of those is max file size which is: 100GB, you can not upload files bigger than 100GB.

Max file size: BlompLive

BlompGo is a blomp’s application for PC which is very restricted in features compared to rclone, max file size seems to be under 5G, exactly 5242879K. Files bigger/equal 5242879K can not be uploaded

Max file size: BlompGo

Blomp Live is blomp’s application mounting disk as Z: drive. Here we currently also have restriction of max file size 5242879K. BlompSupport could show logs where –swift-chunk-size works and files are indeed properly segmented into _segments container. However, nobody except BlompSupport could confirm by log that it works, we all get permission denied error which indicates that it is planned that chunker works. For now it does not for any user and by that max. file size restriction is same as with BlompLive, which is exactly 5242879K. Currently, files bigger than 5242879K can not be uploaded via BlompGo (your Z: drive)

Swift has in general restriction with max file size of 5G. Here is some explanation of limits connected to that.

The Swift API doesn’t return a correct MD5SUM for segmented files (Dynamic or Static Large Objects) so rclone won’t check or use the MD5SUM for these.

blomp-cloud-storage-docs

Table of content

Rclone - Installation and documentation

Rclone Features

Rclone Installation & documentation

Rclone Downloads

Create rclone config for Blomp cloud storage (first time install)

Table of demo remotes

Table description

Start rclone config

Create remote config for Blomp

Optional - advanced config

Local overlays - chunker, compress and crypt

overlays over local overlays

Advanced Configuration for Blomp with rclone

Create alias for remote for blomp-remote

Create chunker overlay for blomp

Optional, advanced chunker settings

Create crypt overlay for blomp chunker

Optional advanced settings

Create compress overlay for blomp crypt overlay

Optional advanced settings

Create compress overlay for blomp chunker overlay

Optional advanced settings

Finished, remote overview and quit rclone config

Demo config (local filesystem) - rclone.conf (recommended)

Demo config (using remote only) - rclone.conf (not recommended for use)

Demo Systemd service files

Why do I recommend to use local filesystem for compress, chunking and crypt

local overlays (recommended)

non local overlays (not recommended)

How to enable service

How to start/stop/restart service

Blomp limitations

Max file size: using Dashboard upload

Max file size: BlompLive

Max file size: BlompGo