Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Servatrice maintenance timed routines #402

Closed
woogerboy21 opened this issue Oct 27, 2014 · 6 comments
Closed

Servatrice maintenance timed routines #402

woogerboy21 opened this issue Oct 27, 2014 · 6 comments
Labels
App - Servatrice Tickets relating to the servatrice application

Comments

@woogerboy21
Copy link
Contributor

Currently there is no implementation for the servatrice application to perform any type of health check type routines resulting in things like replays to grow out of control. Implementing a timed routine that performs maintenance tasks would be nice. Replay cleanup is the first that comes to mind but doing other things like checking for configuration changes (maybe reg only required settings) may be another one.

Kind of brainstorming the idea right now...

@ZeldaZach
Copy link
Member

Can't a simple cronjob do this though?

@woogerboy21
Copy link
Contributor Author

For things like replay clearing, yes you can. The original idea (long term) of the routine was to allow server operators to selectively choose what items to perform for maintenance with in the UI. Replay clearing is just one example and would like to put thought into what additional maintenance type tasks would benefit from the concept.

@Daenyth
Copy link
Member

Daenyth commented Oct 30, 2014

I think a decent way forward may be to include some server maintenance scripts in the repo that would be configurable to do what you suggest. I don't think these types of tasks really belong in the code.

@woogerboy21
Copy link
Contributor Author

Really? You wouldn't prefer that the code itself contain the exact method for maintenance rather than having an outside source that may accomplish whatever maintenance task its trying to do at the risk of an un-knowledgeable operator potentially causing chaos to the DB or application?

To me having an application that has a component of it that goes unchecked isn't good practice. IE the replays can continue to grow at this point and there is no checking what so ever involved. Keep in mind replays is just the most noticeable component right now and is why I keep bringing it specifically up.

@Daenyth Daenyth added the App - Servatrice Tickets relating to the servatrice application label Nov 5, 2014
@ZeldaZach
Copy link
Member

While I think this might be a nice to have, cronjobs do the purpose and are more customizable. We need better docs on suggested cleanups for the wiki. @tooomm reach out i'll give you more details.

@tooomm
Copy link
Member

tooomm commented Oct 30, 2020

I couldn't reach you, let me know on discord.

So far, there is only a placeholder page on the wiki (plus suggested content): https://github.com/Cockatrice/Cockatrice/wiki/Servatrice-Server-Maintenance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App - Servatrice Tickets relating to the servatrice application
Projects
None yet
Development

No branches or pull requests

4 participants