search

lealceldeiro / org.wcdevs.blog.front

Holds the `org.wcdevs.blog.front` application
https://wcdevs.org
Apache License 2.0
2 stars 0 forks source link

Define the project skeleton #3

Closed lealceldeiro closed 2 years ago

lealceldeiro commented 3 years ago

Define the project skeleton (initial resources, framework structure, config files, etc). We should not miss the .gitignore, README.md and .editorconfig files.

lealceldeiro commented 3 years ago

A default html, css, js, etc. is fine to be used to define the skeleton -- these are generally provide by some npm project generator (i.e.: for react, angular, etc.). Later on, we'll change to to the real ones.

lealceldeiro commented 3 years ago

If any test with the core endpoints are needed we should be able to bootstrap the project initial set up (on demand in this initial stage to save some $ on AWS) by executing the initial setup actions (from 01, to 03 here: https://github.com/lealceldeiro/org.wcdevs.blog.awsdeployer/actions) and getting the core app deployed (by getting this action executed https://github.com/lealceldeiro/org.wcdevs.blog.core/actions/workflows/build-and-publish.yml).

After that the API endpoints should be accessible via the AWS, ELB (Elastic Load Balancer) with a base URL like this http[s]://dev-loadbalancer-200136551.eu-central-1.elb.amazonaws.com/, API docs should be available under a URL like: http[s]://dev-loadbalancer-200136551.eu-central-1.elb.amazonaws.com/docs/index.html

lealceldeiro commented 2 years ago

A very basic structure was created here 34127287647bfb58790f366105aab5a9dab11a5c

This should serve as a starting point to integrate the frontend deployment in the AWS stack. But we can change it as needed later, this is just needed to be done now to get it integrated and tested in the AWS infra setup.