INTELLIGENT INTERN PLACEMENT WEB-BASED SYSTEM

Paul Bentor1, Alma Bernales2, Gerran Simacon3, Lester Villanueva4

1st WEEK REPORT
March 17 – 23, 2019

SUMMARY
The team held a meeting to discuss the following agenda: development environment; framework to use;
task assignments; web hosting; domain; mock-up; and other concerns. It was decided by the group to
name the system “Intern Link” after searching for available domain names. A temporary domain name
internlink.cf was registered and using the free AWS, a cloud instance was setup with Linux 2 and LAMP
was installed. Additionally, a web server was setup to run on SSL with the final working test site at
http://www.internlink.cf and a temporary splash page was uploaded. The team also decided to use
react.js or Laravel for the development. A mock up of the site layout was created to guide the UI
designer.

1 PROBLEM/ISSUE/TASK #1: DEVELOPMENT ENVIRONMENT

Setup development environment that is accessible to all members and compatible with all technologies
to be used for this development project.

1.1 SOLUTION #1
Launched a cloud instance with Linux 2 using AWS free tier. Security settings for instance was set to
allow traffic for HTTP/S and SSH. Server was accessed using Putty, LAMP was installed and setup.
Server was tested using the given IP address and was able to access the Apache Test Page. SSH
credentials and ppk file was distributed to fellow team members. All members able to access the server.

2 PROBLEM/ISSUE/TASK #2: SYSTEM NAME, DOMAIN, AND SSL

Select system name and setup domain running on SSL.

2.1 SOLUTION #2
Group had a team discussion on possible name, after deliberation and checking if name and domain is
available, it was decided that system name will be Intern Link. Using Freenom, domain was checked if
available, and was found to be unbound. It was decided to use a free domain extension during the
development phase, internlink.cf was registered. DNS settings of the domain was setup to redirect to
AWS server setup earlier. AWS server was then setup to run SSL using EC2Bot. Server was
successfully setup and tested with the server running on SSL, https://www.internlink.cf .

3 PROBLEM/ISSUE/TASK #3: DESIGN MOCK-UP

Create mock-up to guide UI designer.

3.1 SOLUTION #3
Using Figma, design mock-up were created and distributed to team members assigned to create UI.
https://www.figma.com/file/FbEk5Zg6repiGnftgza76B90/Internlink?node-id=0%3A1

4 PROBLEM/ISSUE/TASK #4: TEMPORAY SPLASH PAGE

Create temporary splash page so Freenom will not disable the free domain.
4.1 SOLUTION #4
Created a counter welcome page using HTML, CSS, and Javascript.

REFERENCES
[1] Amazon Web Services (2019). Tutorial: Install a LAMP Web Server on Amazon Linux 2.
Retrieve from https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-lamp-amazon-
linux-2.html
[2] Amazon Web Services (2019). Tutorial: Configure Apache Web Server on Amazon Linux 2 to
Use SSL/TLS. Retrieve from https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-
an-instance.html#letsencrypt