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

feature request: load web assets from offline #2608

Closed
nicks opened this issue Nov 27, 2019 · 7 comments · Fixed by #5622
Closed

feature request: load web assets from offline #2608

nicks opened this issue Nov 27, 2019 · 7 comments · Fixed by #5622
Labels
enhancement New feature or request

Comments

@nicks
Copy link
Member

nicks commented Nov 27, 2019

Currently, Tilt loads its web assets from a publicly readable google cloud storage bucket at
https://storage.googleapis.com/tilt-static-assets/

This is much easier for us to manage operationally. But it means that if you're offline, or have a firewall that's blocking this site for some reason, the Tilt web UI will fail to load.

One or two people in the #tilt channel have asked how hard it would be to make this work offline. I'm not totally sure, and haven't spent much time looking into using something like Packr to do this

@nicks nicks added the enhancement New feature or request label Nov 27, 2019
@nicks
Copy link
Member Author

nicks commented Nov 27, 2019

(Current workaround is to only use Tilt when online, and unblock the above bucket in your firewall)

@wu-victor
Copy link
Contributor

wu-victor commented May 11, 2020

A workaround is building and running Tilt from source, and setting web-mode=local to serve local assets from your local system. See https://github.com/windmilleng/tilt/blob/master/CONTRIBUTING.md#web-ui

@szucsitg
Copy link

We'd love this as well

@wu-victor
Copy link
Contributor

@szucsitg feel free to upvote (👍 ) the issue. We use to track interest.

@Tchoupinax
Copy link

Hello ✋,

I am also interested about this feature. :)

@nicks
Copy link
Member Author

nicks commented Jul 29, 2020

I think the Go team is working on a much more holistic solution to this problem golang/go#35950, so I'm eagerly watching what happens there

@samkon
Copy link

samkon commented Dec 2, 2020

It can be all about DNS configuration you're using as I use google dns. Reset your DNS configurations and try it again.

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

Successfully merging a pull request may close this issue.

6 participants
@nicks @samkon @Tchoupinax @wu-victor @szucsitg and others