Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 04 21:24
    crajah opened #65
  • Feb 04 2021 16:35
    jjmalina opened #64
  • Jan 29 2020 19:15
    pjfanning commented #58
  • Jan 29 2020 17:50
    franchev commented #58
  • Jan 23 2020 22:22
    geraldstanje commented #63
  • Jan 23 2020 15:37
    geraldstanje commented #63
  • Jan 23 2020 15:35
    geraldstanje commented #63
  • Jan 23 2020 15:08
    montpetitg commented #63
  • Jan 23 2020 15:07
    montpetitg commented #63
  • Jan 23 2020 05:22
    geraldstanje commented #63
  • Jan 23 2020 05:22
    geraldstanje commented #63
  • Jan 23 2020 05:21
    geraldstanje commented #63
  • Jan 17 2020 18:57
    montpetitg commented #63
  • Jan 17 2020 18:56
    montpetitg commented #63
  • Jan 02 2020 14:25
    wiktorolko commented #63
  • Dec 21 2019 14:41
    maziyarpanahi commented #63
  • Nov 20 2019 22:05
    tpiron commented #63
  • Nov 19 2019 17:07
    jjmalina opened #63
  • Sep 06 2019 02:35
    kimxogus opened #62
  • May 13 2019 11:38
    schneist commented #58
Eduardo Pareja Tobes
@eparejatobes
re encryption, server-side encryption should be almost trivial to implement
client-side maybe a bit more tricky, but doable I think
Salman Ahmed
@debugging
sbt dist is a playframework task I am guessing. Actually come to think of it I would probably want a custom task to push to s3. So my build server can first compile, then run the tests, if it passes, run sbt dist, and then sbt publishS3 or something. The sbt dist creates a .zip file in /target/universal/app-name.zip
I'm looking at the README, I don't get how to setup to push a file to S3, or is that not really in scope for this plugin?
Eduardo Pareja Tobes
@eparejatobes
@debugging I'd look at the sbt docs for artifacts; I think you can include basically anything as an artifact and it will get pushed along with the jars
Eduardo Pareja Tobes
@eparejatobes
@laughedelic correct me if I'm wrong but once you define an artifact and include it in publish it will get pushed to S3
?
Alexey Alekhin
@laughedelic
hi @debugging!
@eparejatobes, you’re right. I think this page of sbt docs is relevant: http://www.scala-sbt.org/0.13/docs/Artifacts.html#Artifacts
I think the links referrenced by @eparejatobes can give you an idea how to configure this
then what is left, is to set up credentials for publishing to S3 and set publishTo as it’s written in the plugin’s readme: https://github.com/ohnosequences/sbt-s3-resolver#publishing
By the way, we’re going to release new version this week :wink:
David Roon
@adridadou
Hi everyone, I am trying to deploy my artifact to my S3 bucket but when I load my project I get the error message "Reference to undefined settings" s3resolver
I am using scala 2.11.6 with version 0.12.0
does this plugin work with scala 2.11 ?
Eduardo Pareja Tobes
@eparejatobes
@cubefriendly SBT 0.12?
David Roon
@adridadou
sbt 0.13.7
Alexey Alekhin
@laughedelic
hi @cubefriendly. could you show us your project/plugins.sbt file and build.sbt?
Matthew Stafford
@m-stafford
Hey gang, quick question. I'm seeing the same problem as @cubefriendly with the same sbt version. Does sbt-s3-resolver require explicit enabling in the build.sbt?
Alexey Alekhin
@laughedelic
ah! yes
this: S3Resolver.defaults
sorry, I just updated readme for the upcoming version 0.13.0, but it's not released yet
Matthew Stafford
@m-stafford
Ahhh, gotcha!
Thought it might have been something like that. Thanks!
Alexey Alekhin
@laughedelic
:+1:
Dean Chen
@deanchen
is there a way to use BasicAWSCredentials with the resolver? I'd like to check in my aws creds in to my private repo
Alexey Alekhin
@laughedelic
Hi @deanchen! I don't see an obvios standard way to get a credentials provider from the basic credentials, but it's easy to achieve by just implementing it's interface:
import com.amazonaws.auth._

s3credentials :=  
  new AWSCredentialsProvider {
    def getCredentials(): AWSCredentials = new BasicAWSCredentials("bar", "buh")
    def refresh(): Unit = {}
  }
Dean Chen
@deanchen
ah ok, that's perfect, thanks!
Alexey Alekhin
@laughedelic
:wink: :+1:
Ryan Means
@rmmeans
I hate having to bring up topics like this, but why the license choice for this repo? I totally get it for your other projects as it keeps people from profiting from your work and selling it as their own - but this project's whole point is to integrate it into likely closed source repo's (it if was open source, I wouldn't be publishing to S3, I'd just go to maven central, etc!) My concern is that in a legal battle, one might argue that my private project because it's using this project in its build.sbt file must now also be fully open source? I know the license issue is one of the big reasons the frugal mechanic project got started, but this project seems to be much more maintained and active, and I'd much rather use and contribute to it. Just wish it had a different license? I know y'all probably wont' change it, just curious the history behind the choice for this project?
Eduardo Pareja Tobes
@eparejatobes
hey @rmmeans
no problem with the topic
so why AGPLv3
is just a matter of simplicity
we're fine with anyone selling whatever
as long as it's open too :)
anyway
for private projects
in a lot of cases AGPLv3 is not a big issue
the requirement is over users of your app
so for something internal
Ryan Means
@rmmeans
Yeah, I'm specifically bringing up private projects here where the project might be for some API for our business that customers hit. All the other licenses used by our API allow us to keep the project private and not share our API source to the world, but that last step in our build process of publishing this thing to a private s3 maven repo that now forces me to open source my whole API is a little disappointing because using your s3-resolver is just part of the process for the build management - I wasn't profiting off of the project for my API itself. So it's not that I really have a problem with y'all using APGLv3 for all of your other stuff, because that makes sense based on your business goals for your other intellectual work, but for a build process tool, it just kind of bugs me :smile: given that your work didn't assist in me in creating the intellectual work of what I'm trying to keep private, it only assisted in the process part of efficiently storing or retrieving my compiled work. For now, I've just being using the other library from frugal mechanic, but part of my developer soul is bleeding knowing there is a better project out there, but I can't use it :smile:
Eduardo Pareja Tobes
@eparejatobes
@rmmeans yep I understand. It's just that we decided to keep everything AGPLv3; dealing with different licenses, compatibility, is this linking or not, etc takes a significant amount of time that we think it better spent anywhere else :)
Eduardo Pareja Tobes
@eparejatobes
Anyway, if there'd be someone else maintaining this
we could maybe move it to the sbt org
relicense it etc
that could be an option
Ryan Means
@rmmeans
now I totally get that! In fact, I figured that's what it was :smile: Be awesome to get some wider community effort behind it and move it over to the sbt org, etc. Anyways, thanks for the good conversation. I'll be continuing to watch the project over time. Good work!