Topics created by certificatemanager_4002

Hi @certificatemanager_4002, I'm not sure I totally understand the question :) The ConnectionString property is marked as encrypted, which means that ProGet's Encryption Key will be used to store it to the database as encrypted, and obviously decrypt it. But this should happen automatic, when using the API or UI to save the settings. -- Dean

Hi @certificatemanager_4002 , This is really easy to do in ProGet and no need for a "scan". I can't even imagine how such a "scan" could work. Anyway, you just simply need to add a connector filter that prefixes your internal packages. For example, our filter for NuGet packages would look like Inedo* - which prevents any package named that coming through a connector. Check out this article to get some more details: https://blog.inedo.com/software-supply-chain-security/three-things Thanks, Steve

Hi @certificatemanager_4002 , ProGet is licensed per instance (i.e. installation), you will need a separate license if you wish to maintain a production and non-production instances of ProGet. See the official Licenses for Non-production / Testing Environments for more details. For things like a one-off, cloud-migration, using a Trial license (which you can get from My.Inedo.com) is fine. Thanks, Alana

Hi @certificatemanager_4002 , From the cybersecurity perspective, it's fine to leave it as root since the core process is run by the non-root user postgres inside of the container. You're never exposing a network service while the containerized process has root privileges. Here is more information on this if you're curious: https://stackoverflow.com/questions/73672857/how-to-run-postgres-in-docker-as-non-root-user As you can see in that link, it's technically possible to configure as non-root, but it requires more effort and doesn't really get you any benefit. As for load-testing and restarting, it really depends on the hardware and similar factors. Keep in mind that InedoDB is simply the postgresql container image with some minor configuration tweaks/changes. So any question you ask about InedoDB you can really ask about postgresql as well. As for using an external PostgreSQL server, the only information we have at this time is in the link I sent you before. You really need to be an expert on PostgreSQL if you wish to run your own server. Thanks, Alana

Hi @certificatemanager_4002 , Check out our Licenses for Non-production / Testing Environments for the full details. But if its a short-term migration testing scenario, then using an existing or trial key is fine. For a long-term environment, a separate license is required. -- Dean

hi @certificatemanager_4002 , The 500 is occurring on /health because licenseStatus=Error and the software is basically unusable until you correct the license issue. You would see a similar "blocking" error in the ProGet UI as well - so just check that, and once you correct the license error, the health check will return to normal.. Thanks, Alana

Hi @certificatemanager_4002 , I'm sorry but I'm not familiar enough with Kubernetes to help troubleshoot this issue. All that I recognize here is the upgradedb command, which is documented here: https://docs.inedo.com/docs/installation/linux/installation-upgrading-docker-containers#upgrading-the-database-only-optional If you run that command from the command-line (on either linux or windows), things will written to the console. I wish I could tell you why you aren't seeing the messages. Thanks, Alana

Thank you. Does it mean that I must stay with the SQL server version and do not migrate to the one with PostGres.