27 Nov 2024 |
Christophe Michel | Ok? Where can the project development be followed? | 08:36:42 |
ivan | In reply to @n816:matrix.org Ok? Where can the project development be followed? probably https://github.com/bonfire-networks is the best place to see current development | 08:37:20 |
Christophe Michel | Openscience.network gives badgateway error | 08:38:48 |
Christophe Michel | Download 1000014617.jpg | 08:39:46 |
ivan | In reply to @n816:matrix.org sent an image. that instance is a test server for experimenting new development with a network of scientists, it's not meant to be a production or reliable instance, once we'll have new features focused on open science it will be up and running again, but as said, we're now focusing our energy and time on releasing the basic bonfire 1.0 | 08:43:24 |
| circlebuilder changed their display name from circlebuilder to circlebuilder (@smallcircles@social.coop). | 13:32:53 |
fishinthecalculator | https://lobste.rs/s/zv4ekm/is_there_good_open_source_combined_crm_cms
I read of this and thought of you guys <3
| 16:54:35 |
ivan | Yeah those are indeed use cases we would love to work with | 17:49:54 |
30 Nov 2024 |
| @emlabee:matrix.org joined the room. | 15:49:11 |
3 Dec 2024 |
| Kinetix joined the room. | 20:02:46 |
Kinetix | Howdy all | 20:03:55 |
Kinetix | I went looking for issues relating to initial build/setup and didn't see anything interesting on this. I'm following https://bonfirenetworks.org/docs/deploy/#bare-metal and further hints at https://box464.com/posts/bonfire-setup-guide/ ... after running 'just config', I'm told to run 'just setup-dev' and seems to get to a point where it runs beam.smp for a loooong time. (30+mins of CPU time counted so far). | 20:06:30 |
Kinetix | Does it ever complete? | 20:06:37 |
Kinetix | It's forked off a couple of inet_gethost processes that seem to be doing nothing | 20:09:20 |
Kinetix | It seems to be doing 100% cpu on bonfire.extension.copy_migrations | 20:31:10 |
Kinetix | 12:42:50.039 [debug] Did not find module to use: Elixir.Bonfire.UI.Common.Web.Native - issue? | 20:44:50 |
4 Dec 2024 |
Kinetix | OK, would love to be able to help sort out what could be going weird with the compile in the bare metal setup... I can't seem to get a dev or prod path to get going, always get to ongoing 100% CPU at some point in the 'just setup-dev' or 'just setup-prod' sequence | 06:08:35 |
hxgdzyuyi | Download image.png | 06:10:32 |
hxgdzyuyi | running the app link is broken | 06:10:33 |
ivan | better to include these in .env:
WITH_LV_NATIVE=0 WITH_IMAGE_VIX=1 ENABLE_AI=0
| 08:58:36 |
ivan | * better to include these in .env:
WITH_LV_NATIVE=0 WITH_IMAGE_VIX=1 ENABLE_AI=0
(they should likely be the default values)
| 08:58:48 |
Kinetix | Unfortunately the build still winds up in it's loop | 16:16:51 |
Kinetix | My .env file being used: https://nc.isurf.ca/s/LxKSDRRdxyPG3E7 | 17:14:29 |
Kinetix | The 'just config' and 'just setup-dev' output: https://nc.isurf.ca/s/S47oHYJTCWxQwQY | 17:15:15 |
Kinetix | I'm using Elixir 1.17.2 (compiled with Erlang/OTP 26) btw | 17:17:22 |
Kinetix | It seems to be the point when 'mix bonfire.extension.copy_migrations --force' is run where it winds up sitting and looping | 17:46:17 |
Mayel | In reply to @kinetix:tchncs.de I went looking for issues relating to initial build/setup and didn't see anything interesting on this. I'm following https://bonfirenetworks.org/docs/deploy/#bare-metal and further hints at https://box464.com/posts/bonfire-setup-guide/ ... after running 'just config', I'm told to run 'just setup-dev' and seems to get to a point where it runs beam.smp for a loooong time. (30+mins of CPU time counted so far). Are you doing a prod deploy? Because setup-dev is a command for dev setup | 17:54:50 |
Mayel | BTW can we move this to https://matrix.to/#/%23bonfire-tech:matrix.org | 17:59:50 |
Mayel | (seems the issue is happening when compiling the bonfire_ui_common extension, so not directly related to copy_migrations, it’s just a mix task so requires compiling the app before running) | 18:14:58 |
Mayel | (I was planning to make that into an escript instead to avoid that requirement, but then the issue might just appear later in the setup process) | 18:20:44 |