4 ms·
This is actually the main use-case for this. At work we have machines in different environments, but they all can see the self-hosted gitlab (although not each
by bradwood 6y ago
This is actually the main use-case for this. At work we have machines in different environments, but they all can see the self-hosted gitlab (although not each other). This just makes it easier to get bits of config or scripts from one environment to another with not too much pain.
- specialist 6y agoI do like the auto expire feature idea. (h/t StavrosK, pastery.net) I skimmed your glsnip project and didn't spot that feature. I get that your team self hosts gitlab. Very clever. Nicely done. Pretty much every place I've ever worked has struggled with secure, ad hoc, short-lived file transfers, both large and tiny. (eg Someone in marketing needs a data dump that's too large to sneak thru as an attachment via corporate email.) "virtual sneaker net" Often, we give up and just pass around a thumb drive. Ridiculous.
- bradwood 6y agoI don't think Gitlab does auto expiring of snippets, but I was thinking of adding `glsnip purge` to wipe the "clipboard" -- I may yet add it. I also toyed with making some kind of a `clipit` style clipboard stack with pushing and popping and listing items on the clipboard and all that... I may add that too if there is interest...