1.1.116 #2637

Closed
opened 2022-09-09 23:34:50 +00:00 by AliasAlreadyTaken · 17 comments
  • Rename the bailiff priv to "command_stream"
- Rename the bailiff priv to "command_stream"
AliasAlreadyTaken added the
1. kind/other
label 2022-09-09 23:41:17 +00:00
AliasAlreadyTaken added the
2. prio/critical
label 2022-09-09 23:54:40 +00:00
Author
Owner

Attention: 3d_armor was refactored, the armours are now independent mods. We need to enable all of those mods in world.mt and probably update dependencies

Attention: 3d_armor was refactored, the armours are now independent mods. We need to enable all of those mods in world.mt and probably update dependencies
AliasAlreadyTaken added this to the 1.1.116 milestone 2022-09-10 00:03:15 +00:00
Member

hm. i need to review what changes were made, this sounds like they did at least some of the things i wanted to do w/ 3d_armor

hm. i need to review what changes were made, this sounds like they did at least some of the things i wanted to do w/ 3d_armor
flux added this to the flux's TODO list project 2022-09-11 00:29:10 +00:00
flux added the
2. prio/interesting
label 2022-09-11 00:29:17 +00:00
Member

(adding this to my todo list just as a reminder to review the update)

(adding this to my todo list just as a reminder to review the update)
flux removed this from the flux's TODO list project 2022-09-11 18:34:21 +00:00
Member

reviewed, not particularly interesting. putting the actual armors into a separate mod from the API is reasonable, but there's no reason to add a separate "mod" for every armor... oh well.

not sure that enabling the armor mods in world.mt is enough, you might need to create an armor.conf file in the world root that defines the materials used in crafting them.

reviewed, not particularly interesting. putting the actual armors into a separate mod from the API is reasonable, but there's no reason to add a separate "mod" for every armor... oh well. not sure that enabling the armor mods in `world.mt` is enough, you might need to create an `armor.conf` file in the world root that defines the materials used in crafting them.
flux removed the
2. prio/interesting
label 2022-09-11 18:47:59 +00:00
Author
Owner
UPDATE user_privileges SET privilege='command_stream' WHERE privilege='bailiff'
``` UPDATE user_privileges SET privilege='command_stream' WHERE privilege='bailiff' ```
Author
Owner

Switch from tcp sockets to unix sockets. Example in testserver world.mt

Switch from tcp sockets to unix sockets. Example in testserver world.mt
Author
Owner

Just in case there's no good option to do it before the next restart: Import #2803

Just in case there's no good option to do it before the next restart: Import #2803
Author
Owner

Switch modstorage from file to sqlite:

2022-10-20 15:58:28: WARNING[Main]: Switching to SQLite3 is advised, please read http://wiki.minetest.net/Database_backends.

https://wiki.minetest.net/Database_backends#Mod_Storage_backend says

minetestserver --migrate-mod-storage <name of new backend> --world <path to your world directory>

There is only ONE possible backend to migrate to. Would it have been so hard to give a reasonable example in that fabulous wiki??? Now I can only guess or make experiments. Is it "sqlite"? Or maybe "sqlite3"? Or "SQLite3" ???

minetestserver --migrate-mod-storage sqlite3 --world /home/mt/5.6.1/Minetest_test/worlds/Minetest_test

=>

minetestserver --migrate-mod-storage <name of new backend> --world <path to your world directory>

Same goes for the setting in world.mt, should this be sqlite, sqlite3 or SQLite3?

mod_storage_backend = sqlite3

So, the right thing to do is NOT edit world.mt manually, but simply call

minetestserver --migrate-mod-storage sqlite3 --world /home/mt/5.6.1/Minetest_live/worlds/Minetest_live
Switch modstorage from file to sqlite: 2022-10-20 15:58:28: WARNING[Main]: Switching to SQLite3 is advised, please read http://wiki.minetest.net/Database_backends. https://wiki.minetest.net/Database_backends#Mod_Storage_backend says ``` minetestserver --migrate-mod-storage <name of new backend> --world <path to your world directory> ``` There is only ONE possible backend to migrate to. Would it have been so hard to give a reasonable example in that fabulous wiki??? Now I can only guess or make experiments. Is it "sqlite"? Or maybe "sqlite3"? Or "SQLite3" ??? ``` minetestserver --migrate-mod-storage sqlite3 --world /home/mt/5.6.1/Minetest_test/worlds/Minetest_test ``` => ``` minetestserver --migrate-mod-storage <name of new backend> --world <path to your world directory> ``` Same goes for the setting in world.mt, should this be sqlite, sqlite3 or SQLite3? ``` mod_storage_backend = sqlite3 ``` So, the right thing to do is NOT edit world.mt manually, but simply call ``` minetestserver --migrate-mod-storage sqlite3 --world /home/mt/5.6.1/Minetest_live/worlds/Minetest_live ```

