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.

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

Added basic authentication option #407

Closed
wants to merge 1 commit into from

Conversation

tommoor
Copy link

@tommoor tommoor commented Aug 28, 2016

For those that would like to self publish their storybook to Heroku or a similar service but have some authentication. This adds simple --username and --password args to the start-storybook command.

@arunoda
Copy link
Member

arunoda commented Aug 29, 2016

Storybook is not suppose to run this way.
This is a dev server and it has no any production level optimizations.

I suggest you to do this outside of storybook. Export your storybook as a static site, then add basic auth when serving that.

@arunoda arunoda closed this Aug 29, 2016
@tommoor
Copy link
Author

tommoor commented Aug 29, 2016

That's a shame - no one's talking about production here, just making the
dev server accessible online for teammates to review.

On Sun, Aug 28, 2016 at 8:29 PM Arunoda Susiripala notifications@github.com
wrote:

Storybook is not suppose to run this way.
This is a dev server and it has no any production level optimizations.

I suggest you to do this outside of storybook. Export your storybook as a
static site, then add basic auth when serving that.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#407 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXP8ppOzhVJFTNz9BNQhazKZ8C9EJTzks5qklIygaJpZM4Ju1JY
.

@shilman shilman added the misc label May 27, 2017
@dusterherz
Copy link

We have exactly the same needs at our work. Please considerate to reopen this PR, this is more easy to deploy than exporting the site and do all the auth after that.

@Hypnosphi
Copy link
Member

Hypnosphi commented Oct 16, 2017

Do you really need webpack dev-server with hot module replacement on a deployed storybook? Otherwise, what's exactly wrong with just serving static bundle?

@dusterherz
Copy link

It's not really a problem to just use the static, like i said it is just much more easier to configure Heroku with only two variables and tell him to use the dev-server than it is to generate static files and then add a server with auth. This is more to make our life easier when reviewing a teammate PR that add a component via Heroku review apps. I am aware that this is not the first use of storybook and I understand this PR has been refused for this reason.

@Hypnosphi
Copy link
Member

Hypnosphi commented Oct 16, 2017

You may want to try this package: https://github.com/Alex-Werner/http-server-with-auth

Alternatively, you can just copypaste the logic from this PR into your node.js file that would be responsible for serving the static

@dusterherz
Copy link

dusterherz commented Oct 16, 2017

Thanks for your advice (btw, I love your hair !)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants