How we do decide the name of shopping mall? Does anyone have some ideas?

Frontend UI has to be integrated.

Bank server developers (team 1) will give us special account to manage transection between customors and shopping mall server.

To communicate, special json data structure will be used.
Please design the spec, and write down with markdown at webserver directory.
When finished it, I'll send it to team 1.

Hide purchase button in cart page when there are no item in cart page..
Although server handles it,
it makes user push and get the error message.

After running make in database/, I get the following error:

...
Setting up libhtml-template-perl (2.95-1) ...
Setting up mysql-server (5.5.55-0+deb8u1) ...
Processing triggers for libc-bin (2.19-18+deb8u6) ...
Processing triggers for systemd (215-17+deb8u5) ...
mysql -uroot -p"is521" < initializeData.sql
/bin/sh: 1: cannot open initializeData.sql: No such file
Makefile:5: recipe for target 'mysql' failed
make: *** [mysql] Error 2

Whenever I try to buy items that calls "router.get('/purchase ..."
one of the errors are

express deprecated req.param(name): Use req.params, req.body, or req.query instead routes/product.js:82:26
express deprecated req.param(name): Use req.params, req.body, or req.query instead routes/product.js:83:27

I looked up what the errors mean and it said that we need to change this

    var product_id = req.param('product-id');
    var product_num = req.param('product-num');

to

    var product_id = req.param.product-id;
    var product_num = req.param.product-num;

But when we change that, the code won't work anymore! :(

If you checked, reply about that on this thread please.

I implemented with MySQL for the rapid prototyping.
But some guys said 'they are familiar with SQLite.

So, we choose the DBMS.
The issue will be like the followings.

1. compatibility test with current version of SQL script
2. Makefile for installing DBMS without any problem

When gpg verification is successful, the /var/ctf/shoppingmall.flag file should be updated, with the correct permissions.

Port 42

Accepts JSON

For final submission,
We should make all processes (include initial settings) automatically.

I think current sql files are not suitable for that.
Please check:https://github.com/KAIST-IS521/TeamOne/blob/master/db/Makefile
and apply similar format for our environment.

Frontend UI has to be integrated.

We have to check the undefined scenario which should explain how to deal with the sent message.

Check that flag signature field with gpg verification, using signer's public key.

Is it possible to change output format like following?

print ID
print PW
--> print ID, PW

The initial version of database design for implementing and testing.

Frontend UI has to be integrated.

80 is very commonly used in many web services, so I think changing it is better to avoid port conflicting

For co-working, we need the basic structure in files and directories.
Moreover, some guys are not familiar with Node.js.
Therefore, the code should be proven by working correctly the basic scenario,
so it has to be easy to understand the overall architecture and add the code which is assigned to the other members.

https://developer.github.com/v3/users/gpg_keys/

I think we should agree on a convention for the build system. As the assignment specifies, there should be a toplevel Makefile with a default target building every sub project. So, if every sub project also has a make file (e.g. flagUpdater/Makefile.flag), with the same default target, the toplevel make file could look like:

all: foo bar

foo:
    make -C foo

bar:
    make -C bar

Where foo and bar are each sub-project, webServer etc.

This makes the top-level make file simple to handle and isolates all sub-project specific build stuff to their respective directory. What do you guys think?

Should verify given signature with set of valid gpg keys from TA's

GPGME C Library

Frontend UI has to be integrated.