EVE Technology Lab

... And NO It's not SMA.... :p

Ok Great!

Sorry for being an idiot here, what do you mean (in the OP)?

Thanks! Much appreciated.

#sudo nano /etc/supervisor/conf.d/seat.conf

and paste

[program:seat1]
command=/usr/bin/php /var/www/seat/artisan queue:listen --timeout=3600 --tries=1
directory=/var/www/seat
stopwaitsecs=600
user=apache
stdout_logfile=/var/log/seat_out.log
stdout_logfile_maxbytes=100MB
stdout_logfile_backups=10
stderr_logfile=/var/log/seat_err.log
stderr_logfile_maxbytes=100MB
stderr_logfile_backups=5

(Update the destinations if you installed seat elsewhere)

ctrl + o
ctrl + x

We can provide install services and post install support for SEAT and other 3rd party software if you can't/don't want to do it yourself.

Forum Post

Website

It is somewhat. A mixture of it being summer and so people have been busy with other things, and a larger code update in the background means it doesn't look very active, but work is taking place.

We can provide install services and post install support for SEAT and other 3rd party software if you can't/don't want to do it yourself.

Forum Post

Website

So my question.
Is there an ability to share keys between groups?

Ex. RO1 adds a key, RO2 who logins can't view it. If RO2 adds the same key, RO1 isn't able to see it anymore. Superusers are still able to see the key, but is it possible to share the keys between groups?

Good morning. Ive got this all up and running. However since the last release, a full api isnt a full api anymore. Where can I go to update the FULL api url.

Id like to update the FULL URL and remove the minimum recommended all together.

Thanks

Case Study

A few days ago one of our offices was closed and all the assets vanished. While it wasn't much, we obviously don't want to let people get away with theft, however small. Thankfully, because SeAT is always running and updating on a server, the chances were, it had already updated everyones assets and I could find out who did it.

To start with I needed to narrow down the list of suspects because I didn't want to spend all day searching everyones assets. For this I used the Security audit tools in SeAT. These include a list of current permissions members have, and a change log so I could see if a director was granting access to an alt or something. With these tools in SeAT I now had a short list of suspects who had permission to close an office and/or access to the particular hanger with most of the assets.

The next step was to find the assets to pin point who actually did it. I knew we had some items in the office which aren't too common (random meta level modules, not something shiny :p), so using the generic search feature in SeAT I had a list of toons with that item in seconds. This narrowed down the list even more. From the search results I could then simply view each character and their assets, grouped by station.

Once I found the toon (an alt), SeAT straight away told me all the associated characters and I could determine their main toon.

TL;DR: Used SeAT to track down stupid corp thief and collect all the evidence you would ever need. All in under 20 minutes.