Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Proget 25.x and Azure PostGres



  • I'm facing a lot of issues while setting up InedoDB. Could you explain what to do if I want to use Microsoft Azure PostgreSQL instead?


  • inedo-engineer

    Hi @certificatemanager_4002 ,

    InedoDB is relatively new, so we're still working through some of the setup and installation documentation. We recently published a new release with installer improvements that address some default configuration issues.

    Otherwise, here is the documentation we have on using an External PostgreSQL server:
    https://docs.inedo.com/docs/installation/postgresql#external-postgres

    Note that we don't recommend it unless you have PostgreSQL server expertise - especially when it comes to Azure PostgreSQL, since they make certain customizations to the engine that will be difficult to troubleshoot/diagnose if you're not familiar with them. In particular when it comes to resource constraints and limiting/throttling usage.

    So, unless you have that in-house expertise, we suggest InedoDB.

    Thanks,
    Alana



  • “Thank you for your answer. However, could you provide more information regarding the InedoDB Docker user settings?
    Do I need to run the container as root?
    For example:
    YAML
    securityContext:
    runAsUser: 0
    runAsGroup: 0
    allowPrivilegeEscalation: true
    readOnlyRootFilesystem: false
    Each time I try to setup other user the system regarding access right.
    Show more lines
    **Have you tested whether the InedoDB container can handle 600 requests per minute or more?

    What happens if the InedoDB container crashes?
    How long does it take to restart?”**

    Which kind of action must be node if I user external-postgres?
    Do you have scripts?
    Do you provide support?


  • inedo-engineer

    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


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation