please explain the meaning you give to "stable" branch. #211

New Issue

Closed

opened 2022-09-13 22:31:05 +00:00 by loweel · 6 comments

loweel commented

2022-09-13 22:31:05 +00:00

Today I was naively thinking that a new "stable" version was just working, since it's marked stable.

So I see that develop was merged into stable, and I just went for upgrade.

I did the update, recreate akkoma, and now I need to blank install everything asking the community to register again. The database is completely messed up, so I can't even save the users.

So my point is: what is the meaning of "stable" for you? Is it something I can trust, or I can only trust releases?

thanks.

Today I was naively thinking that a new "stable" version was just working, since it's marked stable. So I see that develop was merged into stable, and I just went for upgrade. I did the update, recreate akkoma, and now I need to blank install everything asking the community to register again. The database is completely messed up, so I can't even save the users. So my point is: what is the meaning of "stable" for you? Is it something I can trust, or I can only trust releases? thanks.

floatingghost commented

2022-09-13 23:35:54 +00:00

Owner

this is phrased needlessly aggressively - I must request that you communicate civilly

may I ask how you updated? typically you don't have to "recreate" anything

this is phrased needlessly aggressively - I must request that you communicate civilly may I ask how you updated? typically you don't have to "recreate" anything

👍 1

floatingghost commented

2022-09-19 17:29:03 +00:00

Owner

poking for comment, so this doesn't happen again

how did you update?

(will close in a few days if this stays silent)

poking for comment, so this doesn't happen again how did you update? (will close in a few days if this stays silent)

spla commented

2022-09-19 17:55:50 +00:00

Today I was naively thinking that a new "stable" version was just working, since it's marked stable.

So I see that develop was merged into stable, and I just went for upgrade.

I did the update, recreate akkoma, and now I need to blank install everything asking the community to register again. The database is completely messed up, so I can't even save the users.

So my point is: what is the meaning of "stable" for you? Is it something I can trust, or I can only trust releases?

thanks.

I'm running stable branch since several weeks ago, it's stable, with any issues at all.
What do you did to update it?

> Today I was naively thinking that a new "stable" version was just working, since it's marked stable. > > So I see that develop was merged into stable, and I just went for upgrade. > > I did the update, recreate akkoma, and now I need to blank install everything asking the community to register again. The database is completely messed up, so I can't even save the users. > > So my point is: what is the meaning of "stable" for you? Is it something I can trust, or I can only trust releases? > > thanks. I'm running stable branch since several weeks ago, it's stable, with any issues at all. What do you did to update it?

loweel commented

2022-09-27 14:55:53 +00:00

Author

After a few days of investigation, I just understand what happened.

I have two instances. One is at https://boseburo.ddns.net , for testing new software, and one at https://bbs.keinpfusch.net which I use also for other people.

The update went all ok when I did the first update in the test. But, in the second one, the configuration was on disk (the file config.exs) and not in database.

As a result of it, the new version did a migration which did not applied the new frontend download system. Apparently, the code has changed regard to the frontend settings.

Meaning, it was running headless and no way to install any frontend anymore. And the problem is, once it enters this situation, there is a little to do.

So my question is, again: i guess you didn't tested this detail of the config vs the database because it was just a "merge into stable", and not a real named release. And my question was very simple. Was not "aggressive", just clear.

After a few days of investigation, I just understand what happened. I have two instances. One is at https://boseburo.ddns.net , for testing new software, and one at https://bbs.keinpfusch.net which I use also for other people. The update went all ok when I did the first update in the test. But, in the second one, the configuration was on disk (the file config.exs) and not in database. As a result of it, the new version did a migration which did not applied the new frontend download system. Apparently, the code has changed regard to the frontend settings. Meaning, it was running headless and no way to install any frontend anymore. And the problem is, once it enters this situation, there is a little to do. So my question is, again: i guess you didn't tested this detail of the config vs the database because it was just a "merge into stable", and not a real named release. And my question was very simple. Was not "aggressive", just clear.

floatingghost commented

2022-09-27 15:26:28 +00:00

Owner

migrations do not apply frontend updates

frontend download tasks are documented at https://docs.akkoma.dev/stable/administration/CLI_tasks/frontend/

database v on disk does not change how config is applied

it sounds like you had incorrect config, closing as resolved

migrations do not apply frontend updates frontend download tasks are documented at https://docs.akkoma.dev/stable/administration/CLI_tasks/frontend/ database v on disk does not change how config is applied it sounds like you had incorrect config, closing as resolved

floatingghost closed this issue

2022-09-27 15:26:28 +00:00

loweel commented

2022-09-28 16:55:17 +00:00

Author

Actually the configuration of frontends part was correct, and it worked with the previous version.

I know the link you posted, and it worked perfectly on the instance which was configured from the database, but not in the one configured from file. Same software.

But I don't mind, close if you like. What's important is the lesson I learnt about all of this.

Actually the configuration of frontends part was correct, and it worked with the previous version. I know the link you posted, and it worked perfectly on the instance which was configured from the database, but not in the one configured from file. Same software. But I don't mind, close if you like. What's important is the lesson I learnt about all of this.

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#211

No description provided.