-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Development issue. #366
Comments
foreman_fog_proxmox 0.17.0 is only supported with latest foreman version. i.e., 3.13 and above due to Zeitwerk changes. So can you please upgrade to latest foreman or use 0.16.2 foreman_fog_proxmox version to make this work. |
Did you execute |
I did a rollback of the plugin version to 0.16.2 and now it works. I'll probably get back to you with more questions. Thanks a lot. |
As I wanted to participate in the development of the plugin, I set up a specific development platform based on Vagrant.
To do this, I followed the following documentation https://github.com/theforeman/foreman/blob/develop/developer_docs/foreman_dev_setup.asciidoc to install the development platform and then the instructions described in your README.
Architecture:
After installing the plugin (creating
Gemfile.local.rb
thenbundle install
), when I run the commandbundle exec rake db:migrate
I get the following error:
rake aborded!
LoadError: Unable to autoload constant ProxmoxVmHelper, expected /home/vagrant/plugins/foreman_fog_proxmox/app/helpers/proxmox_vm_helper.rb to define it.
I get the same error when I try to start Foreman.
bundle exec foreman start
I ended up thinking that this error was linked to a snake_case or CamelCase problem, but why this error from the plugin sources ?
I should point out that I'm taking advantage of this project to learn Rails and Ruby. I'm therefore a beginner in these technologies and it's likely that I may have missed a step.
Thanks in advance for any help you can give me.
The text was updated successfully, but these errors were encountered: