Skip to content

Commit

Permalink
Merge pull request #22 from Academic-Weapons/documentation
Browse files Browse the repository at this point in the history
Documentation week 5, 3. Removed keys.
  • Loading branch information
Magmose authored Mar 7, 2023
2 parents 287a46a + 1a7361e commit 153e4ff
Show file tree
Hide file tree
Showing 4 changed files with 15 additions and 41 deletions.
38 changes: 0 additions & 38 deletions MiniTwit/id_rsa

This file was deleted.

1 change: 0 additions & 1 deletion MiniTwit/id_rsa.pub

This file was deleted.

12 changes: 11 additions & 1 deletion worklogs/session03/README.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,12 @@
# Session 03 worklog
## Arguments for the choice of virtualization techniques and deployment targets.
## Arguments for the choice of virtualization techniques and deployment targets.

We chose to use DigitalOcean as a platform to deploy our server to as you get 200 free credits to host managed service and servers.

As students our budgets are a big concern and therefore DigitalOcean seemed like a solid choice for the purpose of this course.However, it also offers high-performance hardware, fast SSD storage, and a reliable network infrastructure, ensuring that our server can handle high traffic and provide a smooth user experience. Additionally security is a crucial aspect of any web application. By using DigitalOcean's built-in security features such as firewalls, SSH keys, and two-factor authentication, we can ensure that our server is protected against unauthorized access and potential cyber threats

We also chose Vagrant as our virtualization technique as it allows for easily reproduceable environments - both for creating develoment and production environments. In addition it's allowing us to test and deploy the server without worrying about potential conflicts or dependencies as Vagrant takes care of that for us. We combined Vagrant with Docker, a platform for containerizing applications, to streamline deployment and management, as well as to ensure consistency across environments.

In DigitalOcean we have also turned on a Reserved IP address which we can assign a Droplet and then reassign to another Droplet later, as needed. This also allows us to build a failover mechanism with reserved IPs to build a high availability infrastructure for our service.

Overall, DigitalOcean, Vagrant, and Docker provide a flexible, scalable, and secure solution for hosting our server, while also optimizing our deployment and management processes.
5 changes: 4 additions & 1 deletion worklogs/session04/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,7 @@ We have choosen Github Actions with a YAML file for configuration and Docker for

4. Wide Range of Supported Platforms and Environments: Github Actions supports a wide range of platforms and environments, including Linux, macOS, and Windows, as well as cloud services such as AWS, Azure, and Google Cloud, if we want to migrate in the furture.

5. Community Support: Github Actions has a large and active community of developers, who share their workflows and best practices on Github.
5. Community Support: Github Actions has a large and active community of developers, who share their workflows and best practices on Github.

### Secrets
Currently we're also using github secrets, that integrates with the Github Actions. This way we can store secrets that the pipeline requires, in our organazation so that it can be updated on the fly.

0 comments on commit 153e4ff

Please sign in to comment.