Hardware Reference
In-Depth Information
Step 5 - filling the server database and
contents
It's now time to fill the
MediaDrop
database we've created previously with some
tables and required data. We just have to call a predefined command:
(venv)debian@beaglebone:~/MediaDrop$ paster setup-app deployment.ini
Step 6 (optional) - full-text searching
Create some triggers that will allow you to have better searches than exact matches,
as follows:
(venv)debian@beaglebone:~/MediaDrop$ mysql -u root -proot MediaDrop <
MediaCore-0.10.3/setup_triggers.sql
Nothing else is remaining; we are in. Time to start our first server!
Testing time - "Hello Server"
You have a server that is waiting to be started locally:
(venv)debian@beaglebone:~/MediaDrop$ paster serve --reload production.ini
source env/bin/activate
You need to wait for the last line to be displayed before you move on, which means
that the server is ready to answer the request.
Take the example of your command, which ends with the following
line of code:
IOError: [Errno 2] No such file or directory: '/home/
debian/production.ini'
You might not be in the good path; using the
ls
command, check
whether the
production.ini
file exists in the current directory.
Now, from anywhere on your local network, enter the address of your board with
the defined port—for me, it's
192.168.0.15:8082
.
