Skip to content
This repository has been archived by the owner on Apr 16, 2019. It is now read-only.

Add support for server-baked apps #17

Open
bsatrom opened this issue Jul 8, 2013 · 3 comments
Open

Add support for server-baked apps #17

bsatrom opened this issue Jul 8, 2013 · 3 comments

Comments

@bsatrom
Copy link
Contributor

bsatrom commented Jul 8, 2013

Rather than opening the preview to a static html file, it would be nice for the bootstrapper to support server backends like node, rails or ASP.NET MVC. Probably the simplest way to do this would be to allow the user to set a URL for their project (eg. http://localhost:8081/home) though we could even add support for Node and have the user provide a custom command to use to start up the server.

What are your thoughts?

@mishoo
Copy link
Contributor

mishoo commented Jul 9, 2013

That's definitely something we should do. I have some ideas, will cook something up before the beta goes out.

mishoo added a commit that referenced this issue Jul 9, 2013
…custom server.

Rather than including scripts literally and updating the page on "build",
use a single <script> tag that targets the bootstrapper server (on
//localhost:7569/@load-assets/PROJ/PAGE).  This url generates code that
loads the assets, as well as the live preview code.  It will be replaced
with the actual assets on "bundle".

Ref. #17
@mishoo
Copy link
Contributor

mishoo commented Jul 9, 2013

So, this should actually work now, except that there's no place to specify the preview URL. I need to add a project config dialog I guess. For now, just enter the URL to your server in the preview window. All page assets should load correctly and live preview should still work, as long as the bootstrapper is running.

@bsatrom
Copy link
Contributor Author

bsatrom commented Jul 9, 2013

looks good!

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

No branches or pull requests

2 participants