Want to contribute but Vagrantfile is not working/up to date about countly-server HOT 4 CLOSED

Hello,
This is the problem with contributions :D
Someone contributes something, like a Vagrant file, but no one maintains it later. We definitely don't support it internally.

From an OS perspective, we only support Ubuntu and Centos/RHEL.

For local development, I would suggest using Docker containers, but I am honestly not sure how it would work on Windows.
I know someone tried to run it on Mac M1 and had problems with bitnami images, so they needed to replace them with something more compatible.

from countly-server.

Would you be ok with having a discussion/call about this?
Then we can both see how we can help you and align together on the vision of the feature.

from countly-server.

Would you be ok with having a discussion/call about this? Then we can both see how we can help you and align together on the vision of the feature.

I thank you very much for the offer and agree that a call would be helpful. I therefore sent you an email to the address linked to your github profile

from countly-server.

Meanwhile, I've got news about the reason why the Vagrantfile did not work. I suppose this is very different on each operating system.
I am mainly in windows and the original Vagrantfile mounted all files from the github repository from the host system (so windows in my case) to the guest system. On this way, the permissions are not correctly set and it seems like some part of an automatic git download failed too, which was why it did not start.

For the Vagrantfile: Updating the OS to the current ubuntu and changing the automatic shell deployment to use your recommended self-install script wget -qO- https://c.ly/install | bash in the right directory of the guest system, it is now working. I attached the Vagrantfile which worked. There currently is a host volume mount within, but it is not required, just optional.

Regarding the normal install in ubuntu (tested in a Virtualbox Ubuntu22), we noticed that it is very important where a user starts the wget -qO- https://c.ly/install | bash command and with which user and which shell. In our environment, it only worked like this:

• In bash: sudo su -
• switch to the /opt directory (seems to be necessary for the script to work): cd /opt
• wget -qO- https://c.ly/install | bash

Simply using sudo instead of switching to the root bash did not work for us and it also failed when trying to execute the script in a directory other than /opt.

I hope this helps.

Best regards,
Tobi

Vagrantfile.zip

from countly-server.