Posts made by luke.duddridge_1525

Where has the feed APIKey gone?

We found this very useful for separation on team feeds in that they could be sure they were not affecting anyone else's feeds.

Product: ProGet
Version: 5.0.10

Hello Alana,

That does take you out of the flow a bit, as I assume that this would give them access to edit the "Manage Licences" page?

I think is a step in the right direction, but I would still think using the Manage Feed flag and adding that as a role to that which allows Assign Licence is a good option as well.

Thanks,

Luke

This is an issue we now face, our lead developers manage feeds, but need rights to assign licences. Configure Proget is a bit too much, so it would be ideal to have this covered under the manage feed as they can already add approved or rejected states to licences they want.

I am on 4.8.8

Thanks,

Luke

I was wondering what the licensing requirement might be for a DR setup, is there a licensing requirement?

Does this fit the HA, the replication or something else?

Product: ProGet
Version: 4.8.8

Hitting the same problem with v4.0.15.

@Hasse did you ever resolve this or just move onto a new feed provision?

Currently left at 3.6.1, which works out the domains correctly.

I have renamed the roles just incase, but as soon as I upgrade to 4 it appears I get knocked out of the necessary task groups.

Your user account does not have the Admin_ConfigureProGet task.

I also get the same message if I don't change the role names.

I have been having a battle with upgrading our 3.6.1 instance to 4.0.15.

The problem from previous questions is the major change from 3 to 4 using "Tasks" which means every account we create appears to fall out of the Admin group.

So I thought I'd do a minor upgrade, from 3.6.1 up to 3.8.6, I actually perform an upgrade to the database to 3.7.6 before going to 3.8.6.

I copied the web config to connect to the database the same way and we are using Windows Authentication so changed that in the authentication.

• I stop the app pool,
• update on the database steps,
• then I completely delete the full content in the web application and then copy the web app for 3.8.6, with my altered web config.
• I then start the app pool again.

The problem I am seeing is that I get taken to the log-in page, I did create a no LDAP login, but the admin account I created does not let me in.

If I try to putting in any url (luckily I did one that was invalid) I get the error at the top of the page saying:
Severe Error: There is a problem with the license key.

I need to get this working in a test environment before I can get signoff that the upgrade will not affect anything.

Product: ProGet
Version: 3.8.6

After upgrading to v4.0.9 I have lost admin rights on my account.

I can view the feeds with another account that does not have admin rights.

is there something I can run?

Product: ProGet
Version: 4.0.9

Hi,

I have had a version of the database for our live instance of proget moved to a development server, but I am trying to use the bmdbupdate to update the database, as the account I need to use to update the database does not allow interactive logins.

I was hoping for example of the simple script I can run with bmdbupdate.exe UPDATE /conn which would include the markup of a valid submission of the /conn option.

The attempts I have made so far came back saying:
"Only one command can be specified"

an example of what I have tried:
bmdbupdate UPDATE /conn=[Data Source=DB1;Initial Catalog=ProGet;Integrated Security=SSPI;User ID=Account;Password=Password;]

Product: ProGet
Version: 3.6.1

I have taken all the packages that had been installed locally in my npm-cache, this was a load of package.tgz files, which I managed to script so that called each file something unique, this saved me time and did a bulk upload of all the packages into npm.

So I can see a list of all the packages we use.

to test how things were looking I simply pointed our registry reference over to the proget site, and started the build.

the problem I get is the central respsitory has a json file at the root of the package but this appears to be missing.

for example:
http://registry.npmjs.org/ag-grid

returns a json file with versions installed on the local feed this returns a 404.

have I missed a setting or is this different in later versions? we are looking to upgrade to version 4 shortly.

Product: ProGet
Version: 3.6.1