feat: adding corsOptions config variable for CORS middleware in app.js

[tech4242]

Summary

The idea of this PR is simple - introduce an optional corsOptions parameter to the siteConfig, so that one can e.g. create an Angular/React/... app where the Statusfy API is reachable without the typical CORS header errors in modern browsers like Chrome. If corsOptions is not set, nothing changes to the CORS middleware settings in Express. I have also added this to the Configuration documentation with a link to the official Express documentation. Since there is no data where authentication is needed, I thought it's harmless to give '*' as the parameter for origin but made a note for users to check out the official documentation on the middleware if they have not used it before. No tests were written for this feature.

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

[welcome]

Thanks so much for opening your first pull request! Please check out our contributing guidelines.

[ghost]

There were the following issues with this Pull Request

• Commit: 23e12fa
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 384680a
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[CLAassistant]

All committers have signed the CLA.

[ghost]

There were the following issues with this Pull Request

• Commit: 23e12fa
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 384680a
  • ✖ message may not be empty
  • ✖ type may not be empty
• Commit: 3e7f553
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[tech4242]

If you need anything from me to move forward with the PR, please let me know @juliomrqz

[ghost]

There were the following issues with this Pull Request

• Commit: 6206bee
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[tech4242]

The CI is failing because of your linter about changes that I have not committed. It initially complained about my use of !! for my CORS statement in app.js but I fixed that. Now it has found 16 other errors that were not caused by my commits (see Travis logs). Please let me know how we can proceed on this PR.

[juliomrqz]

Hello @tech4242. There are big changes coming (mostly internal) for the next major version of Statusfy (v1). For more details go to #551. A CORS middleware will not be required with the new changes

We appreciate your comments or concerns.