So I've been toying with this tool and think it's great! I'm going to use it to power a private internal repo at my job.
But one thing I'm a little worried about is sharing this tool with my co-workers - if they make a simple mistake, like not putting --preserve-versions in, or forgetting to specify a 'codename' like -c stretch or -c jessie or whatever - that they will stomp all over my very carefully constructed repository, which is set up just exactly how I like.
The workaround I'm probably going to use is to put some kind of 'wrapper' around the tool so they can only invoke it with my preferred settings. That's probably fine, I guess?
But what I think could be really neat is if we stored some kind of .config file in the base of the repo, that had certain settings in it that couldn't be overridden without some real effort.
Then my coworkers could upload packages like crazy and I wouldn't have to worry about them somehow blowing up our Packages list or whatever, or putting a bunch of crap where I don't want it. And, although it ends up only being a side effect, a nice feature here would be that subsequent invocations of the command-line tool wouldn't require as many required parameters - as they could get fetched from the 'config file' that lives on S3 instead.
So I've been toying with this tool and think it's great! I'm going to use it to power a private internal repo at my job.
But one thing I'm a little worried about is sharing this tool with my co-workers - if they make a simple mistake, like not putting
--preserve-versionsin, or forgetting to specify a 'codename' like-c stretchor-c jessieor whatever - that they will stomp all over my very carefully constructed repository, which is set up just exactly how I like.The workaround I'm probably going to use is to put some kind of 'wrapper' around the tool so they can only invoke it with my preferred settings. That's probably fine, I guess?
But what I think could be really neat is if we stored some kind of
.configfile in the base of the repo, that had certain settings in it that couldn't be overridden without some real effort.Then my coworkers could upload packages like crazy and I wouldn't have to worry about them somehow blowing up our
Packageslist or whatever, or putting a bunch of crap where I don't want it. And, although it ends up only being a side effect, a nice feature here would be that subsequent invocations of the command-line tool wouldn't require as many required parameters - as they could get fetched from the 'config file' that lives on S3 instead.