This way, we don't generate humongous unecessary source code dumps for packages that will never be viewed (I'm thinking of CI output here), while still maintaining a bare minimum for searching.
It should be that you can use the search page and find types or members, without every viewing the source pages, ie. it should be possible to get what you need from the search alone.. An "ah, that's the name I was looking for" result.. :)
I validated that an change to 20gb is working. The file was put fine.
Hi every body!
Is there any news about when does private feed branch release?
Is there anybody to answer me?!!
Hey, I haven’t had a chance to work on the private feed branch
It’s still something I’d like to do!
what's the best (free) solution to have a private feed? because it's very essential...
There are none as far as I’m aware
how about github package registry?
is that a good solution?
Ah it looks like GitHub’s package registry lets you do private feeds for free actually. I haven’t tried it myself, so I don’t know if it’s any good
If you try it, I’d love to hear what you think of it
I will try it and tell you about it...
thanks a lot for your help
Yup of course :smile:
I am trying to implement Baget at work, so far it works on our kubernetes cluster using PersistanVolumeClaim but for cost i would like to use GCS. I saw on your doc that it's possible, but i tried stuff and it doesn't work. First i don't see any use of the baget.env values in the container.
Is there something that catches the env values to write them up on appsettings.json? because nothing seems to moves even though the env values are correctly updated.
I've never used this myself, so please let me know if you run into issues
But yes, you can always use a proxy like NGINX
Can BaGet be hosted behind a nginx proxy? I tried a couple weeks ago and ran into the issue described here: loic-sharma/BaGet#276
Thanks. I'll give it a try now and will report. I guess Kestrel is a bit too complicated and I gonna use a Nginx-Proxy instead
Ok, I've BaGet running on port 80 and behind an Nginx-Proxy behind port 443. It seems that the content under /static wasn't generated. I guess the Docker image doesn't create them. I'm using loicsharma/baget:latest
Gonna test now, which stage in the Dockerfile of BaGet create the static files and why they aren't generated