aws-sdk-go
rclone
aws-sdk-go | rclone | |
---|---|---|
34 | 963 | |
8,548 | 43,840 | |
0.2% | 1.1% | |
9.4 | 9.8 | |
1 day ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aws-sdk-go
- my first go project, a CLI application to store IP addresses
-
Go 1.21 will (probably) download newer toolchains on demand by default
I'm... really not sure I agree with this, from a philosophical point of view. It feels like this is making "eh, we'll just upgrade our Go version next quarter" too easy; ultimately some responsibility toward updating your application's Go version to work with what new dependencies require should fall on Us, the application developers. Sure, we're bad at it. Everyone's lived through running years-old versions of some toolchain. But I think this just makes the problem worse, not better.
Its compounded by the problem that, when you're setting up a new library, the `go` directive in the mod file defaults to your current toolchain; most likely a very current one. It would take a not-insignificant effort on the library author's part to change that to assert the true-minimum version of Go required, based on libraries and language features and such. That's an effort most devs won't take on.
I'd also guess that many developers, up-to this point if not indefinitely because education is hard, interpreted that `go` directive to mean more-of "the version of go this was built with"; not necessarily "the version of go minimally required". There are really major libraries (kubernetes/client-go [1]) which assert a minimum go version of 1.20; the latest version (see, for comparison, the aws-sdk, which specifies a more reasonable go1.11 [2]). I haven't, you know, fully audited these libraries, but 1.20 wasn't exactly a major release with huge language and library changes; do they really need 1.20? If devs haven't traditionally operated in this world where keeping this value super-current results in actually significant downstream costs in network bandwidth (go1.20 is 100mb!) and CI runtime, do we have confidence that the community will adapt? There's millions of Go packages out there.
Or, will a future version of Go patch a security update, not backport it more than one version or so, and libraries have to specify the newest `go` directive version, because manifest security scanning and policy and whatever? Like, yeah, I get the rosy worldview of "your minimum version encodes required language and library features", but its not obvious to me that this is how this field is, or even will be, used.
Just a LOT of tertiary costs to this change which I hope the team has thought through.
[1] https://github.com/kubernetes/client-go/blob/master/go.mod#L...
[2] https://github.com/aws/aws-sdk-go/blob/main/go.mod
- How to get better on golang
-
Send an Email through AWS SES with GoLang
This email was sent with " + "Amazon SES using the " + "AWS SDK for Go.
-
Looking for library recommendations: Django -> Golang port
I figured I'd ask the community for some recommendations for the following capabilities that Django + python stack is giving me at the moment: 1. Amazon SES Mailing (considering - aws-sdk-go) 2. Django Admin (considering go-admin 3. Django Signals (considering syncsignals 4. Celery (No contenders here)
-
S3 upload with progress
I've been trying to implement some logging of progress when uploading objects to S3. My code is building on this example and can be found here.
-
Background process in Lambda using SQS
Now that you have everything you need, let’s install the AWS SDK for Go library.
- Node.js 18 support in Lambda added to Go SDK
- Node.js 18 Runtime support added to Golang SDK
-
AWS and its complicated shit needs to die
Counterpoint 2: Amazon is bad and should feel bad for making this an internal and embedding it in the Credentials struct.
rclone
-
Supabase Storage: now supports the S3 protocol
rclone: a command-line program to manage files on cloud storage.
- World Backup Day
-
S3 Client against disasters (hacks, fires, catastrophes)
Synchronise buckets with Sclone or Rclone
- Show HN: Query Your Sheets with SheetSQL
-
Rclone syncs your files to cloud storage
Says that Apple doesn't provide a multi platform API. It doesn't provide any official supported way to access iCloud from Windows, Linux.
There's a ticket covering everything you might ever want to know:
https://github.com/rclone/rclone/issues/1778
-
Ask HN: Best modern file transfer/synchronization protocol?
seconding rsync and syncthing.
the server could expose an smb or nfs share, the client could mount it, and then sync to that mount.
rsync over ssh also works, if you do not want to run smb/nfs.
this is also a cool tool https://rclone.org/
-
Ask HN: How do you do personal backups in 2023? (Google and Dropbox issues)
rclone [1] to dropbox. works since years without problems
[1] https://rclone.org/
-
Which synchronization tool are you using together with the pCloud Crypto Folder?
rclone provides a special pCloud config option, which makes the setup straight forward. rclone can encrypt the data it uploads with its own encryption but not with the pCloud encryption. Therefore it can only upload data to the unencrypted pCloud folders, not to the Crypto Folder.
- Backup of Google Drive (and photos?) to local disk (not to Google Drive)
-
All I want for Christmas is
The arkclone project impliments rclone in ArkOS to achieve cloud saves. Not yet built in to ArkOS yet, and not a lot of recent traction on the pull request to get it added, but it can be installed manually.
What are some alternatives?
minio-go - MinIO Go client SDK for S3 compatible object storage
syncthing - Open Source Continuous File Synchronization
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
Cryptomator - Multi-platform transparent client-side encryption of your files in the cloud
botocore - The low-level, core functionality of boto3 and the AWS CLI.
rsync - An open source utility that provides fast incremental file transfer. It also has useful features for backup and restore operations among many other use cases.
twitter-scraper - Scrape the Twitter frontend API without authentication with Golang.
s3fs-fuse - FUSE-based file system backed by Amazon S3
cachet - Go(lang) client library for Cachet (open source status page system).
Duplicati - Store securely encrypted backups in the cloud!
goamz
aws-cli - Universal Command Line Interface for Amazon Web Services