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

Using storybooks in another URL #3330

Closed
frntendev opened this issue Apr 1, 2018 · 4 comments
Closed

Using storybooks in another URL #3330

frntendev opened this issue Apr 1, 2018 · 4 comments

Comments

@frntendev
Copy link

Hello,

I have an existing project and I want to add storybook in the project with a separate URL. For example the website is test.com and we want to see storybook on test.com/storybook so we need to add router.use('/storybook', storyBook) in our server.js file.
Also I don't want to use start-storybook -p 9001 -c .storybook and we have only npm start script to running the project. Is there any way to do that?

@igor-dv
Copy link
Member

igor-dv commented Apr 2, 2018

Maybe I don't fully understand your question. Can't you use a static build of Storybook and point to the index.html from the router?

@danielduan
Copy link
Member

danielduan commented Apr 2, 2018

build the static version of storybook in a folder like /storybook-static, make that folder a public static folder in your web server, point your url to that folder. you can serve the static build just like any other html file.

sounds like you're using Heroku or some CloudFoundry based solution. you'll have to add the config in your server code, in your Express node app, or Python Flask, or whatever you're using.

@stale
Copy link

stale bot commented Apr 23, 2018

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Apr 23, 2018
@stale
Copy link

stale bot commented May 23, 2018

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!

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

No branches or pull requests

4 participants