Sender | Message | Time |
---|---|---|
24 Feb 2024 | ||
fishinthecalculator | somehow it didn't work, in
but right now I have to leave. I'll try again probably tomorrow thanks for your help | 19:21:33 |
Mayel | Oh just merged the paginator PR, you prob need `mix deps.update paginator` now | 19:22:37 |
Mayel | No hurry of course! | 19:23:02 |
fishinthecalculator |
| 19:23:59 |
fishinthecalculator | progress! | 19:24:05 |
fishinthecalculator | 👋 | 19:24:12 |
Mayel | Nice, have a good evening! | 19:24:43 |
2 Mar 2024 | ||
ivan | hi :) recently i've started playing with LiveDashboard tool to investigate the causes of bonfire being so slow... I have the gut feeling is not a matter of optimizing in lot of places, but that there may be few bottlenecks that slows the whole app (but it's really just a gut feeling and others may disagree) I've started reporting the finding here https://github.com/bonfire-networks/bonfire-app/issues/891 but not being a BEAM expert i'm not sure if those metrics are a strong indication or not really, any feedback would be very welcome :) | 16:05:44 |
terra set a profile picture. | 20:52:11 | |
5 Mar 2024 | ||
Jeff joined the room. | 05:14:58 | |
Jeff | Hi there! I'm walking through the Bonfire Setup Documentation and preparing an instance running on my local homelab, using the Docker B1 option. I'm filling out the configuration variables, and got to the S3 container config section, which states:
So of course I want to be difficult and use my own S3 vendor, not Scaleway. When I look at config/runtime.exs tho I'm not seeing any variables related to S3 storage? I see a bonfire_files.exs and when I open that, it says "See Bonfire.Files.RuntimeConfig for what env vars to set". But..I don't know where that is either. 😆 | 05:20:26 |
Mayel | Ah apologies the docs are out of date. Firstly the warning may no longer apply thanks to a recent refactor (though would be good to test that to be sure). Second, the upload settings are defined in https://github.com/bonfire-networks/bonfire_files/blob/main/lib%2Fruntime_config.ex#L26 | 08:03:18 |
Mayel | (we also now have the ability to copy files between storages, though still need to write some migration logic around that, I'll add to the backlog) | 08:06:12 |
Jeff | Thanks for the pointers! I'll get back to this after my work day. Looking forward to it. | 14:20:50 |
6 Mar 2024 | ||
tandy left the room. | 13:39:52 | |
9 Mar 2024 | ||
Jeff | I'm back again, causing trouble. After running "just config", I see the following message:
But I don't see that "just setup" command listed anywhere in the deploy docs. My assumption is: alter any ./env and ./config/* fields as needed, then run "just setup" after that point, then move on to "just rel-run"? (Going Docker Easy Mode, B1 option) | 17:22:15 |
Mayel | In reply to @box464:matrix.orgAh yeah that's a recent change. I think you can run just setup straight away and then edit the configs... | 17:35:24 |
Jeff | Ok getting farther along. I had already edited the configs, and then ran the just config afterwards. I saw a warning and then a couple of errors which I assume are associated.
| 17:44:08 |
Mayel | that's strange, what env file did you edit if that one doesn’t exist? | 18:06:05 |
Jeff | i updated the ./.env file - my mix_env variable it set to prod - and that's where I see the .env file with my changes as well. but for some reason it's looking for the config file in the dev folder and that's empty. I can switch the mix_env variable to dev and re-run the just config, see if it populates the dev folder with my updates? | 19:43:59 |
Jeff | * i updated the ./.env file - my mix_env variable is set to prod - and that's where I see the .env file with my changes as well. but for some reason it's looking for the config file in the dev folder and that's empty. I can switch the mix_env variable to dev and re-run the just config, see if it populates the dev folder with my updates? | 19:44:15 |
Jeff | * i updated the ./.env file - my mix_env variable is set to prod - and I see the .env file with my changes copied into the prod/.env file, too. but for some reason it's looking for the config file in the dev folder and that's empty. I can switch the mix_env variable to dev and re-run the just config, see if it populates the dev folder with my updates? | 19:44:51 |
Jeff | But also - the .env file doesn't have an "ELIXIR_DOCKER_IMAGE" variable there and I don't know what it should be. Is elixir a dependency I should install as a pre-requisite? | 19:56:40 |
Mayel | Oh I didn’t realise this was for prod, sorry! Then it shouldn’t be looking for a dev folder… | 20:00:56 |
Mayel | And with option B1 it shouldn’t be trying to install deps | 20:04:50 |
Mayel | Apologies, not many people have deployed using this method yet | 20:05:14 |
Jeff | I'm going to walk through the install one more time - I've got snapshots setup so it's easy to scrap and go back a few steps. | 20:05:40 |
Mayel | I think you can skip `just setup` in this case | 20:05:51 |
Mayel | Since that's for compiling | 20:06:17 |
Jeff | In reply to @mayel:matrix.org No worries at all I'm just playing around with it. I did want to mention something about the docs: I JUST noticed the pinned item at the top of this room about the location of docs. And it's a different URL / format than what I was initially following, which I got to from https://bonfirenetworks.org > https://bonfirenetworks.org/docs/deploy And then this chat has: https://doc.bonfiirenetworks.org Are they the same content, just deployed to different doc sites? They look fairly similar. | 20:06:45 |