Open joseivanlopez opened 7 months ago
Please assign me this issue @joseivanlopez
Hi @ShatilKhan,
Thanks a lot for jumping into the project. Appreciated.
Sure, you can go ahead with this issue if you want. Please, ask for help if you get stuck at any time.
Enjoy!
Hey @dgdavid apologies for the delay I tried running using these command
$ git clone https://github.com/openSUSE/agama
$ cd agama
$ ./setup.sh
Doesn't seem to work, I opened my localhost , but there was nothing It didn't show any error
Hi @ShatilKhan,
Where are you running the setup.sh
script? Asking because setup.sh
is expected to run only in openSUSE Tumbleweed systems, as @imobachgs replied in https://github.com/openSUSE/agama/discussions/876#discussioncomment-7597243
Let me quote a recent comment from @joseivanlopez that might help you
For running Agama you need to start both the Agama services (backend) and the web UI. Are you running the Agama services?
I would suggest to create a virtual machine and use it to run our live iso image.
Once the Agama live image is booted in your virtual machine, you can run the web UI from your git clone:
$ git clone https://github.com/openSUSE/agama $ cd agama/web $ npm install $ COCKPIT_TARGET=<virtual-machine-ip> npm run server
Then point your browser to https://localhost:8080/. Probably you will be requested to enter username/password. If so, use root/linux.
Please, try it and let me know if it works. We can try another approach if it does not work. Thanks!
As he said there, please try it and don't hesitate on asking us whatever you need for getting the development environment ready for start having fun.
Thanks @dgdavid , just found the comment
I'm running on windows (WSL2)
So I suppose I'm supposed to actually download the openSUSE Build Service right?
Can you suggest the right version to download?
Also would be great to have a setup guide to install the tumbleweed system on a drive other than C Drive, since my system drive is full
Hi @ShatilKhan,
In a nutshell, we can say that Agama is divided into two different parts: the front-end (a React application) and the back-end (a set of D-Bus services). Both parts use Cockpit's infrastructure for communication.
I guess you are interested in the front-end, right? In that case, you could use the approach proposed by @dgdavid and @joseivanlopez in this comment, and you would not need to perform a Tumbleweed installation at all.
So the idea is:
web
directory and run npm install
to install JavaScript dependencies.COCKPIT_TARGET=<virtual-machine-ip> npm run server
replacing virtual-machine-ip
with, well, your virtual machine IP.We will try to write a guide in the future to use Docker to run the Agama D-Bus services, but by now, live media is your best bet if you are not using Tumbleweed as your operating system.
Thanks!
PS: I am unsure whether this is a good first issue, given that you might need to register your system in order to give it a try. Anyway, the instructions to set up your development environment still apply.
Thanks @imobachgs! I'll follow the instructions & let you know
I've been trying to run agma through VMWare but it keeps getting stuck on the start screen
@ShatilKhan,
Sorry for the late answer. I overlooked your last comment until now.
Do you still having problems for running Agama?
Yes It would be great to get some help with setting the project up I am using VM Ware As you can see from the screenshot, the screen freezes when I try to start agma
Yes It would be great to get some help with setting the project up I am using VM Ware As you can see from the screenshot, the screen freezes when I try to start agma
It seems you are using VirtualBox, right? Anyway, could you please paste the link of the image you are trying to boot? Are you running VirtualBox from WSL or from Windows?
I'm running from Windows 10 (64 bit)
Given that the image matches your architecture, I expect it to boot correctly on VirtualBox. Do you know if a regular openSUSE Tumbleweed image works? Could you try with a newer image, please?
If a product was already registered and you try to select a new product, then a popup is shown indicating that the product must be deregistered first.
This popup could offer a button for deregistering the product and open the registration form.
Note that the deregistration could fail. In that case, the popup has to show the error instead of opening the registration form.