Vagrant installation script is out of date #2343
Comments
|
It's hard because you've tried to use vagrant and that is not maintained at all and is well out of date. Just follow the instructions in INSTALL.md instead. |
|
@tomhughes could you please try to be a bit more welcoming when new developers try to get started with our project! Also, we agreed before that we will provide support to developers who try to get the codebase up and running, up to the point that the tests pass on their system (but excluding non-standard db configurations). You don't need to provide this support, I volunteered to do so and I'm still happy to do so. Feel free to tag such issues with the "support" tag and let other people deal with them. |
gravitystorm
added
the
support
|
Well there is no useful support to give here other than not to use the vagrant method - there is no support we can give which will make it work. Now a bug ticket asking for the Vagrantfile to be fixed would be reasonable except that we will fix it and it will just get broken again next week - while it is not being actively used or tested on a weekly basis it is just going to continuously bitrot. The same goes for the Dockerfile. |
This is simply not true. We can provide support by fixing the obvious problems with the vagrant setup scripts. If one person has reported them broken, I'm sure others have tried and given up without alerting us.
You could consider this as such a bug, since it's obvious to you and me what needs to be changed in the vagrant scripts to get it working again. But you just closed the ticket, and I'm glad that I spotted the notification and reopened it since it's an issue where something is broken and needs fixing.
It's not outwith the realms of the possible to deal with this, as I know you know. So please don't declare everything as hopeless. I'm no big fan of the vagrant scripts, but if it helps new developers get started then I'll put in the effort to make it work. But like I said before, if you don't want to do this stuff that's fine, just please leave the support issues alone for other people to deal with. |
|
@YuriiNskyi thanks for the bug report and sorry that you've been having these problems. As you might have gathered from the previous comments in this thread, the vagrant scripts are not yet part of our CI system, so when we make substantial changes to the setup or dependencies, they are sometimes broken without us noticing. The I don't know exactly why the libarchive errors are occuring, but I can investigate further for you in a few days. In the meantime I would guess that |
|
So I think we have different definitions of support which is leading to confusion. I view support as providing advice on how to fix something and anything which requires making a change to the repository as being a bug report. Unfortunately while that is generally possible for manual installations, by providing instructions on how to workaround anything that is missing from the instructions, it isn't generally possible for vagrant or docker because there is no way to manually intervene to workaround any errors. I was genuinely attempting to provide support here by advising not to use the vagrant method, which is why I closed it, but I should probably have turned the ticket into a bug report instead. |
|
The libarchive error will be because the vagrant script hasn't installed |
|
I've opened #2344 to discuss how we can better maintain vagrant and docker support. |
tomhughes
changed the title
|
Hopefully 4efe7cd will have fixed this although I don't have a working vagrant setup to test it at the moment. |
|
@tomhughes @gravitystorm First of all, I really appreciate your help! After executing
it's finally works while executing Honestly, I did setup with Vagrantfile half a year ago, so I thought that everything should works as usual today. But unfortunately, times have changed. It is absolutely normal that Vagrantfile doesn't have support, what is really confusing, is that I can't find any clear mention about that in INSTALL.md or VAGRANT.md. If I knew that Vagrantfile is not supported, I would not even try to use it! |
|
I'd be interested to know if a |
|
@tomhughes It works now, but unfortunately not perfect at all. After executing It is non-critical and after executing This is non-critical too and could be simply resolved with So yes, partially |
|
Ah yes that's a known issue... It shouldn't really be needed but sprockets doesn't support conditional dependencies :-( I think dc5cdeb should fix it. |
|
I also gave it a go, in case others are trying, I also edited the end of the provision.sh script to copy the storage config file (if it's needed) and use also use "bundle exec" to call the rake tasks Running the tests, there were errors related to
This was solved by changing the environment variable from "phantom" to "offscreen" in the application_system_testcase.rb
|
|
Yeah that's a result of the silly way Debian/Unbuntu build phantomjs, so that it requires a graphical display evening if running headless. |
I'm trying to run my own
openstreetmap-websiteonUbuntu 18.04 LTSsystem.Here are the commands to reproduce an issue:
A problem with
example.application.ymlfile occurs here - it is required while it is not provided.This is OK and file from here is perfectly valid.
Let's again try
vagrant up.Here's the new error:
I did nothing to activate rake 12.3.3 previously and I don't even bother what is it, but it is OK, we can successfully enter Vagrant virtual machine with the help of
vagrant sshcommand.Finally, we are executing
bundler exec rails serverusing SSH and get the following error:I have only two questions.
openstreetmap-website?The text was updated successfully, but these errors were encountered: