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!

  • Change port of integrated ProGet server

    Support proget proget-installation
    4
    0 Votes
    4 Posts
    100 Views
    ?
    Sorry about that, I got a little confused with BuildMaster's configuration... there is no appSettings.config file for ProGet :-/ ProGet's website port is determined by arguments passed to the service. If you stop the ProGet service, run ProGet.Service.exe as administrator, and choose Uninstall, the service will be uninstalled. You can run it again and choose "Install" to add it back, then it will ask for the URL to reserve, and you can enter something like http://*:1000/ to reserve all hostnames on port 1000. Make sure to choose an identity that has access to the SQL Server database. If you chose Network Service as the account to use when you first installed, just leave that as the default option for the user account when prompted. If the service takes a while to start up (i.e. longer than 5 seconds), it probably means the user account assigned to run the service does not have access to the DB (it could take a minute or more to time out). Just reinstall the service in the same manner to host with a different user.
  • 0 Votes
    2 Posts
    7 Views
    ?
    Yes, just edit the connection string in both the web and services directory.
  • 0 Votes
    2 Posts
    29 Views
    ?
    The service does need to be running mainly to index packages. If you selected the IIS option during install, the web server in the service will not run. If you are switching from integrated web server to IIS, make sure to update the service's .exe arguments to exclude the /urls argument and then the web server component of the service will not run.
  • Proget in IIS fails

    Support proget proget-installation iis error
    4
    0 Votes
    4 Posts
    37 Views
    T
    Tod's answer gave me something to look for. The IIS 7.5 did not have ISAPI enabled so after doing that the proget site worked as a charm. Definitely something that is missing in the documentation! For further reference see below: To enable ISAPI in the IIS look here: http://www.iis.net/configreference/system.webserver/security/isapicgirestriction at the part Setup The <isapiCgiRestriction> collection is available only after you install the CGI or ISAPI Extensions modules on your IIS 7 server. You cannot install it independent of those features. WINDOWS SERVER 2008 OR WINDOWS SERVER 2008 R2 On the taskbar, click Start, point to Administrative Tools, and then click Server Manager. In the Server Manager hierarchy pane, expand Roles, and then click Web Server (IIS). In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services. On the Select Role Services page of the Add Role Services Wizard, select CGI or ISAPI Extensions. If the Add role services dialog appears, click Add Required Role Services. (This page appears only if you have not already installed any prerequisite role services on your server.) On the Select Role Services page, click Next. On the Confirm Installation Selections page, click Install. On the Results page, click Close. After doing that i restarted and did not have to any further setup. Loading the site just worked. Inedo should make it much clearer in the documentation that this must be installed in the IIS for proget to work. Just setting the App Pool to Classic is not enough. Thomas
  • 0 Votes
    1 Posts
    9 Views
    No one has replied
  • Manual installation of ProGet

    Support proget-installation proget
    2
    0 Votes
    2 Posts
    7 Views
    ?
    It is possible (and fairly easy), but we do not have instuctions just yet. Hopefully this response will be enough. It basically follows the same steps as the Manual BuildMaster Installation ( http://inedo.com/support/documentation/buildmaster/installation/manual ), just without the Extensions or Agents. The hardest part will be getting the artifacts, as we don't have those available for download yet. But it's not so bad. For the files (WebApp and Service), you can just directly copy out of an existing installation. Just make sure to edit the appropriate appsetting config files when moving to the new server. For the Database, you can restore a back-up of the existing installation. To upgrade, you can use 7-zip to open the installer, and then copy out bmdbupdate.exe and $_OUTDIR\OBJECTS\SqlScripts.sql. First run bmdbupdate.exe then the .sql scripts. We will definitely make manual install artifacts avaiable in the future (along with instructions), and we do support this scenario for Enterprise Customers. We'll even help with install through our Professional Services ( http://inedo.com/company/professional-services ). Hope this helps...