Post a Reply

Local DB option please!

  1. 10 years ago
    Z

    zyg0tic

    Show in context

    Hi. So I've decided I do want persistence for my mission, so I can restart it and not lose all the progress. However, the War Room is problematic... Frequent internal server errors, saying "Sorry." a lot. Why cant we just have a local DB option? It says because messing around with database software is a hassle - well so is War Room so whats the problem with a hasslesome local DB when the remote DB is hasslesome too?

    I've followed the tutorial steps for getting my server connected to ALiVE War Room DB and it isnt working.
    Does it matter which computer the Alive.cfg is downloaded with?
    When editing the mission, does @AliveServer have to be enabled?

  2. 9 years ago

    Tupolov

    Show in context Administrator
    Edited 9 years ago by Tupolov

    Just to chip in here.

    Finn, I didn't find your response particularly rude.

    The reasons we don't support local db are because

    1. Believe it or not there's lots of people incapable of setting up databases
    2. A lot of game hosting services don't provide dbs
    3. The effort to support people who can't admin MySQL was overwhelming with MSO
    4. Local DBs are often based around SQL and we didn't want to use a fixed scheme based DB due to the effort of updating schemas etc
    5. Some of the crew work for cloud companies, we wanted to go to the cloud
    6. Having persistence only require an http connection and a config file makes persistence accessible to everyone
    7. We wanted to offer a web based admin console for people to edit and update missions as well as have community stats
    8. We didn't want to support two DB approaches
    9. There's no developer who is around to do the SQL integration or other local DB
    10. When we want to change things - we don't need to update 1000 DBs, just ours.

    We honestly felt this approach was the best for ALiVE and we hope people respect that decision.

    Now as you can see a few quite blunt responses here shows the passion and effort some people have put in :) I hope this post explains things in more detail and is not considered bullshit reasons.

    We are looking at a possible file based local storage for certain things.

    Cheers,
    Tup

  3. Tupolov

    Show in context Administrator

    @zyg0tic BTW internal server errors on the website only occur for maps that are currently not uploaded on War Room - does not affect persistence.

    alive.cfg can be downloaded by any machine, but it must be placed on the server you setup in War Room.

    @AliveServer is only required on your server during the mission (not during editing). @ALiVE is also required on your server.

    Having a single config file and registering your server on War Room is a lot easier than administering your own DB :)