infrastructure

This mono repository contains all infrastructure we use to run ThymeSave as a managed service.

Providers we use

CloudFlare

Battle proven DNS and DDOS protection. There service is free and they also offer SSL termination out of the box.

Oracle Cloud

Oracle Cloud provides a Free Tier that allows us to run in an cloud environment with failure resilence and use clustering. And the best of all: its completely free!

At the time of creating the project knowledge inside the ThymeSave org is very limited, so things are subject to change and improvements.

Because of the free tier we are limited on how we can build infrastructure, so please keep this in mind :)

Development

This repository is categorized by technology e.g. terraform and modules underneath it. You can find detailed information about setup and execution in the top level folders:

• terraform
• ansible

Required Tools

• pre-commit
• Python 3
• tfenv
• tflint
• tfsec
• Ansible 4.7

Commit Message Convention

This repository follows Conventional Commits

Format

<type>(optional scope): <description> Example: feat(pre-event): Add speakers section

1. Type

Available types are:

• feat → Changes about addition or removal of a feature. Ex: feat: Add table on landing page , feat: Remove table from landing page
• fix → Bug fixing, followed by the bug. Ex: fix: Illustration overflows in mobile view
• docs → Update documentation (README.md)
• style → Updating style, and not changing any logic in the code (reorder imports, fix whitespace, remove comments)
• chore → Installing new dependencies, or bumping deps
• refactor → Changes in code, same output, but different approach
• ci → Update github workflows, husky
• test → Update testing suite, cypress files
• revert → when reverting commits
• perf → Fixing something regarding performance (deriving state, using memo, callback)
• vercel → Blank commit to trigger vercel deployment. Ex: vercel: Trigger deployment

2. Optional Scope

Labels per page Ex: feat(pre-event): Add date label

If there is no scope needed, you don't need to write it

3. Description

Description must fully explain what is being done.

Add BREAKING CHANGE in the description if there is a significant change.

If there are multiple changes, then commit one by one

• After colon, there are a single space Ex: feat: Add something
• When using fix type, state the issue Ex: fix: File size limiter not working
• Use imperative, dan present tense: "change" not "changed" or "changes"
• Use capitals in front of the sentence
• Don't add full stop (.) at the end of the sentence

Contributing

Code of Conduct

ThymeSave has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Contributing guide

For infrastructure there is no standardized way to contribute. If you feel like sth. could be improved feel free to create a ticket or pull request.