Standard virtual marchine with generic setup

Installation
1

Hello Users,

Because the setup is not as easy as we think for everybody,
Would it help if we make a virtual machine with generic setup that anybody can download, and use on a computer, for a fast start with the software.

We can make a vmware virtual machine for esxi 6.5.0 (free) under ubuntu desktop (free) with the name « fablab » for all the setup, and anybody could use it on a computer with enouth ressources. Or in a cloud server online, in a datacenter.

What do you think about it, users ?

2 « J'aime »
2

Oh yes!

That would be awesome and very helpful for evaluating fab-manager in a « production » set up.

I like docker and I’m currently evaluating porting the default images that fab-manager needs to pull for the arm architecture.

In my case I’ll try to run all of our makerspace software in small and silent boxes, splitting one for the DB and another (or more) for the front-end apps.

3

I have provisioning scripts that install and configure the required software to work under a virtual machine with Vagrant and an Ubuntu image, mostly for testing and development (in an effort to deploy the manager over Heroku).

I could make a PR to include it on the repo as the changes don’t interfere with the manager source.

2 « J'aime »
4

@clemclem @funk I’ve extracted and set a PR with the configuration and instructions to set up an instance running within a virtual machine.

I hope that @Sylvain likes it and allows it into de codebase.

You can see it here: Pull Request 101

1 « J'aime »
5

@akaiiro thanks much man :slight_smile:

I’m about to start messing and testing with FabManager again, tomorrow

1 « J'aime »
6

Salut,
Il y a eu des avancées sur cette proposition ? Je suis bien intéressé et éventuellement de participer aux tests…

bonne journée !

7

Salut Clem clem,
Est-ce que tu as réussi à faire une machine virtuel ? Je suis bien intéressé car comme tu le dis, ce n’est pas simple à installer.

Bonne journée !

8

Hello,
I didn’t take the time to do it yet,
i have been busy to move my lab
from one location to another.

9

Salut @ths,
Depuis la version 2.6.4, une VM de test sur est déployable avec vagrant grâce à la contribution de @akaiiro.

10

Yes, merci. Mais Vagrant sur un serveur virtualisé … c’est pas top non ?
Je galère avec Docker sur une machine proxmox … du coup, j’essaie sur un ARM pour docker-compose galère avec Debian Stretch …
Peut-être que je devrais utiliser un ubuntu server sur le ARM ?

11

Comme dit ici, on a jamais essayé de lancer fab-manager sur du ARM … donc normal que tu galères :slight_smile:. Il est probable que certaines gems ruby doivent être recompilées pour cette architecture, voire sont incompatibles. À mon avis, tu vas devoir faire une installation manuelle (sans passer par docker) en suivant ces instructions pour voir si ça peut marcher. Attention c’est un peu plus long et compliqué qu’une installation avec docker-compose. N’hésite pas à partager avec nous les résultats de tes investigations

12

Ok, merci je vais effectivement approfondir ça. Je vous tiens au courant et je prends des notes en cas de réussite.

13

Bonjour,

J’ai suivi l’installation manuel qui s’est passé sans heurt. En revanche à la conclusion … pof :

root@fabmanager:~/fab-manager# foreman s -p 3000
20:16:55 web.1 | started with pid 21604
20:16:55 worker.1 | started with pid 21605
20:16:55 mail.1 | started with pid 21607
20:16:59 mail.1 | Starting MailCatcher
20:16:59 mail.1 | ==> smtp://127.0.0.1:1025
20:16:59 mail.1 | ==> http://127.0.0.1:1080
20:17:04 worker.1 | W, [2018-04-03T20:17:04.163503 #21605] WARN – : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
20:17:07 worker.1 | (): could not find expected ‹ : › while scanning a simple key at line 13 column 1
20:17:07 worker.1 | /usr/local/rvm/rubies/ruby-2.3.6/lib/ruby/2.3.0/psych.rb:379:in parse' 20:17:07 worker.1 | /usr/local/rvm/rubies/ruby-2.3.6/lib/ruby/2.3.0/psych.rb:379:in parse_stream’
20:17:07 worker.1 | /usr/local/rvm/rubies/ruby-2.3.6/lib/ruby/2.3.0/psych.rb:327:in parse' 20:17:07 worker.1 | /usr/local/rvm/rubies/ruby-2.3.6/lib/ruby/2.3.0/psych.rb:254:in load’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:60:in parse' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:56:in block in raw_configuration’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:56:in raw_configuration' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:64:in global_configuration’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:32:in configuration' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:42:in each’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/application.rb:36:in load' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro.rb:23:in load’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/figaro-1.1.0/lib/figaro/rails/railtie.rb:5:in block in <class:Railtie>' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/activesupport-4.2.10/lib/active_support/lazy_load_hooks.rb:36:in execute_hook’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/activesupport-4.2.10/lib/active_support/lazy_load_hooks.rb:45:in block in run_load_hooks' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/activesupport-4.2.10/lib/active_support/lazy_load_hooks.rb:44:in each’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/activesupport-4.2.10/lib/active_support/lazy_load_hooks.rb:44:in run_load_hooks' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/railties-4.2.10/lib/rails/application.rb:93:in inherited’
20:17:07 worker.1 | /root/fab-manager/config/application.rb:22:in <module:Fablab>' 20:17:07 worker.1 | /root/fab-manager/config/application.rb:21:in <top (required)>’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:236:in require' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:236:in boot_system’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/sidekiq-3.3.4/lib/sidekiq/cli.rb:50:in run' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/sidekiq-3.3.4/bin/sidekiq:8:in <top (required)>’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/bin/sidekiq:23:in load' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/bin/sidekiq:23:in ’
20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/bin/ruby_executable_hooks:15:in eval' 20:17:07 worker.1 | /usr/local/rvm/gems/ruby-2.3.6@fab-manager/bin/ruby_executable_hooks:15:in ’
20:17:07 worker.1 | exited with code 1
20:17:07 system | sending SIGTERM to all processes
20:17:07 mail.1 | exited with code 0
20:17:07 web.1 | W, [2018-04-03T20:17:04.508501 #21604] WARN – : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /usr/local/rvm/gems/ruby-2.3.6@fab-manager/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
20:17:07 web.1 | terminated by SIGTERM

Si vous avez une petite piste, je suis preneur. Merci :wink:

Bon soir !

14

Does this happen when running the 2.6.4 version with Vagrant?

15

Hello,

With 2.6.4 version