Welcome Guest [Login | Register| Register as Seller]

Netjuke V1.0b16

Related Searches:
Netjuke V1.0b16
NetJuke v1.0b16.zip
Netjuke
Free Netjuke V1.0b16
Netjuke V1.0b16 Download

NetJuke v1.0b16.zip

Name: NetJuke v1.0b16
Size: 1.16 MB
Type: Compressed (zipped) Folder
Date modified: 8/19/2008 8:25 PM
Date created: 12/4/2002 2:13 AM
Date accessed: 12/4/2002 2:13 AM

NetJuke v1.0b16/netjuke/README.txt

Please see the ./docs/ directory for the provided documentation files.

NetJuke v1.0b16/netjuke/VERSION.txt

1.0b16

NetJuke v1.0b16/netjuke/docs/CHANGELOG.txt

------------------------------------------------------------------------
NETJUKE 1.0 BETA CHANGE LOG: Keeps track of the changes made
------------------------------------------------------------------------

VERSION 1.0b16: 2002-11-03 (EST: Montreal, PQ, Canada)

1. THIS VERSION IS ONLY COMPATIBLE WITH PHP 4.1 AND ABOVE.

This new version brings the first incarnation of the long-awaited
jukebox feature (server-play), adds RealAudio support to the Recursive
Audio File Finder, uses md5 encryption for user passwords in the database,
removes the cookie requirement for clients not accepting or supporting
them, now supports apache 2, fixes some problems with the app and the
installer, and more. See below for install/upgrade instructions, and to
see what's new and fixed.

2. UPGRADING FROM 1.0b14, b15, b15.1 or b15.2:

You MUST RUN THE UPGRADE PROCESS of the installer to add the new
database columns required by this version, and/or convert the
existing user passwords to the new md5 format.

+ CLEAN INSTALL as second install:

If you already have a copy of the netjuke running, but want to
start fresh, remember to drop the existing netjuke database.
You can also use the delete scripts delivered in the netjuke-toolkit
if you cannot drop and create databases.

You can also create a new database to be accessed by this version,
if you want to keep your old version running as well, and simply
test this one.

After that, see netjuke/docs/INSTALL.txt and MAINTAIN.txt for details.

3. Added first incarnation of the jukebox feature (server-play).

See associated paragraphs in netjuke/docs/MAINTAIN.txt for
full details.

Currently supports mpg123, mpg321, ogg123 and winamp.

Mac OSX users can get mpg123 from http://www.drizware.com project
page located at http://www.drizware.com. Thank you!

------------------------------------------------------------------------

NetJuke v1.0b16/netjuke/docs/CREDITS.txt

------------------------------------------------------------------------
NETJUKE CREDITS: Individuals & Groups Who Make This Project Possible
------------------------------------------------------------------------

Eternal kudos go to the following people for their direct or indirect
contribution to the Artekopia Netjuke and related components.

DEVELOPERS:

- Stephane Daury: Original Author & Current Maintainer
Web Site: http://www.drizware.com/

- The MySQL Project: database system
Web Site: http://www.drizware.com/

- The Apache Foundation
Web Site: http://www.drizware.com/

Many thanks also go to the people on the respective mailing list(s) for
their support and inspiration, as well as to the providers of all the
great http servers, audio players and formats, operating systems and
the multitude of other great tools that make the Netjuke a reality.
And there sure are a lot of them!

THANK YOU! :o)

NetJuke v1.0b16/netjuke/docs/GLOBAL_LOGIN.txt

------------------------------------------------------------------------
NETJUKE: Global Login and Scheduling Notes
------------------------------------------------------------------------

USING GLOBAL LOGIN:

You can now login to the netjuke by adding the following parameters to
the URL of any of its scripts:
netjuke_login=admin@drizware.com&netjuke_password=mypassword

