Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/deploy incremental #34

Closed

Conversation

ThornWalli
Copy link

@ThornWalli ThornWalli commented Nov 2, 2020

Hello

Would have an adaptation for the Deploy CLI process.

Background was that I have a website where I upload up to 4000 files with each deployment.

The upload now, is suitable for the case with < 1000 files.
With large amounts of data, many files are uploaded unnecessarily and consume the app quota (e.g. requests).

With the change from the PR there will be incremental upload.
Initially we will check which files have to be uploaded at all.

Important: For the incremental upload the eTag and lastModified of the file objects will be used. Here it was missing the storage of both properties in the file lib/binding/File.js, if files were retrieved via listFiles.

There are two new options for the 'deploy' command.

--clean-up

If the --clean-up option is set, all unused files are removed from the bucket. Ideal for static pages where an HTML file disappears 馃檭

--upload-limit

With the option --upload-limit the number of parallel uploads can be defined. Default is 2.

@fbuecklers
Copy link
Member

Sorry, can you reopen this MR based on the main branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants