1.1 - Bulk upload and fixes
- Bulk upload:
you can upload multiple files as a queue, without having to confirm one at a time
- Dots parsing fix:
fixed a bug that made the server unusable when there were dots in the name
- Documentation update:
specified download folder path type and removed Docker references as it is not used
1.2 - Bulk download, folder deletion, wiki, client startup and fixes
- Bulk download:
you can download all the files in a folder with a single click
- Complete folder deletion unlock:
you can delete a folder and all the files in it
This is a dangerous operation, so a dedicated button has been added to make sure the operation is voluntary
- Invalid special characters in the file name fix:
fixed an error due to file names containing special characters that caused the server crash
- Client opening at server startup:
after the server loads, the client will start fully automatically in the default browser
- Wiki:
a wiki has been implemented (this one on which you are reading)
1.3 - Corrupted files management, startup checks and logs refactoring
- Downloading a corrupted file:
if a file is corrupted, the download will not works and the user is informed
- Manual deletion of corrupted files:
server no longer crashes when trying to manually delete a corrupted file
- Missing env file:
during startup, the server checks whether the .env file has been created
- Integrity checks:
during startup, the server detects and deletes any corrupted file
- Logs refactoring:
server logs are more readable
- Server already running:
if the server is already started and the user is trying to start a new instance, he will be informed about the running instance
1.4.1 - Concurrent chunks upload, technical/bug fixes, better logs, UI fixes
1.4
- Concurrent chunks upload:
files can be uploaded by transmitting multiple chunks simultaneously depending on your connection speed
- Upload status:
shown the number of chunks loaded and not the chunk that is currently uploading
- Network error codes:
in case of network error, its code is now shown in the logs
- Better contrast in input fields:
text in input fields and select boxes are black and bold
- Better contrast in the loading overlay:
it darkens the page more
- Fixed mismatched firebase metadata on corrupted data:
now the server no longer dies in that case
1.4.1 patch
- Attempts system on concurrent chunks upload:
uploading on Telegram may occasionally encounter errors due to Telegram's own server issues. This hotfix adds a system that allows for retrying the upload without having to restart it from scratch.
2.1 - Faster integrity checks, startup logs cleaner, scheduled deletion
- Faster integrity checks:
integrity checks on files and folders were performed sequentially, whereas now they are performed
asynchronously, so that multiple files and folders are checked at the same time
- Loading bar on startup:
integrity checks progress is shown in the server console via a loading bar
- Startup logs cleaner:
server startup cleans the server console of old logs
- Scheduled deletion:
when you download an entire folder you can schedule its automatic deletion. You must keep the server turned on to allow deletion
- Download path on server folder fix:
due to a problem with the construction of the download path, it happened that the downloaded files ended up in the HorizonGram server folder. This bug has been fixed
Note: how can i setup the scheduled deletion time?
Follow this guide.
2.2 - Template executors, configuration checks, bug fixes
- Template executors:
now you can startup HorizonGram and change the profile with few clicks!
You don't need anymore to edit sources or launch npm start command.
- Checks on profile parameters:
some checks have been implemented in the
config.json file inherent to profile management to avoid some errors due to incorrect profile setting.
- Cannot delete files sent more than 48 hours ago:
in case of deleting older files, HorizonGram would throw an error. This problem was solved by acting directly on the metadata database.
- Clarifications about Node.js version into documentation:
Node.js v.14+ is needed to avoid errors during execution.
- Error not shown when upload fails:
it was readable in the site's dev console. Now it is available directly on the upload page.
Note: how can i setup startup and profile shortcuts?
Follow this guide.
