4 ms·

You've chosen a really bizarre way to package your software. I'm looking through your repo and can't see any code for your libraries. It seems like its somehow

You've chosen a really bizarre way to package your software. I'm looking through your repo and can't see any code for your libraries. It seems like its somehow part of the docker image? So then this is just a shim for a docker environment that contains the code? Normally people would use Github for a hosted repo and make their software available on Pypi. But deploying with a docker file is kind of opaque and sketchy. I would give better feedback but still no easy way to see the code? Unless you're trying to do it like this to have something like a closed-source version of your libraries... which would again be kind of a bizarre model to use with Python.

jimmyechan 3y ago
Yeah, the code is in a docker image, published on docker hub. It's prepackaged so it's easy to set up with docker-compose. The repo mostly has the docker files needed to self-host the dropbase worker and client. As you said, it's a bizarre, but not uncommon way to distribute. We're not technically open source at the moment, but considering evolving into source-available, and maybe eventually move up to an open source model. But we still have plenty to figure out. It's a bummer we can't get your feedback though, that's definitely a nice thing about open.
- Uptrenda 3y ago
  So does the docker file have something like python bytecode files in it or actual source? If it has source aren't you worried about people leaking it?
  - jimmyechan 3y ago
    It has actual source for the worker. We aren't worried about it being leaked because we are not particularly trying to hide it in the first place. We will probably make source available to paying customers on request if they want to verify that their sensitive data only moves between self-hosted worker and self-hosted client. The other reason is that internally we've always thought that we'd eventually gravitate to an open model when the time is right i.e. at least until after we've figured out the product.

jimmyechan 3y ago

Yeah, the code is in a docker image, published on docker hub. It's prepackaged so it's easy to set up with docker-compose. The repo mostly has the docker files needed to self-host the dropbase worker and client. As you said, it's a bizarre, but not uncommon way to distribute. We're not technically open source at the moment, but considering evolving into source-available, and maybe eventually move up to an open source model. But we still have plenty to figure out. It's a bummer we can't get your feedback though, that's definitely a nice thing about open.

Uptrenda 3y ago
So does the docker file have something like python bytecode files in it or actual source? If it has source aren't you worried about people leaking it?
- jimmyechan 3y ago
  It has actual source for the worker. We aren't worried about it being leaked because we are not particularly trying to hide it in the first place. We will probably make source available to paying customers on request if they want to verify that their sensitive data only moves between self-hosted worker and self-hosted client. The other reason is that internally we've always thought that we'd eventually gravitate to an open model when the time is right i.e. at least until after we've figured out the product.