MitsuWiki

Outils pour utilisateurs

Outils du site

Piste : • i_m_feeling_lucky • magnyaa
php:magnetik_nyaatorrents

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
Prochaine révision		Révision précédente
php:magnetik_nyaatorrents [2012-06-19 09:57] – mitsuphp:magnetik_nyaatorrents [2012-10-15 23:03] (Version actuelle) – mitsu
Ligne 2: Ligne 2:
 ===== Lightweight Infohash Database ===== ===== Lightweight Infohash Database =====
  
-IMPORTANT: Magnetik is no longer developed ! Using it in a production environment is strongly unwise.+---- 
 +<file>IMPORTANT: LiVID/Magnetik is no longer developed ! Using it in a production environment is strongly unwise and difficult.</file>
  
-The new project is called [[php:magnesia|Magnesia]]. Don't waste more time on this page ;-)+**The new project is called [[php:magnyaa|Magnyaa]]. Don't waste more time on this page ;-)** 
 + 
 +----
  
 **Download:** **Download:**
Ligne 71: Ligne 74:
   * first public release, working HTML, insertion, search and full listing.   * first public release, working HTML, insertion, search and full listing.
  
-===  how Magnetik and Magnesia were born ===+===  how Magnetik and [[php:magnesia|Magnesia]] were born ===
  
  
Ligne 81: Ligne 84:
 Manipulating a real database ? Well ok, but it shouldn't rely on a heavyweight like MySQL or PostGreSQL (not very easy to backup and restore). So I started messing around with SQLite3 and fSQL. And here we are :) Manipulating a real database ? Well ok, but it shouldn't rely on a heavyweight like MySQL or PostGreSQL (not very easy to backup and restore). So I started messing around with SQLite3 and fSQL. And here we are :)
  
-SQLite and fSQL are working well and all, but for very heavy databases they just aren't fast enough. We're talking about retrieving little data and parsing mid-long listings: it's much more efficient to split the data and load it on-demand as close as possible from the target. This leads us to Magnesia. We talk about it later..+SQLite and fSQL are working well and all, but for very heavy databases they just aren't fast enough. We're talking about retrieving little data and parsing mid-long listings: it's much more efficient to split the data and load it on-demand as close as possible from the target. This leads us to [[php:magnesia|Magnesia]]. We talk about it later..
  
 ===  SQLite3 ? fSQL ? Does it work on my hosting ? === ===  SQLite3 ? fSQL ? Does it work on my hosting ? ===
Ligne 90: Ligne 93:
 fSQL, while supporting MySQL-like commands, is still a PHP script. Having PHP5 installed is much all you need :-) fSQL, while supporting MySQL-like commands, is still a PHP script. Having PHP5 installed is much all you need :-)
  
-===  Magnesia doesn't rely on SQLite/fSQL ? ===+===  [[php:magnesia|Magnesia]] doesn't rely on SQLite/fSQL ? ===
  
 As said: for heavy databases we need something faster, much faster, but still portable. For Magnesia my choice is a plain file storage, in PHP files, the data being stored and loaded as arrays with a requiring as needed/asked. So no worry about millions of entries, PHP only loads the needed files and doesn't have to parse more than 1000 arrays. And it does it quite well and fast, on both PHP4 and PHP5. Simply said: it works fucking good on almost every web hosting for a potential heavy database (according to my calculations, the full The Pirate Bay database wouldn't weigh more than 2 GB and any data from it could still be called very fast). As said: for heavy databases we need something faster, much faster, but still portable. For Magnesia my choice is a plain file storage, in PHP files, the data being stored and loaded as arrays with a requiring as needed/asked. So no worry about millions of entries, PHP only loads the needed files and doesn't have to parse more than 1000 arrays. And it does it quite well and fast, on both PHP4 and PHP5. Simply said: it works fucking good on almost every web hosting for a potential heavy database (according to my calculations, the full The Pirate Bay database wouldn't weigh more than 2 GB and any data from it could still be called very fast).
Ligne 103: Ligne 106:
  
 -> make sure the data is correctly formatted before "wgetting" it to the instance ! The data retrieval can be affected by changes, especially on NyaaTorrents: maybe you'll have to modify the awk functions to get the right data out of the page. -> make sure the data is correctly formatted before "wgetting" it to the instance ! The data retrieval can be affected by changes, especially on NyaaTorrents: maybe you'll have to modify the awk functions to get the right data out of the page.
- 
-**Magnesia r1 is the most complete package**: code, database and feeders are provided, and README's give a good overview of it. 
  
 ===  LEGAL NOTICE === ===  LEGAL NOTICE ===
Ligne 118: Ligne 119:
 ===  LICENSE === ===  LICENSE ===
  
-Magnetik Nyaatorrents and Magnesia, published under [[http://creativecommons.org/licenses/by-sa/3.0/fr/|Creative Commons by-sa]] by Mitsu.+Magnetik Nyaatorrents, published under [[http://creativecommons.org/licenses/by-sa/3.0/fr/|Creative Commons by-sa]] by Mitsu.
  
 * included: torrent-rw, published under GNU GPL by Adrien Gibrat: https://github.com/adriengibrat/torrent-rw/ * included: torrent-rw, published under GNU GPL by Adrien Gibrat: https://github.com/adriengibrat/torrent-rw/
Ligne 128: Ligne 129:
 Bug report, feature requests, love declarations ? Head over here: Bug report, feature requests, love declarations ? Head over here:
  
-http://www.suumitsu.eu/index.php?2012/05/24/15/48/31-contact+http://www.suumitsu.eu/contact
php/magnetik_nyaatorrents.1340099836.txt.gz · Dernière modification : (modification externe)