awscli-local VS shadow

> not really.. as soon as you need cloud resources that are not in your k8s cluster, you end up with the cloud in your development loop.

https://github.com/localstack/awscli-local

https://github.com/fsouza/fake-gcs-server

https://cloud.google.com/sdk/docs/downloads-docker

I’ve used all of these locally to great success.

Glad to hear you guys want to interop with npm. Is wing going to be a superset of js then?

awslocal CLI

https://localstack.cloud/ https://github.com/localstack/awscli-local

I also used awslocal as my CLI tool for interacting with my Localstack AWS environment. Assuming you already have aws cli installed, awslocal can be installed using:

If you want to test your created resources, you can always use the official AWS-CLI. However I found a library called awscli-Local, which already knows the LocalStack endpoints and you can use just like the official one from AWS. I’m presenting a couple of useful commands that you might need:

So: I am making a JavaFX application to act as a remote console for my server. I'm the only person that will have a copy of it, so it doesn't need to be snazzy or 100% efficient. I have turned the project into a jar via ShadowJar, turned that into an EXE via Launch4j, and yesterday turned that into an installer via Inno.

I’ve never tried this and I I’m not libgdx expert, but you can try running a Uber jar with shadow. it’s the Gradle equivalent of the shade plug-in for maven builds.

When you get into a situation where you need to sandbox a dependency within another, including this example, where you want each of your dependencies to get its own unique instance of their dependency, you can "shadow" the dependency that is to be sandboxed this way. Look into https://github.com/johnrengelman/shadow.

Try using the shadow plugin for gradle https://github.com/johnrengelman/shadow

and also apparently, it's a problem with shadowJar itself https://github.com/johnrengelman/shadow/issues/713

Behind the scenes, Shadow creates a FatJar with all the things we may need in the future.

Note: **According to Serverless documentation you can use the command **serverless deploy -v. However, with Java-based-projects that’s not true because it needs to create a Fatjar with all the needed requirements (so the command will fail). By default, Serverless will set **shadow** as a dependency in the gradle file for those purposes. The deploy command will generate a build file called -all.jar that is the one that’s going to be uploaded to the AWS Lambda function.

The result .jar is going to submitted to Apache Spark cluster (e.g. spark-submit command). So, it should contain all runtime artefacts. Unfortunately, the standard Spring Boot packaging does not put the dependencies in the way Apache Spark expects it. So, we'll use shadow-jar Gradle plugin. Take a look at the example below.

I've writen many Kotlin+Gradle projects that produce jars without the shadow plugin. They're not fat, shaded, standalone executable jars though - is that what you need?