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

Don't copy problem resources #30

Open
ali-ramadhan opened this issue Jul 15, 2019 · 0 comments
Open

Don't copy problem resources #30

ali-ramadhan opened this issue Jul 15, 2019 · 0 comments

Comments

@ali-ramadhan
Copy link
Member

Right now the engine copies static and dynamic resources(?) which might be a bad idea if the resource files get large enough. Resources are also pushed into the LXD container.

We don't have any big files right now so it's not an issue but when we start dealing with big files, might be better if we don't copy files, and maybe even have the static files ready in the LXD container (lovelace-problems can be part of the LXD image).

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

No branches or pull requests

1 participant