The string "admin@drizware.com" used in this document is meant to be a valid
netjuke account email address, and "mypassword" its associated password.
The account must be a valid netjuke admin when you want to login to admin
features, such as the music import, or if you are in security mode 1.2.
Only use the "127.0.0.1" ip if the netjuke runs on the same computer as
the software calling these URLs.

You can also logout from any script by adding the following parameters
to its URL: netjuke_logout=1

If security is a concern (it should be), please realize that using such
URLs will make your netjuke account email and password appear in the web
and proxy server logs. It is therefore advised to use the POST method with
curl to avoid this. Also, your password will be in clear text the scripts
and/or cron jobs that you might use, which will most likely be readable by
other users having shell or filesystem access to the server. To conclude,
it is an obvious advantage to use SSL, along with the POST method, so that
noone can "snif" these values on the network.

------------------------------------------------------------------------

USING A BROWSER BOOKMARK/FAVORITE FOR ACCESS:

Once logged in, go to any page you would like to automatically login to
(such as a search query, a genre listing, the browse page, etc.) and add
this page as a bookmark/favorite in your browser. Then, edit the bookmark
and add the login parameters explained above to its url.

<EXAMPLE TYPE="Browser Bookmark/Favorite">
http://127.0.0.1/netjuke/index.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword
http://127.0.0.1/netjuke/search.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=list.tracks&col=ge_id&val=1&sort=ge
</EXAMPLE>

------------------------------------------------------------------------

USING wget FOR ACCESS:

On the command line (*nix), see if you have wget by typing "whereis wget".

With wget, you can use the -O flag to specify where the output of the script
is supposed to be saved. Only use the -q (quiet) flag and/or "/dev/null" for
output if you do not care about the script's output.

<EXAMPLE TYPE="wget, HTTP GET Method">
wget -q -O /dev/null 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain'
wget -q -O /dev/null 'http://127.0.0.1/netjuke/admin/tabfile-recursive.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=process&recursive_scan=on&auto_queue=on&direct_import=on'
wget -q -O /dev/null 'http://127.0.0.1/netjuke/admin/tabfile-import.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=import'
wget -q -O /dev/null 'http://127.0.0.1/netjuke/login.php?netjuke_logout=1'
</EXAMPLE>

------------------------------------------------------------------------

USING curl FOR ACCESS:

On the command line (*nix), see if you have curl by typing "whereis curl".

With curl, make sure to use the -L option, which enables http redirection
to other pages. Only use the -s (silent) and/or ">/dev/null" options if you
do not care about the script's output. For setup, testing and debugging, use
only the -L flag.

<EXAMPLE TYPE="curl, HTTP GET Method">
curl -Ls 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain' >/dev/null
curl -Ls 'http://127.0.0.1/netjuke/admin/tabfile-recursive.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=process&recursive_scan=on&auto_queue=on&direct_import=on' >/dev/null
curl -Ls 'http://127.0.0.1/netjuke/admin/tabfile-import.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=import' >/dev/null
curl -Ls 'http://127.0.0.1/netjuke/login.php?netjuke_logout=1' >/dev/null
</EXAMPLE>

<EXAMPLE TYPE="curl, HTTP POST Method">
curl -Ls -F 'netjuke_login=admin@drizware.com' -F 'netjuke_password=mypassword' -F 'do=maintain' 'http://127.0.0.1/netjuke/admin/db-maintain.php' >/dev/null
curl -Ls -F 'netjuke_login=admin@drizware.com' -F 'netjuke_password=mypassword' -F 'do=process' -F 'recursive_scan=on' -F 'auto_queue=on' -F 'direct_import=on' 'http://127.0.0.1/netjuke/admin/tabfile-recursive.php' >/dev/null
curl -Ls -F 'netjuke_login=admin@drizware.com' -F 'netjuke_password=mypassword' -F 'do=import' 'http://127.0.0.1/netjuke/admin/tabfile-import.php' >/dev/null
curl -Ls -F 'netjuke_logout=1' 'http://127.0.0.1/netjuke/login.php' >/dev/null
</EXAMPLE>

