lit

lit copied to clipboard

If there is a secondary upstream, it will be used for downloads and publishing of private modules, but the real upstream will still be used for publishing public packages and for searching.

Hello, I really like the premise of lit. A fair bit of the code I write and use is, however, private and lives on an company repository, not on github, and network access to external entities is strongly discouraged. How do you recommend dealing with that case? I tried pushing a lit project to the private repo and then writing a dependent package with:

package.lua:
    .... dependencies = { "git://code.company.com/project" }

But when I ran lit install it made a network request to wss://lit.luvit.io/ and the install failed.

Best wishes, Max

(Kudos for trying to come up with a better packaging system than luarocks, by the way! :-) I think the Lua ecosystem could benefit a lot from that. )

So the official way to do this is to deploy a caching proxy of the lit server. It's literally as simple as going to a server in your private network and running lit serve.

You then configure your local upstream to point to this server instead of the public one. Any modules published will go to the local server and any downloads will come from it first and it will proxy from the main server any reads it doesn't have cached locally.

I'd love feedback on this design, I don't think it's been used much yet.