There is only ONE possible backend to migrate to. Would it have been so hard to give a reasonable example in that fabulous wiki??? Now I can only guess or make experiments. Is it "sqlite"? Or maybe "sqlite3"? Or "SQLite3" ???

based on https://forum.minetest.net/viewtopic.php?p=408010#p408010
it should be "sqlite3"

> There is only ONE possible backend to migrate to. Would it have been so hard to give a reasonable example in that fabulous wiki??? Now I can only guess or make experiments. Is it "sqlite"? Or maybe "sqlite3"? Or "SQLite3" ??? based on https://forum.minetest.net/viewtopic.php?p=408010#p408010 it should be "sqlite3"
Author
Owner
  • petz
  • plantlife
  • pipeworks
  • speed up serverstart meseportals
  • rotate logfiles
  • backup
  • switch from postgres 14 to postgres 15
  • #2281
* [x] petz * [x] plantlife * [x] pipeworks * [x] speed up serverstart meseportals * [x] rotate logfiles * [x] backup * [ ] switch from postgres 14 to postgres 15 * [x] #2281
Member

not sure it's possible to do this easily, but if possible, could we keep the rollback logs until sometime after 1.1.116? there's still some stuff marsey seether griefed that i want to try to roll back w/ my custom command from the debuggery mod.

not sure it's possible to do this easily, but if possible, could we keep the rollback logs until sometime after 1.1.116? there's still some stuff marsey seether griefed that i want to try to roll back w/ my custom command from the debuggery mod.
Author
Owner

For context: Rollback database is 64 GB by now, in contrast to 105 GB of the main database. That's about two to three month of operation.

Rollbacks are stored in an sqlite database, no chance of concurrent access while the server is running.

I don't remove the rollback database too often, usually only during engine migrations.

However I'd like to have a feature in MT that let's me configure how long rollback entries are to be kept. Like "Cull all entries older than 3 Month" or so. For now, we can still do that when the server is not running by firing some SQL towards the rollback sqlite.

Regarding what MarseySeether did: We should add the debuggery mod until cleanup is done?

For context: Rollback database is 64 GB by now, in contrast to 105 GB of the main database. That's about two to three month of operation. Rollbacks are stored in an sqlite database, no chance of concurrent access while the server is running. I don't remove the rollback database too often, usually only during engine migrations. However I'd like to have a feature in MT that let's me configure how long rollback entries are to be kept. Like "Cull all entries older than 3 Month" or so. For now, we can still do that when the server is not running by firing some SQL towards the rollback sqlite. Regarding what MarseySeether did: We should add the debuggery mod until cleanup is done?
Member

However I'd like to have a feature in MT that let's me configure how long rollback entries are to be kept. Like "Cull all entries older than 3 Month" or so.

i would love that too, but no-one has done the work to "abstract" the rollback backend so that it could easily be ported to postgres. currently, it'd be a lot of work, i don't even see an open issue about it.

Regarding what MarseySeether did: We should add the debuggery mod until cleanup is done?

i don't understand?

> However I'd like to have a feature in MT that let's me configure how long rollback entries are to be kept. Like "Cull all entries older than 3 Month" or so. i would love that too, but no-one has done the work to "abstract" the rollback backend so that it could easily be ported to postgres. currently, it'd be a lot of work, i don't even see an open issue about it. > Regarding what MarseySeether did: We should add the debuggery mod until cleanup is done? i don't understand?
Author
Owner

Move all file regarding meseportals to the folder "meseportals"

Move all file regarding meseportals to the folder "meseportals"
Author
Owner

Include somehow the watchtower functionality Ravise made: https://gitea.your-land.de/Ravise/watchtower

Another licensing confusion: Is BSD-3 compatible with MIT? Ravise especially stated he doesn't like MIT license in the commit messages. This website says it's more or less the same, but somehow one cannot be converted into the other: https://fossa.com/blog/open-source-software-licenses-101-bsd-3-clause-license/

Include somehow the watchtower functionality Ravise made: https://gitea.your-land.de/Ravise/watchtower Another licensing confusion: Is BSD-3 compatible with MIT? Ravise especially stated he doesn't like MIT license in the commit messages. This website says it's more or less the same, but somehow one cannot be converted into the other: https://fossa.com/blog/open-source-software-licenses-101-bsd-3-clause-license/
Author
Owner

#3013 depdendency circle

#3013 depdendency circle
Author
Owner

Switch to postgres 15 and tower-mod postponed, so we can close this.

Switch to postgres 15 and tower-mod postponed, so we can close this.
AliasAlreadyTaken added the
5. result/fixed
label 2023-01-11 17:00:32 +00:00
Sign in to join this conversation.
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: your-land/bugtracker#2637
No description provided.