Skip to content

nicklaustrup/kenziegains

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

97 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ATA-Capstone-Project-KenzieGains

Follow the instructions in the course for completing the group Capstone project.

Fill out the environment variables

Complete setupEnvironment.sh with the group repo name and the github username of the team member holding the repo. Confirm these are in lower case. The repo owner should confirm that all team members have been added to collaborate on the repo.

To create the Lambda Example table in DynamoDB:

You must do this for the ServiceLambda to work!

aws cloudformation create-stack --stack-name lambda-table --template-body file://LambdaExampleTable.yml --capabilities CAPABILITY_IAM

To deploy the Development Environment

Run ./deployDev.sh

As you are taking a break from work, use the END LAB button in Vocareum instead of removing the pipeline each time. The End Lab button will pause the lab and resources, not allowing the budget to be used. When you're ready to start again, click the Start Lab button to begin again with renewed AWS credentials.

To tear down the deployment then run ./cleanupDev.sh

To deploy the CI/CD Pipeline

Fill out setupEnvironment.sh with the url of the github repo and the username (in all lowercase) of the team member who is maintaining the repo. Confirm that the team member has added your username as a contributor to the repo.

Run ./createPipeline.sh

As you are taking a break from work, use the END LAB button in Vocareum instead of removing the pipeline each time. The End Lab button will pause the lab and resources, not allowing the budget to be used. When you're ready to start again, click the Start Lab button to begin again with renewed AWS credentials.

To teardown the pipeline, run ./cleanupPipeline.sh

Steps for developing/working locally

>> Activate local AWS container

  • Start Docker

>> Install the DynamoDB instance in the Docker container - Do this every time Docker has been shutdown

  • Open a terminal in Intelli J and run:
./local-dynamodb.sh

>> Activate local DynamoDB interface

  • Open a terminal in Intelli J and run for Windows:
set DYNAMO_ENDPOINT=http://localhost:8000 dynamodb-admin
  • Open a terminal in Intelli J and run for Mac:
DYNAMO_ENDPOINT=http://localhost:8000 dynamodb-admin

>> Builds the application and starts the local web server - Do this every time you make code changes to your project

  • Open a terminal in Intelli J and run:
./gradlew :Application:bootRunDev

>> Load the test data

  • Open a terminal in Intelli J and run:
./dynamodb_preload.sh
  • If you want to delete all the entries from your tables. Stop all the commands from above that are running in the background; and start over.

>> Just for building

  • Open a terminal in Intelli J and run:
./gradlew build

>> For Unit tests and Code Coverage

  • Open a terminal in Intelli J and run:
./gradlew jacocoTestReport
  • Reports will be recorded in:
Application/build/reports/jacoco/test/html/index.html
  • Open this file in IntelliJ by right-clicking and going to:
Open In -> Browser -> (Your browser of choice)

Tools for developing/working locally

>> Local DynamoDB interface page

http://0.0.0.0:8001/

>> Local API interface page

http://localhost:5001/swagger-ui/index.html 

>> Frontend local page

http://localhost:5001/index.html 

GIT workflow

  • At the beginning of the day, make sure you are in your branch by running:
git checkout <your_branch_name>
  • Before pushing your changes make sure you are in your branch by running this command and checking that an asterisk is next to it:
git branch -a
  • Push your changes by running:
git add .
git commit -m "<your_code_change_description>"
git push
  • Create a "Pull Request" by clicking on the "New Pull Request" button next to your branch in here:
https://github.com/KenzieAcademy-SoftwareEngineering/ata-lbc-project-movienightrsvp/branches
  • Notify a team member for reviewing the code change, approving it; and merging into main.
  • Once the changes have been merged into main, run the following commands for keeping the branches in your desktop in sync with the recent changes:
git checkout main
git pull
git checkout <your_branch_name>
git pull
git rebase main
  • If the rebase cannot be performed due to un-committed changes in your branch, commit them and then retry the rebase.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published