Dev Showing Production
Since 0.13.4 some things have been broken. I wanted to try the dev branch before posting an issue but for some reason it appears dev isn't working. Can someone see what I have done wrong?
Solution:Jump to solution
Hi, it is normal that it will show production there. It doesn't matter if it's the development version or not. The production build means, that it has been optimised for actual use.
11 Replies
Solution
Hi, it is normal that it will show production there. It doesn't matter if it's the development version or not. The production build means, that it has been optimised for actual use.
Also, can you maybe elaborate on "things have been broken"? Do you have other issues or problems?
Why would you label dev as production? The whole idea of having two different branches is they are different is it not?
As for things that are broken; the different time zone on the clock widget was not working (showed my current timezone) and one of the homarr icons disappeared
Both are production builds. Development is just more active but less stable.
Can you tell us your configuration regarding the clock widget?
About the icon: What icon disappear? When did it disappear?
The icon in the top left - next to the name. I don't remember if this was a config or not so was checking the settings first as well
@Tag you implemented the time zone feature. Can you look into it?
So the icon that disappeared was your page icon?
It fixed after switching to dev and updating my dev install
Looks like it. Hence 'some problems' instead of being specific as I didn't want to waste time if it was user error (ie I put a link there) or if it was a bug
Did it reappear now? Is it a custom icon that you mounted via Docker?
Nah it is still broken but it was a link to a URL with an expiry token so it stopped working so I will have to find the image and self host it
Ah okay, makes sense. Downloading and mounting it with Docker is probably the most reliable way 🙂
Timezones feature hasn't changed between 0.13.4 and dev. Actually nothing has changed except dns-hole and healthcheck. So either the problem isn't fixed but you got around, or it's user error.
If you have any feedback on how we could replicate the problem or maybe you know why you may have not done it right so I can improve it is welcome.