Thanks for replying. I see now.
Thought I was in a forum of advanced hydro-dynamic engineers for a second there.
Thanks for replying. I see now.
Thought I was in a forum of advanced hydro-dynamic engineers for a second there.
@tomasz - Do you think we should bring them back?
The last word of the comment is loss.
Are people saying "None" because the spout into 'cup 5' is a mil lower than the rim of 'cup 5'? If so, then "None" could make sense.
I'm curious what you mean by this.
It works perfectly - clean and convenient. Thank you for sharing.
The main 'mood fixes' for me are:
And to deal with the actual 'causes':
Something I notice... after doing those 'lists' and 'mood fixes'... the situation is usually not as 'hopeless' or 'complicated' as it seemed.
Feel free to share your lists/ideas (or feel free to message me if you'd rather discuss it in private). I will be honest and encouraging.
I guess that depends on how you define success:
Personally - I’d rather have a tight-knit community than a zillion spammers regurgitating low-effort posts (like many reddit subs).
The cool thing about success is - you get to decide what it means.
1 - I’ve completed your suggestions.
You are correct - I had forked the ‘Main’ branch, which runs a different js-client
than UI-16.7.
So I merged 16.7 into my fork... and everything WORKS.
Thank you - that was helpful.
[I also set up Drone. Yes, it builds very fast.]
**
2 - Perhaps “LEMMY_DATABASE_URL” shows an obsolete value in the config docs:
postgres://lemmy:pw@LEMMY_DB:5432/lemmy
postgres://lemmy:pw@POSTGRES:5432/lemmy
That 2nd string worked for me anyway - on an ansible install. (the former gives a 404 fetch error).
**
Thank you very much again.
Lemmy is running smooth and looking great.
I hope you are doing alright.
I forked the UI at 15.4, to build some new UI features.
Next I will manually add those features to this clean fork of Lemmy-UI 16.7 (so all code is up-to-date).
--
If I may ask, do you recognize what this issue might be?
These pages work:
--
However, I get a loading spinner and Uncaught TypeError: Cannot read properties of undefined (reading “____” )
on the following pages [in console]:
And if I do create a post [by using ‘default UI’, and then switching back to 'forked UI'], then Post-List pages also give that error:
--
So my question is:
Do you see a likely cause from that pattern?
(Perhaps a backend/database connection - an undefined string).
If you have an idea, I would love to know.
--
ENVIRONMENT:
Docker + NGINX logs seem to be clean.
I have not modified the ‘UI fork’ code.
I have not modified anything on the VPS - only added these Environment Variables in docker-compose.yml (in various combinations):
environment:
- LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
- LEMMY_UI_LEMMY_EXTERNAL_HOST=ggg.com
- LEMMY_UI_HTTPS=true
- LEMMY_UI_DISABLE_CSP=true
- LEMMY_UI_HOST=0.0.0.0:1234
--
Thank you for your time and work. Lemmy is awesome.
[I am learning about drone now.]
Thank you for the reply.
If I can eliminate QEMU, I’d love to (it’s slow).
Have you shared your workflow.yml anywhere? (for the lemmy-ui DockerHub image build)
**
This is my current workflow.yml (for Github Actions).
The reason I added QEMU was:
1 - Github Actions was only building the ‘forked-UI’ docker-image for AMD64.
2 - I then added buildx and specified a platform in the workflow:
- name: Buildx
uses: docker/setup-buildx-action@v1
- name: Build and push
uses: docker/build-push-action@v2
with:
context: .
platforms: linux/arm64/v8
Which failed with:
Error: buildx failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c
yarn install --pure-lockfile" did not complete successfully: exit code: 1
3 - I then added the QEMU step, and the build succeeded.
**
*Lemmy-Translations
I also had to add an "Update lemmy-translations" step:
- name: Update submodules
run: git submodule update --init --recursive
otherwise the build would fail with:
/usr/src/app/generate_translations.js:7
files.forEach(filename => {
^
TypeError: Cannot read properties of undefined (reading 'forEach')
at /usr/src/app/generate_translations.js:7:9
at FSReqCallback.oncomplete (node:fs:201:23)
After adding that “Update Submodules” step, the build succeeds.
Is there a better way to do it?
**
I am 100% open to any suggestions/critiques (and if your workflow.yml is public, I will study it and learn).
Hey I think that is a great idea. I agree that mental/spiritual freedom is reached through the breath.
That will be a great strategy and you can definitely help people who are ready to try it.
Yes, so we can talk to each other.