Feature/vagrant for 20.04 #762
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
look reasoably safe, but untested
ideally we would upgrade to some later npm version, but lets do one thing at once
to prevent immediate crashes on startup
matkoniecz
force-pushed
the
feature/vagrant-for-20.04
branch
from
ec19486
to
4637113
Compare
This was referenced Jan 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is sadly incomplete but fixes several things that were bitrotten (18.04 vagrant was not running already).
Still, it continues not fully working.
But anyway, after discovering colouring-cities@de641c6 issue I am really considering Docker.