Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide instructions on changing apikey versus what setapikey does #25

Closed
pravincarvalho opened this issue Jan 15, 2018 · 5 comments
Closed

Provide instructions on changing apikey versus what setapikey does #25

pravincarvalho opened this issue Jan 15, 2018 · 5 comments
Assignees
@ferventcoder
Labels
enhancement
Milestone
0.2.3

Comments

@pravincarvalho
Copy link

version: 0.2.2
I've used the following command to set the api key on my chocolatey server. I've run this command from an administrative powershell on the same machine.

choco setapikey --source="http://<<myserver>>/chocolatey" --api-key=oYyDQXtsNQjPMUUUMtkE3YhJ

which returns

Updated ApiKey for http://<<my server>>/chocolatey

However, when I try pushing a package I get a 403 forbidden error and if I try pushing a package with the default "chocolateyrocks" API key, the package is uploaded successfully.
@ferventcoder
Copy link
Contributor

Hi @pravincarvalho choco setapikey is for you to set your LOCAL choco client to the existing API key on the server. To change the key on the server, you have to manually edit the web.config file.

Perhaps it would be good for us to draw that out in the instructions.

NOTE: If that was your actual apikey, you might change it.

@ferventcoder
Copy link
Contributor

@bcurran3 fyi

@ferventcoder ferventcoder changed the title setapikey does not seem to work Provide instructions on changing apikey versus what setapikey does Jan 15, 2018
@bcurran3
Copy link

Don't forget to put in the docs viewing Chocolatey Simple Server with Internet Explorer or Firefox versus Chrome. Set expectations and head off the support questions. :) (I'd love to find a Chrome "fix" to view the feed correctly - I'm sure there's an extension....)

@pravincarvalho
Copy link
Author

@ferventcoder Thanks for the explanation! On the landing page, you could just modify the line

You can set the ApiKey for this repository with 
choco.exe push [{package file}] --source http://<<my server>>/chocolatey [--api-key={apikey}]

to say something like

You can set the ApiKey for your choco client to connect to this repository with
choco.exe push [{package file}] --source http://<<my server>>/chocolatey [--api-key={apikey}]

and that should make it clear.

@ferventcoder ferventcoder mentioned this issue Feb 6, 2018
Closed
@ferventcoder ferventcoder added this to the 0.2.3 milestone Feb 11, 2018
@ferventcoder
Copy link
Contributor

This is completed for 0.2.3

@ferventcoder ferventcoder self-assigned this Feb 11, 2018
ferventcoder added a commit that referenced this issue Feb 11, 2018
@ferventcoder
(GH-25)(GH-26)(GH-27) doc enhancements
78d94bc 
- Clean up sections and separate them nicely
- Explain how to use install.ps1 to install Chocolatey internally
- Show how to add source with choco source command
- Links to push package docs
- Note how to manage install of Chocolatey from this repo with
different configuration management items and point to issues for
Ansible and Salt that don't support offline installation of Chocolatey
itself.
- Explain the api key and how to set it
- Explain basic authentication and how to enable it
- Add docs surrounding packages and how big they can be, timeouts
surrounding larger packages, how to delist/delete, and package version
immutability.
- Explain the package cache and what it means to clear it.
- Add docs for building packages and the best way to get started.
Explain why Package Builder is awesome.
- Explain the difference between caching and internalizing. Point to
Package Internalizer.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
enhancement
Projects
None yet
Milestone
0.2.3
Development

No branches or pull requests
3 participants
@ferventcoder @bcurran3 @pravincarvalho