------------------------------------------------------------------------

USING cron FOR SCHEDULING:

Below are two examples of cron jobs, as set through "crontab -e" on *nix.

<EXAMPLE TYPE="cron">
59 9 * * 3 wget -q -O /dev/null 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain'
59 15 28 1 * curl -Ls 'http://127.0.0.1/netjuke/admin/tabfile-recursive.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=process&recursive_scan=on&auto_queue=on&direct_import=on' >/dev/null
59 21 * 8 * curl -Ls -F 'netjuke_logout=1' 'http://127.0.0.1/netjuke/login.php' >/dev/null
</EXAMPLE>

It is advised to use the db-maintain script before using the music or
tabfile import ones one, as you most likely want to delete the netjuke
tracks that cannot be found in the filesystem before you start importing
new ones. This is a nicer way to handle files that changed location.
It's also a good idea to use the logout function after.

------------------------------------------------------------------------

USING FROM OTHER APPLICATIONS

You can also access these functions through any application that will support
an http connection, or can access the appropriate command line tools.

<EXAMPLE TYPE="perl, curl">
#!/usr/bin/perl
print `curl 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain'`;
`curl 'http://127.0.0.1/netjuke/login.php?netjuke_logout=1'`;
exit;
</EXAMPLE>

<EXAMPLE TYPE="perl, lwp">
#!/usr/bin/perl
use HTTP::Request;
use HTTP::Response;
use LWP::UserAgent;
my $request_1 = new HTTP::Request('GET', 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain');
my $ua_1 = new LWP::UserAgent;
my $response_1 = $ua_1->request($request_1);
if ($response_1->is_success) {
my $request_2 = new HTTP::Request('GET', 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain');
my $ua_2 = new LWP::UserAgent;
my $response_2 = $ua_2->request($request_2);
}
exit;
</EXAMPLE>

<EXAMPLE TYPE="sh, curl">
#!/bin/sh
curl 'http://127.0.0.1/netjuke/admin/db-maintain.php?netjuke_login=admin@drizware.com&netjuke_password=mypassword&do=maintain'
curl 'http://127.0.0.1/netjuke/login.php?netjuke_logout=1'
exit 0
</EXAMPLE>

------------------------------------------------------------------------

NetJuke v1.0b16/netjuke/docs/INSTALL.txt

------------------------------------------------------------------------
NETJUKE: Software Installation Notes
------------------------------------------------------------------------

IMPORTANT NOTES

1. Existing users should refer to the provided UPGRADING.txt instead.

2. The netjuke is now only compatible with PHP 4.1 or over. PHP 4.07
or prior is not supported because of major changes since PHP 4.1
in how global variables are handled.

3. Mac OS X users might want to read the following if they are new to
PHP and MySQL, and want a step-by-step help on how to install both,
as well as the netjuke itself: http://www.drizware.com/oddball/
(Thanks Ethan for this great doc!).

4. On Windows, make sure to select "Advanced" when you install PHP,
and select "Show all errors" (3rd choice) when prompted by the
PHP installer for the level of error reporting. Not doing so will
result in not being able to install or run the netjuke.

------------------------------------------------------------------------

NEW INSTALL: SHORT VERSION:

1. Download the latest release of the netjuke package.

2. Create and/or make sure you have access to a database.

3. Unpack the Netjuke files in a web accessible directory.

4. Go to http://www.drizware.com/

2. Create and/or make sure you have access to a database.

Examples:

+ PostgreSQL:
shell: createdb <database_name>
shell: psql <database_name>

+ MySQL:
shell: mysql -u your_user -p
mysql: create database <database_name>;
mysql: use <database_name>;

The netjuke doesn't require for the database instance to be dedicated
to its application. All the DB objects (tables, indexes, etc.) are
prefixed with "netjuke_" so that they do not conflict with others you
might have created for another software and/or data repository.

Portability being a primary focus, this hopes to help insure keeping
a low footprint for the overall solution, as well as insure that
people with most basic hosting accounts can still host their data
in a shared database.

3. Unpack the Netjuke files in a web accessible directory.

If you are upgrading, be sure to backup a copy of your existing
preference file before you overwrite anything...

The web server must have PHP installed and running, and PHP must
have the appropriate libraries for the database type you will be
connecting to.

The web application, the database, and the media files can all be
hosted on different servers/networks to allow for multiple apps
connecting to a single data source, streaming files from multiple
servers, etc.

If your user privileges allow for such tasks, we do advise to use
whatever extra security measures you have access to.

Suggestions:

- Leave the server(s) behind a firewall.

- Use host-based authentication at the http server level for the
application and streaming servers (.htaccess, etc.).

- Use host-based authentication at the database server level.

- Use SSL for browser access, and tunneling for server-side
connections.

- Use bandwidth and/or disc space quotas for the streaming server.

4. Go to http://.../netjuke/installer/installer.php and proceed with
the appropriate installation steps (license + docs + web form).

If you want to access the netjuke from more than one computer
right away, make sure to connect to the installer using a valid
hostname or ip address (IE: not just 127.0.0.1 or localhost).

The installer will ultimately generate the required database
objects, as well as provide you with the vital "inc-prefs.php"
file that will host all your preferences and configurations
based on the answers you provide.

FOR INCREASED SECURITY, remove the "installer/" directory from
within the netjuke when you are done installing.

5. Save the resulting text file as netjuke/etc/inc-prefs.php

This file must be saved as /etc/inc-prefs.php, the leading slash
being the root of the netjuke application.
(eg: http://your.domain.dom/netjuke/etc/inc-prefs.php

IMPORTANT: After saving the resulting file, we strongly advise
to verify it in a text editor to make sure there are no empty
characters or blank line before the top "<?php" and after the
bottom "?>" as they may generate errors when the file is used
by the freshly installed application.

Some browser will prompt you to save the file (as inc-prefs.php),
while some will save it to your default download folder, or
even display the content of the file. Just make sure to verify
the file afterward. If unsure or unsucessful, you can download
the netjuke-toolkit package, and generate the database and/or
preference file manually by referring to PHP/master-inc-prefs.php
(to be edited, not run), obfuscate-db-passwd.php, and SQL/install/.

To install multiple copies of the Netjuke application that would
connect to a centralized db and/or stream server (virtual hosts,
server farms, load or geographic balancing, etc.), the easiest
way is to simply clone the provided preference file and modify
it as needed.

FOR INCREASED SECURITY, remove the "installer/" directory from
within the netjuke when you are done installing.

6. Make the inc-prefs.php file and netjuke/var/data/ directory owned
by the web server user, or world-writable (Read/Write privileges
for all. Less secure).

If you omit to do so, you will encounter permissions errors when
importing your music, or running the database maintenance tools.

Make sure that not web server doesn't display directory listings
of you don't want users to download the tracks. This is a matter
of how your web server software is setup on your machine though,
not part of the netjuke application itself.

7. You can now login to your new Netjuke using the admin account you
just created. Refer to the admin section once logged-in to setup
your site preferences, users, and import your audio files.

8. READ THE IMPORTANT MAINTAIN.txt DOCUMENTATION

HAPPY STREAMING!

------------------------------------------------------------------------

If you need help with using or installing this software, please refer
to the web site(s) listed above to get in touch with the related user
and developer communities directly, through the provided public forums
and mailing lists. These are the best ways to get quick technical
support, or to get involved with the development of the Netjuke and
its related custom components.

For critical operations, we advise to get commercial support or
integration services from people actually involved in the development
of this software application (TekArtists, or other individuals and
organizations officially listed in the provided credits document).

Thank you for trying and/or using the Netjuke.

We hope you will enjoy this software as much as we do!

------------------------------------------------------------------------

NetJuke v1.0b16/netjuke/docs/KNOWN_ISSUES.txt

------------------------------------------------------------------------
NETJUKE: Known Issues
------------------------------------------------------------------------

- Affected versions: all (?)
- Affected OS: all (?)

Some people are experiencing problems with connecting the netjuke to
their database server.

This can be due to network settings, or permissions settings, or the
fact that your php install might not have the appropriate db libraries.

There is no fix-all solution to these issues, so your best bet is to
post to the mailing list or the forum and see if someone can help you
figuring out what the source of your problem is.

------------------------------------------------------------------------

- Affected versions: all (?)
- Affected OS: Linux

Some browsers on linux are experiencing problems with the M3U playlist
generation.

Make sure Plugger isn't installed, and all should now work fine, even
under galeon and Konqueror.

------------------------------------------------------------------------

- Affected versions: all
- Affected Audio Format: Ogg Vorbis

When the "PROTECT MEDIA" feature is enabled in the admin section, Ogg
Vorbis files will not play in XMMS, Audion, and potentially all players.

Error: no error shows in the audio player or the logs of the http
server, which makes it difficult to troubleshoot at this time.

- Opt. Fix: Turn off the "Protect Media" option in Admin -> Pref. File
Edit (or just stick to mp3 for now)

------------------------------------------------------------------------

- Affected versions: all
- Affected OS: Windows

When accessing tracks from a Netjuke playlist generated from Windows,
your audio player might not play the tracks if their respective filenames
contain parentheses (). Other platforms do not seem to be affected.

Error: winamp says 404 not found; MSIE6 media player says Error# 8007000D

There is no known solution to this problem.

- Opt. Fix: remove the parentheses from the filenames (and update the
associated netjuke record).

------------------------------------------------------------------------

- Affected versions: all (with jukebox feature)
- Affected OS: Windows

When using Windows as the server OS, and using winanmp as a player with
the jukebox (server-play) feature, the netjuke has problems adding tracks
to the playlist (replace should be fine), and killing the process of the
background winamp player. The latter leads to too many winamp processes
being started.

- Opt. Fix: restart the server to kill all current winamp bg processes.

- Looking for: proper way to add files t playlist, and how to get the
process id and kill it by pid on Windows.

------------------------------------------------------------------------

NetJuke v1.0b16/netjuke/docs/MAINTAIN.txt

------------------------------------------------------------------------
NETJUKE MAINTENANCE DOCUMENTATION
------------------------------------------------------------------------

------------------------------------------------------------------------
+ INCREASED SECURITY
------------------------------------------------------------------------

FOR INCREASED SECURITY, remove the "netjuke/installer/" directory
when you are done generating your preference file with the installer.

The netjuke installer contains a script that allows you to get some
info on your server. You might not want this info to stay available
to others after installing. The similar script available in the admin
section makes sure you are logged in as an admin to display the info.

Also if you do not want remote users to know which version of the
netjuke you are running, make sure to remove the "netjuke/VERSION.txt"
file, but only once this install process is completed, as the installer
needs it.

------------------------------------------------------------------------
+ SECURITY MODE FEATURE AND DEFAULT SETTINGS
------------------------------------------------------------------------

If you start creating users, make sure to go to the "Preference File"
screen in the admin section, and switch to the appropriate SECURITY
MODE.

Experienced users can also obviously edit the preference file with
any text editor. Its structure has been kept pretty evident to make
it easy for users to change the values manually.

------------------------------------------------------------------------
+ MUSIC IMPORT, SAMPLE DEMO DATA AND INFO EDITING
------------------------------------------------------------------------

If you would like to try this software on your server without
involving your actual audio collection, a sample data demo file
is provided in the import backup directory located within the
Netjuke directory ( */netjuke/var/data/backup/DEMO_DATA.txt )

Simply move this file from backup/ to import/, and proceed with
the import utility provided in the admin section of the Netjuke
(you need to be logged in as a Netjuke administrator).

If you then decide to go with the netjuke to handle your own music,
just use the Music Database Maintenance tools in the Admin section
to delete all the music data, while preserving the user records
(users, prefs and sessions). You can then start importing your files
using the Recursive Audio File Finder.

Use the Recursive Audio File Finder (in Admin) to scan for music on
your local system, or any mounted fileserver. Make sure to setup
permissions appropriately, as explained in the INSTALL.txts file.

When you have a lot of files, it is strongly advised to limit the
search requirements of the recursive tool by entering subdirectories
of your Music Directory, or the query could last a while, though
should run successfully in the end, unless maybe if you run PHP in
safe mode.

Personally, I split my MP3 collection by backup CD. I just create folders
named like MP3001, and load them with files until they hit the 650 MB
maximum size. I then burn a backup, and just start a new MP3002 directory.

Please note that the netjuke does not attempt to write back to your
media files when you change any information in the web interface.

If you want to edit the data that is displayed in the netjuke only (not
the actual tags), you will need to be logged in as an administrator or
an editor. If so, just click on the music note icon next to any track
in the listings (search, playlists, etc), and once the new window will
be opened, you will be able to switch to "Edit Mode".

You can change all of the track's detailed info through this tools, or
by using the batch editing tools displayed in these same listings.
You can also add and delete new genres, artists and albums, as well as
associate the record(s) with images (see customization paragraph below).

------------------------------------------------------------------------
+ AUTOMATED LOGIN AND TASK SCHEDULING FEATURES
------------------------------------------------------------------------

Please see netjuke/docs/GLOBAL_LOGIN.txt to see how you can login
to the netjuke without passing by the login page, schedule automated
music imports and/or database maintenance tasks, as well as access
these features from other scripting/programming languages.

------------------------------------------------------------------------
+ MUSIC SERVER SETTINGS AND VARIATIONS
------------------------------------------------------------------------

The Stream Server (STREAM_SRVR) and Music Directory (MUSIC_DIR)
must ultimately point to the same location if you use http or
rtsp streaming.

The Stream Server is the web url to the netjuke music directory,
and the Music Directory is the filesystem path from root to your
music. If a protocol separator (://) is not found in the Stream
Server value, the web url to the root of the netjuke is assumed.

If you use symbolic links (unix equivalent of aliases, shortcuts)
to link your music directory and replace the netjuke/var/music
directory, make sure your http server has the proper security
options enabled (FollowSymLinks). Otherwise, you will most likely
get a 403 error (access refused/denied).

On Mac OS X, and if you have the netjuke within a specific user's
"Sites" directory instead of at the apache root located at
/Library/WebServer/Documents, you will have to make sure that
the appropriate apache include config file for this user has the
FollowSymLinks option turned on as well (/etc/httpd/users/*.conf).

Also for OSX users, if you decide to point to a user's "Music"
directory (see in your home dir., iTune Music Library), you will
have to make sure to enable read privileges on this directory, as
Apple sets it to only be readable for the very user it is owned
by (drwx------).

Unix symbolic link are not supported (or complicated) on Windows,
so users are advised to use a virtual directory in IIS/PWS, or
a <Directory> block with apache.

You can also use virtual hosts for the streaming server.

A neat feature of the netjuke is that the location field of any
track can be set to a local file (relative to the defined music
directory), or a full url to a radio stream (http://www.drizware.com/.

- *nix: Except on OSX, people wanting to use this on *nix will have to
make sure that the webserver can run the player, and has write access
to their audio device (/dev/dsp, /dev/audio, etc). Linux (and others?)
have a tendancy to have the audio device owned and only readable by
root. Sometimes, X windows will also change these permissions upon
startup, usually to the user X is starting as. This makes it quite a
challenge to keep access to the audio device... Some users switch the
sticky bit as root on their players (chmod a+s), some use shell scripts<

Price: $0.00

Product Code: NetjukeV10b16

Quantity: Download!