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

Figure out deploy process #6

Open
hawkw opened this issue Jul 15, 2015 · 10 comments
Open

Figure out deploy process #6

hawkw opened this issue Jul 15, 2015 · 10 comments

Comments

@hawkw
Copy link
Contributor

hawkw commented Jul 15, 2015

Things we will want to do before deploying frontend code to the main repo:

There's other stuff we'll want to do; this is just everything that immediately came to mind.

@redbassett
Copy link
Member

Mock APIs should match real APIs. Current versions are experimental demos. #7 would cancel this issue out anyway.

@hawkw
Copy link
Contributor Author

hawkw commented Jul 16, 2015

Not the whole thing, we would still need to rewrite the parts of the URLs pointing towards API Studio to point towards /?

@redbassett
Copy link
Member

?

@hawkw
Copy link
Contributor Author

hawkw commented Jul 16, 2015

Like, if we are requesting some data from http://playground.apistudio.io/try/0777f0be-3679-4a80-a445-52c7ce34f0c5/api/books/ or whatever, we would still need to remove the http://playground.apistudio.io/try/0777f0be-3679-4a80-a445-52c7ce34f0c5/ part so it just points to /api/books?

@redbassett
Copy link
Member

Still confused.

@hawkw
Copy link
Contributor Author

hawkw commented Jul 16, 2015

If we use the mock API routes in dev, they'll point at API Studio. We need to rewrite them to point at slash when we deploy into production. Am I just saying gibberish here?

@redbassett
Copy link
Member

The routes should have a root base. Yes. One that can be changed (or defined) in one location.

@hawkw
Copy link
Contributor Author

hawkw commented Jul 16, 2015

Yes. That is what I am saying.

@redbassett
Copy link
Member

👍

@hawkw
Copy link
Contributor Author

hawkw commented Jul 16, 2015

So I have been trying to add a gulp vulcanize task, but I cannot seem to get it to work. Shall I push my attempt to a new branch so that somebody else can hack on it?

EDIT: okay, see #15

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

2 participants