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

LEGACY appears, code cleaning, Dockerfile for backend updated #197

Merged
merged 3 commits into from
Oct 21, 2015

Conversation

feroda
Copy link
Contributor

@feroda feroda commented Oct 21, 2015

No description provided.

@warp10
Copy link
Contributor

warp10 commented Oct 21, 2015

Why did you remove apt in favor of apt-get? That's quite anti-historic

@feroda
Copy link
Contributor Author

feroda commented Oct 21, 2015

I did it because when the image is built I get some warnings about the non-interactive use of apt . Weird red docker warnings make me afraid...

It doesn't really matter to me which frontend use to the dpkg, tell me and I change it.

@warp10
Copy link
Contributor

warp10 commented Oct 21, 2015

Weird it doesn't show the same warnings with apt-get. In any case, better to keep up with apt, which is the bright future of dpkg frontends.

feroda added a commit that referenced this pull request Oct 21, 2015
LEGACY appears, code cleaning, Dockerfile for backend updated
@feroda feroda merged commit 992b727 into befair:master-dj17 Oct 21, 2015
* Dockerfile: improved static directory and bower install dependencies
* static/nui/scripts/: added some other js symlinks needed to make legacy working
@michelesr
Copy link
Contributor

The warnings are related to the fact that apt hasn't a stable cli yet, and should be used with caution in scripts.

WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.

But for simple commands (like apt install -y ...) this shouldn't be an issue

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

Successfully merging this pull request may close these issues.

3 participants