Check status on the separated databases #825

New issue

Closed

opened 2026-05-07 19:36:53 +00:00 by a24sakma · 4 comments

a24sakma commented

2026-05-07 19:36:53 +00:00

Collaborator

There has been a request from Andras "The sensors should have their own databases to store earlier collected data." we need to check that.

a24sakma added the

team leaders

label

2026-05-07 19:36:53 +00:00

a24sakma commented

2026-05-08 09:15:56 +00:00

Author

Collaborator

This change is moved to future as now we are focusing on the frontend.

a24sakma added the

wontfix

label

2026-05-08 09:16:33 +00:00

a24timsv commented

2026-05-08 17:31:25 +00:00

Collaborator

This should be covered by using stacks or sub-compose files (see #635). I will also cover the issue with connectionString referencing a specific database (see #808 comment).

It is in my opinion that this should be done before handing it over to the next year as they will otherwise receive a cluttered compose file that is hard to follow. It could also be included in the service creation script to generate the skeleton for the stack/sub-compose file.

I'm fairly certain that @c24elipe or @a24noabe could figure it out since they both know enough about docker to do so.

This should be covered by using stacks or sub-compose files (see #635). I will also cover the issue with connectionString referencing a specific database (see [#808 comment](https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/808#issuecomment-9203)). It is in my opinion that this should be done before handing it over to the next year as they will otherwise receive a cluttered compose file that is hard to follow. It could also be included in the service creation script to generate the skeleton for the stack/sub-compose file. I'm fairly certain that @c24elipe or @a24noabe could figure it out since they both know enough about docker to do so.

a24sakma commented

2026-05-09 11:41:58 +00:00

Author

Collaborator

@a24timsv wrote in #825 (comment):

This should be covered by using stacks or sub-compose files (see #635). I will also cover the issue with connectionString referencing a specific database (see #808 comment).

It is in my opinion that this should be done before handing it over to the next year as they will otherwise receive a cluttered compose file that is hard to follow. It could also be included in the service creation script to generate the skeleton for the stack/sub-compose file.

I'm fairly certain that @c24elipe or @a24noabe could figure it out since they both know enough about docker to do so.

I think the customer has clarified his priority and me and @c24danli concluded that even though the change itself is very easy but we don't focus on it now but if we have ambitions developers that can deliver it this period I wouldn't stop it from our team. :) what is your though @c24danli ?

@a24timsv wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/825#issuecomment-9210: > This should be covered by using stacks or sub-compose files (see #635). I will also cover the issue with connectionString referencing a specific database (see [#808 comment](https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/808#issuecomment-9203)). > > It is in my opinion that this should be done before handing it over to the next year as they will otherwise receive a cluttered compose file that is hard to follow. It could also be included in the service creation script to generate the skeleton for the stack/sub-compose file. > > I'm fairly certain that @c24elipe or @a24noabe could figure it out since they both know enough about docker to do so. I think the customer has clarified his priority and me and @c24danli concluded that even though the change itself is very easy but we don't focus on it now but if we have ambitions developers that can deliver it this period I wouldn't stop it from our team. :) what is your though @c24danli ?

a24sakma removed the

wontfix

label

2026-05-11 08:13:24 +00:00