Thanks, @iso@lemy.lol.

Thanks for explaining that, @pe1uca@lemmy.pe1uca.dev

Thanks for the help, @pe1uca@lemmy.pe1uca.dev.

I do still have my old server (I’m posting this from it). The new Lemmy server is using a different domain.

Thanks for the assistance, @iso@lemy.lol.

My new server uses a new domain. I do still have the old data (in fact, the old server is still up - that’s where I’m posting this from).

I installed both Lemmy servers via Docker. It would be nice if I could rsync my account data (including post/comment history) from the old server to the new server, but I’m now wondering if my changing domains would make the old account not work at all in the new server.

I see the import/export settings in my new server (0.19.3) but not in my old server (0.18.3). But it sounds like exported account settings don’t include post/comment history. Thanks, though, @willya@lemmyf.uk.

Thanks for that info, @tobogganablaze@lemmus.org.

I don’t know if your problem is the same as mine was, but the symptom sounds the same.

The docker-compose.yaml file shown in the Forgejo documentation for docker installation shows this mount:

    volumes:
      - ./forgejo:/data

For me, Forgejo installed and created new resource files in /data and ignored the resource files gitea alread made.

I changed the volume to:

    volumes:
      - data:/var/lib/gitea

Forgejo then recognized the gitea resources.

Thanks for that info. I did combine an upgrade (1.20 to 1.21) with the migrations, but I guess I lucked into it working. My problem was that the container’s path to the migrated gitea volume was incorrect.

Can you see the data you copied inside the container?

That led me to my problem! I did have the volume mounted, but the container’s path was incorrect: Forgejo was recreating it’s resource files as a new install because where it was looking for them, they didn’t exist.

Thanks!

Both gitea and forgejo are using sqlite3. Gitea 1.20.0, Forgejo 1.21.

Can you share some of them so I might have an idea what to try to do differently?

Unfortunately that didn’t work for me.

That is what I did. And it didn’t work.

Thanks, I’ll try that.

You’re sharing your thoughts about the real life club online.

Thanks for the references, but at least one example from https://www.home-assistant.io/integrations/intent_script/ seems to be wrong/outdated.

From that page:

Local lists

Sometimes you don’t need a slot list available for all intents and sentences, so you can define one locally, making it usable only in the context of the intent data (like a collection of sentences) where it was defined. For example:

language: en
intents:
  AddListItem:
    data:
      - sentences:
          - add {item} to [my] shopping list
        lists:
          item:
            wildcard: true

This is the code in my conversations.yaml:

intents:
  HowManyDaysUntil:
    data:
      - sentences:
          - how many days until {countdownname}
        lists:
          countdownname:
            - "this"
            - "that"

Here are the only difference I see between my code and the example above:

• I don’t have language: en (but when I add it, I get Invalid config for 'conversation' at conversations.yaml, line 1: 'language' is an invalid option for 'conversation', check: conversation->language)
• The example uses a wildcard and I’m using strings (but I’m following their other examples to have a list of strings)

However, this yaml gets Invalid config for 'conversation' at conversations.yaml, line 9: value should be a string 'conversation->intents->HowManyDaysUntil->0', got None

Perhaps I can’t have intents in conversations.yaml? Or maybe not lists? I started this project by editing config/intents/sentences/en/_cmmon.yaml but that’s a bad idea because an update would wipe my customizations. What’s the appropriate place for me to add custom sentences/intents/responses/lists?

You’re welcome!

From what I understand, a timer’s duration is the amount of time the timer was set to run for when it was started - the total time, not the time remaining.

If you’re wanting to determine the time remaining in an active timer, you need something like:

{% set finish_time = state_attr('timer.timer_entity_id', 'finishes_at') %}
{{ '00:00' if finish_time == None else (as_datetime(finish_time) - now()).total_seconds() | timestamp_custom('%H:%M', false) }}

Or this version, which breaks hours and minutes into speakable parts:

{% set finish_time = state_attr('timer.timer_entity_id', 'finishes_at') %} 
{% set hours, minutes = ('00:00' if finish_time == None else (as_datetime(finish_time) - now()).total_seconds() | timestamp_custom('%H:%M', false)).split(':') | map('int') %} 
{{ '' if hours == 0 else hours ~ ' hour' if hours == 1 else hours ~ ' hours' }} {{ ' and ' if hours > 0 }} {{ minutes ~ ' minute' if minutes == 1 else minutes ~ ' minutes' }}     

I currently use Photo structure, which is good, but its not open source and the one guy behind it, Matthew, is quite slow with progress. He’s super friendly and helpful, and bug fixes are pretty quick. But feature additions are glacial.

I was considering switching to photoprism but was turned off by the attitude of some of the developers. The product looks prery good, though.

I’m pretty sure I’m going to switch to Immich, which is also really good.

A friend uses Piwigo which is decent and has good features, though I find it’s very ugly regardless which skin you use.