EVE Technology Lab

Only way to learn stuff is to ask questions so not a problem. Yapeal doesn't have any kind of frontend for getting the keys etc into it but does include classes you can use from class/util/*php to add them to it once you collect them. It should have all the APIs you need to get the other stuff you want once that's done. Make sure you read the wiki pages I pointed out a couple post back as they should be helpful to you as well.

I'm new to Yapeal as well. It's taken a couple of nights to get my head round how it works, but I will give it two thumbs up. Thanks Dragonaire

Ok Thought I'd update everyone on some changes that I've finished in the last couple days which should make existing users happier and make it easier for people just getting start with Yapeal. They also should help decrease the number of times I get to explain some of the same things over and over again. That my hope anyway but we'll see if it works that way

First let me give a little history. There have been a couple tries at adding things to Yapeal to make it easier to install. There was one that used a series of web pages first which worked and was a great chance for someone that was relative new to PHP to and Yapeal get started on. After a few months they moved on to other projects I also didn't think a web front end installer for a command line tool like Yapeal was a good match but I did see where having some kind of instiller would be helpful so I worked on adding an installer that had both GUI and command line interfaces that worked cross platform on Linux, Windows, Mac, and several other Unix platforms.

No one but me seemed to like it and many long time users continued to install manually or use the web installer even though it wasn't really working correctly any more. The GUI had several problems with it most of which came down to me trying to have it do things it wasn't made to do and trying to do it in the same ways as the web installer had.

During the development of the GUI installer I found a need to write some scripts to let it do some stuff I need so I hack together a few PHP scripts for it to use on the back end. In the mean time the Web installer became totally unusable with the changes that had happened in Yapeal and I didn't have the time to update it and like I said I thought it was bad match anyway. I was also in the middle of a rewrite in the GUI installer at the same time so Yapeal was once again without a working installer.

One reason many of the developers using Yapeal didn't like the GUI installer or even the CLI version of it is they didn't have shell access on their hosting service but they did have crontab service so they could simple install it locally and copy it over and do a few database updates with phpMyAdmin which they also had access to. I suggested to a few of them when they said something about not have either the old web or new GUI installer to use locally to help out that they could use some of the back end scripts from the GUI to do stuff if they wanted and even finally wrote up a quick check list to help them remember the steps.

If this is starting to sound familiar that's because the current process used is basically the same now but I did improve on the instructions a little and started including them with Yapeal. What wasn't improved was the scripts since the plan was to one day go back and do an improved GUI installer.

So now it's been a while and some other projects demanded some attention so for the last 6 months to a year everyone has used the scripts I hack together for the GUI back end. During that time I've had many questions about installing Yapeal etc plus had feedback from developers using it that it would be nice if they didn't have to keep reentering the same information a couple times during updates.

Now pair the above with CAK coming out and I had to switch my attention back to Yapeal again for a while and deciding I could make it smarter and take advantage of some additional information that has been made available. Also during that time PHP 5.3 was released with many improvements and many hosting sites finally dropping the older versions of PHP when the PHP developer team stopped doing updates for them etc. One of the improvements with PHP 5.3 is the Windows CLI gained better support for command line parameter processing including using long versions which all of the other platforms had supported for a long time. So now it's possible to really design CLI scripts in PHP with all the features that have been available to every other shell or command line scripting language for a long time.

So what does all of this long history lesson have to do with this update? I'm glad you asked

I've updated the old hack together scripts used to install Yapeal currently into ones that are much more human friendly and even more intelligent then before. They now have actual parameters instead of just putting the settings needed after them in the right order to make them work. You can actually ask them for help with -h or --help and not just have to figure it out by trial and error from the error you got back if you entered something wrong. At the same time using the parameters has become largely unneeded with the other major change which is they can now use the same information that the rest of Yapeal does from config/yapeal.ini.

So now you can just download/extract Yapeal some where, edit one file, and then run a few simple scripts to setup the database and tables and have it ready to take your API information.

As always your feedback is welcome both good and bad as can be seen from the above history it's important in determining what improves in Yapeal even if it sometimes seems to take forever Also bug reports are always welcome as well even if the bugs themselves aren't. You can report them here or preferably as an issue on Google Code web site.

Fly safe and continue to camp those stations I'll be inside

revision 1246

I have just upgrade but I can't get MySQL update to work. I've tested connection and it's ok:

When I try to update tables (./createMySQLTables.php -s localhost -u myyapealuser -p myyapealpass --database=myyapealdb):

Sorry for confusing you about names, I've changed them to post in forum.
I'm using Yapeal for over one month, so my yapeal.ini is working.



I enabled mysql logging but I didn't see any error in queries. I have the log if you want to see it.

I've manually imported new utilAccessMask and utilCachedInterval into my "old" yapeal database and now it works ok.

I disabled my crontab line (although I've set it up every 2h), so I think nothing should be access to my Yapeal DB.
I didn't know about cache/ADOdb/util.sql, so I installed new Yapeal in another directory and DB and just export and import ^^;

MySQL log sent.

Yes, it's working now and I have "status" column :)

Thank you for this great tool!

Thanks for a great tool Dragonaire fits my requirements exactly!
I installed yapeal ver1249 yesterday.

I run yapeal.php and get the error:
Warning: getopt(): No support for long options in this build in /etc/yapeal/inc/parseCommandLineOptions.php on line 82

Presumably this is because im running slightly old version of php5-cli. (Just runnnig this by you in case it causes problems - I dont think it should)

Anyway I added a new (Full CAK) API to the utilRegisteredKey table and a character row to the utilRegisteredCharacter table.

When I run yapeal.php (This is presumably the script i should add to cron) - it does not pull all the available APIs associated with that key.

It *did* populate the following tables however: accountAPIKeyInfo,accountAccountStatus, accountCharacters, accountKeyBridge
utilXmlCache, serverServerStatus.
So it seems to have downloaded and saved certain information to the database.

How do i add other API feeds to the database such as AssetList etc. etc. Shouldn't it just pull all apis permitted by the access mask for each api key.
Can't seem to find this anywhere, can you show an example?

Also I can't seem to see any logs? My ini is set to log_level=E_ALL and has the standard log files defined.

I dont really want to use PHP - I just want the API results cached in a mysql - so thank you for this
-duffs

thanks dude - checking now

edit - yup that was it!
Sorry for wasting time and thanks again.

@Sable Blitzmann - Make sure you backup your config/yapeal.ini and then clear the directory where you are installing Yapeal too. The most common cause of that error is ending up with multiple copies of a file in different places when they are moved around in Yapeal. I try not to do that very often because of the issues it can cause but had to do so in one of the recent versions. Also make sure you run the database update as well. You can find out more about what needs to be cleared in the CHANGELOG.

Did you export from either your local working copy or directly from the SVN because it looks like it's finding the same API twice which the only other time I've seen that is when someone was trying to use their working copy directly without export.

Now that you have a working copy you can export from it to where you plan on

running Yapeal.

svn export --force /path/to/my/wc/ /directory/where/yapeal/should/be/installed/

Let me know if that doesn't clear it up. I'm testing some other changes right now that should help with this problem as well. Once I'm sure there aren't any problems with the changes I'm looking at I'll let everyone know and have to update some of the docs to reflect the changes.