Home/ Questions/Q 8358103
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T10:41:34+00:00

My friend has setting up a database for a Ragnarok Online server, and he

  • 0

My friend has setting up a database for a Ragnarok Online server, and he wants me to code the relative website, which is going to use some of that data (and obviously, i’ll have to add tables for the news system, website accounts, etc). Since i’m learning RoR i was going to do it that way.
I have a few “best practice” questions related to this :
Should I create a different database for the website, since it’s going to have its particular data alongside the game data ? (i already have a few clues to link multiple databases with Rails, but that seems too much of a hassle for what it is).
If not, do i have to create Model/Controller for each of the tables composing the database, despite the fact that i’m not going to use 90% of it ? Or just the ones that i need ?

An example of this problem : the game database has its own “user” table, but i have to have another “user” table for the website, and do some Joins between those two. So, what’s the best practice here ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Uhm, best practice is not making your own user table. This will cause you much pain. Best practice? Use an API. Expose the game’s database in some way to your website, and fetch that info with external requests in your web application.

    The reason why making a second user table is a hassle:

    1) You’ll constantly have to update it, pulling data from the original
    to keep it up-to-date.

    And I mean furthermore, you’re gonna have to create a CRON job or something pulling data from that original table to keep it up to date. Yuck. Also what if that CRON job makes a mistake? (It will)

    2) It’s almost inevitable that there will be inconsistencies if two
    separate tables are maintained. Are you sure your web application is
    really fail-proof?

    Update:

    What you’re gonna need is essentially a second Rails application that acts as a REST API for that database. For a good idea of what REST is, I’d read through this to get you started: http://tomayko.com/writings/rest-to-my-wife

    Once you have a good understanding of that, start making your app, and test if it’s working by using tools like cURL to send requests to your API.

    Once you have that done, I’d take a look into the Ruby rest-client gem like Nobita mentioned. This is what you’re going to use from your web application to request information from your API application.

    Just let me note, I think this would be a terrible first Rails project, unless you’re already really well versed in other web development tools, preferably MVC frameworks.

    • 0