Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/simonskodt/itu-minitwit
Weekly updates in the course DevOps, Software Evolution and Software Maintenance
https://github.com/simonskodt/itu-minitwit
devops twitter
Last synced: 27 days ago
JSON representation
Weekly updates in the course DevOps, Software Evolution and Software Maintenance
- Host: GitHub
- URL: https://github.com/simonskodt/itu-minitwit
- Owner: simonskodt
- License: mit
- Created: 2023-01-31T15:38:15.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2023-08-30T22:13:24.000Z (over 1 year ago)
- Last Synced: 2024-11-09T12:35:23.060Z (3 months ago)
- Topics: devops, twitter
- Language: C#
- Homepage:
- Size: 12.8 MB
- Stars: 1
- Watchers: 2
- Forks: 1
- Open Issues: 16
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://github.com/simonskodt/itu-minitwit/blob/main/LICENSE)
[](https://dotnet.microsoft.com/)
[](https://www.typescriptlang.org/)
[](https://sonarcloud.io/summary/new_code?id=simonskodt_itu-minitwit)
[](https://github.com/simonskodt/itu-minitwit/actions/workflows/snyk-security.yml)
[](https://github.com/simonskodt/itu-minitwit/actions/workflows/build-test.yml)
[](https://github.com/simonskodt/itu-minitwit/actions/workflows/continuous-deployment.yml)
[](https://github.com/simonskodt/itu-minitwit/actions/workflows/swarm-deployment.yml)
# DevOps—Twitter Project
| :love_letter: Group k—Radiator | Link |
| ------------- | ------------- |
| Website | [http://164.92.167.188:3000](http://164.92.167.188:3000) |
| Swagger | [http://164.92.167.188/swagger/index.html](http://164.92.167.188/swagger/index.html) |
| Monitoring and Logging (requires login) | [http://164.92.167.188:9091](http://164.92.167.188:9091) |
| Status on projects | [http://104.248.134.203/status.html](http://104.248.134.203/status.html) |
| Weekly commit activity per group | [http://138.197.185.85/commit_activity_weekly.svg](http://138.197.185.85/commit_activity_weekly.svg) |
## Contents
- [Missing Implementations](#missing-implementations)
- [Weeks](#weeks)
- [Week 1](#week-1)
- [Week 2](#week-2)
- [Week 3](#week-3)
- [Week 4](#week-4)
- [Week 5](#week-5)
- [Week 6](#week-6)
- [Week 7](#week-7)
- [Week 8](#week-8)
- [Week 9](#week-9)
- [Week 10](#week-10)
- [Week 11](#week-11)
- [Week 12](#week-12)
- [Week 13](#week-13)
- [Course description](#course-description)
## Missing Implementations
We currently **lack the following features**:
- Deploy to DigitalOcean with Vagrant.
- Refactor the tests to work with new design.
- Implement end-to-end tests.
- Make UML-diagram of system.
- Add scaling.
- Use Terraform for IaC.
It would be **nice to have the following features**:
- Create automatic releases when merging into main branch.
- Switching from HTTP To HTTPS.
## Weeks
### Week 1
Refactor ITU-MiniTwit to work on modern system.
- [x] 1) Adding Version Control.
- [x] 2) Try to develop a high-level understanding of ITU-MiniTwit.
- [x] 3) Migrate ITU-MiniTwit to run on a modern computer running Linux.
- [x] 4) Share your Work on GitHub.
### Week 2
Refactor ITU-MiniTwit in another programming language and tech stack.
- [x] 1) Refactor ITU-MiniTwit to another language and technology of your choice.
- [x] 2) Containerize ITU-MiniTwit with Docker.
- [x] 3) Describe Distributed Workflow, see [CONTRIBUTE.md](https://github.com/simonskodt/itu-minitwit/blob/main/Documents/CONTRIBUTE.md).
### Week 3
Continue refactoring, introduction of DB abstraction layer, and deployment of your ITU-MiniTwit to a remote server.
- [x] 1) Implement an API for the simulator in your ITU-MiniTwit.
- [x] 2) Continue refactoring of your ITU-MiniTwit.
### Week 4
Continue refactoring, Setup CI & CD for reproducible builds, tests, delivery, and deployment.
- [x] 1) Complete implementing an API for the simulator in your ITU-MiniTwit.
- [x] 2) Creating a CI/CD setup for your ITU-MiniTwit.
- [x] 3) Continue refactoring of your ITU-MiniTwit.
### Week 5
Cleaning and polishing of your ITU-MiniTwit, introduction of DB abstraction layer, and entering maintenance (Simulator starts).
- [x] 1) Add missing features.
- [x] 2) Introduce a DB abstraction layer in your ITU-MiniTwit.
### Week 6
Add monitoring to your ITU-MiniTwit and peer-review.
- [x] 1) Add Monitoring to Your Systems.
- [x] 2) Software Maintenance II: Check the user interface of another group (Group m, *Jason Derulo*), see [Issue#17](https://github.com/NiclasHjortkjaer/itu-minitwit/issues/17).
- [x] Do you see a public timeline?
- [x] Does the public timeline show messages that the application received from the simulator?
- [x] Can you create a new user?
- [x] Can you login as a new user?
- [x] Can you write a message?
- [x] After publishing a message, does it appear on your private timeline?
- [x] Can you follow another user?
### Week 7
Enhancing CI/CD setup with test suite and static code analysis.
- [x] 1) Add tests to your CI chain (Selenium)
- [x] 2) Enhance your CI Pipelines with at least three static analysis tools
- [x] eslint (typescript)
- [x] codeql (csharp)
- [x] Snyk (containers)
- [x] 3) Add Maintainability and Technical Debt estimation tools to your projects
- [x] Sonarqube
- [x] Code Climate (hosted from Code Climate, not in GitHub actions)
- [x] 4) Software Maintenance
### Week 8
Add logging to your ITU-MiniTwit.
- [x] 1) Add Logging to Your Systems
- [x] 2) Test that Your Logging Works
- The Devs introduce a bug; the Ops resolve the bug by using the logs.
### Week 9
Security Assessment & Pen Testing.
- [x] 1) Perform a Security Assessment, see [SECURITY_ASSESSMENT.md](https://github.com/simonskodt/itu-minitwit/blob/main/Documents/SECURITY_ASSESSMENT.md)
- [x] A. Risk Identification
- [x] B. Risk Analysis
- [x] C. Pen-Test Your System
- [x] 2) White Hat Attack The Next Team
- Group k Radiator -[checks]-> Group m Jason Derulo, see [Issue#20](https://github.com/NiclasHjortkjaer/itu-minitwit/issues/20).
### Week 10
Isolate components into services/containers/VMs.
- [x] 1) Add Scaling to your projects
- [x] 2) Rolling Updates
- [x] 3) Software Maintenance
### Week 11
Workshop: How to SSL in front of Docker Swarm.
- [ ] 1) Using LetsEncrypt and Nginx as a reverse proxy.
- [ ] 2) Using Digital Ocean managed load balancers as SSL terminator.
### Week 12
Encode your infrastructure setup.
- [ ] Automating also the creation of infrastructure.
### Week 13
- [x] Write report, see [BSc_group_k.pdf](https://github.com/simonskodt/itu-minitwit/blob/main/Report/build/BSc_group_k.pdf).
## Course description
As a participant of the DevOps course at the IT University of Copenhagen, we are in for a hands-on learning experience. Every week, we will make changes to a Twitter project to put into practice the concepts and tools that we learn in class. Here is what we will be covering during this course:
- Bash: We will learn the basics of the shell, navigate the file system, and execute commands.
- Packaging applications: We will get hands-on experience with packaging applications for distribution and deployment.
- Containerization: We will learn how to create and manage containers to isolate applications and their dependencies.
- Virtual Machines: We will explore the use of virtual machines for testing, development, and deployment.
- CI/CD: We will understand the concepts of Continuous Integration and Continuous Deployment, and implement them using popular tools such as Jenkins and GitLab.
- Monitoring: We will learn how to monitor the performance of our applications and infrastructure to ensure optimal operation.
- Maintainability: We will gain insight into making our applications maintainable, and understand the importance of clean code and testing.
- Log analysis: We will collect and analyze log data to identify and resolve issues in our applications.
- Web security: We will explore the importance of web security and the measures we can take to protect our applications and users.
- Scalability: We will understand the concept of scalability and learn how to design and implement scalable applications.
- Load balancing: We will balance loads across multiple servers to improve performance and reliability.
- Infrastructure as Code: We will manage and provision infrastructure using code, and understand how this can improve the consistency and reliability of our deployments.
By the end of this course, we will have developed a solid foundation in DevOps concepts and practices, and will have the skills and confidence to build, deploy, and manage applications at scale.