The wayfar1444.com domain will no longer be available starting 10th Nov. If service resumes a notice will be posted on this blog. Previous articles, which may be helpful for hellcore users, will remain available at http://wayfar1444.blogspot.com indefinitely. Thanks to the many players that tried our game, and if a new game is released, or MOO service resumed, you will be notified!
Love,
El Management
Monday, October 17, 2016
Sunday, October 16, 2016
Tutorial: Exporting JSON from Hellcore for use with jquery Datatables
* Step 1: HTML or PHP template page
You will need jquery and datatables, which can be downloaded to your local folders. These will be included in our PHP pages later. Let's say we want to display all weapons, here is the template (HTML or PHP). You must replace $weapons_db with the actual OBJNUM of your weapons database:
<html>
<head><title>Weapons Table</title>
<script src="/lib/jquery-3.1.1.min.js" type="text/javascript"></script>
<script src="/lib/datatables.min.js" type="text/javascript"></script>
<link href="/lib/datatables.min.css" rel="sylesheet" type="text/css"></link>
<script type="text/javascript">
$(document).ready(function() {
$('#weapons').DataTable( {
"ajax": "http://yourdomain.com/query.php?objid=$weapons_db"
} );
} );
</script>
</head>
<body>
<table class="display" id="weapons">
<thead>
<tr>
<th>ID</th>
<th>Name</th>
</tr>
</thead>
</table>
</body>
</html>
* Step 2: PHP ajax page
Query.php is a PHP file that queries the MOO server on port 8080. This is already setup by default in hellcore, but you need some modifications, firstly to $json_utils:_www
You must replace $json_utils in the code above with the actual object number of your JSON utils object. The code above means that we call json_utils, and we pass it an additional argument in the form of: yourdomain.com:8080/$json_utils/desired_objectnumber
* Step 3:
Now - our desired_objectnumber must have _json verb, and it must return formatted json (not HTML). Note that the data is structed very specifically to comply with jquery datatables. Example:
* Step 4: Getting JSON from our MOO server
http://yourdomain.com:8080/query.php?objid=$weapons
Will now return JSON output, something like this (partial):
{"data":[["13477","generic melee weapon"],["14111","shock baton"],
This has hopefully given you some hints for exporting this data. Modifying it, in MOO, on the fly, is also possible, with callbacks in datatables, but is more advanced. If you get the basics working, you'll see something like an auto paginating page like this:
*Step 5: Security
Use iptables to ONLY allow requests to query.php, and yourdomain.com:8080 from your own domain. Google this!
Questions? Comments?
Post them below!
You will need jquery and datatables, which can be downloaded to your local folders. These will be included in our PHP pages later. Let's say we want to display all weapons, here is the template (HTML or PHP). You must replace $weapons_db with the actual OBJNUM of your weapons database:
Query.php is a PHP file that queries the MOO server on port 8080. This is already setup by default in hellcore, but you need some modifications, firstly to $json_utils:_www
$json_utils:"_www _html" this none this
try
wargs = $su:explode(args[1], "/");
if (length(wargs) > 1)
item = toobj(wargs[2]);
if (gamevalid(item))
data = item:_json();
return {data};
endif
endif
except e (ANY)
$rpg:report_error(e);
return pass(@args);
endtry
return pass(@args);
This changes the $json_utils:_www verb to accept an additional objects. Now let's make query.php:
* Step 3:
Now - our desired_objectnumber must have _json verb, and it must return formatted json (not HTML). Note that the data is structed very specifically to comply with jquery datatables. Example:
$weapons:_json
w = $ou:fertile_branches($weapon);
data = [];
data = ["data" -> {}];
for x in (w)
id = tostr(x)[2..$];
d = data["data"];
d = setadd(d, {id, x:name()});
data["data"] = d;
yield;
endfor
return $json_utils:encode(data);
* Step 4: Getting JSON from our MOO server
http://yourdomain.com:8080/query.php?objid=$weapons
Will now return JSON output, something like this (partial):
*Step 5: Security
Use iptables to ONLY allow requests to query.php, and yourdomain.com:8080 from your own domain. Google this!
Questions? Comments?
Post them below!
Monday, October 10, 2016
Transition to Amazon managed DNS
Wayfar has originally run its own DNS servers. I shifted this to Amazon, since I am moving the server and no longer want to run DNS services on the box itself.
First step - the easy part:
Import your zone file into Route 53 Amazon. It costs about a dollar a month.
Hard part: you have a second server that you'd like to modify and upgrade before fully moving to it as your primary server.
Step 1: http://cobus.io/linux/2015/02/17/route-53-dns-update-script.html
Get these scripts installed and configure not just the DNS (test.wayfar1444.com for instance), but also a user (updateip or dyndns) with the appropriate permissions. Run the updateip script to make sure that your changes are reflected in the amazon dashboard.
Once you've confirmed that the changes are actually taking effect, use crontab to add this to your server and keep amazon's DNS service updated with your actual IP by calling crontab -e:
First step - the easy part:
Import your zone file into Route 53 Amazon. It costs about a dollar a month.
Hard part: you have a second server that you'd like to modify and upgrade before fully moving to it as your primary server.
Step 1: http://cobus.io/linux/2015/02/17/route-53-dns-update-script.html
Get these scripts installed and configure not just the DNS (test.wayfar1444.com for instance), but also a user (updateip or dyndns) with the appropriate permissions. Run the updateip script to make sure that your changes are reflected in the amazon dashboard.
Once you've confirmed that the changes are actually taking effect, use crontab to add this to your server and keep amazon's DNS service updated with your actual IP by calling crontab -e:
*/30 * * * * /home/wayfar/www/updateip.sh YOURHOSTEDZONEHERE your-iam-user your-domain.com
Subscribe to:
Posts (Atom)