https://github.com/daemontoolz/workstation
Just a personnal project about a Simplified Collaboration tool
https://github.com/daemontoolz/workstation
asp csharp database golang net-mvc signalr
Last synced: 3 months ago
JSON representation
Just a personnal project about a Simplified Collaboration tool
- Host: GitHub
- URL: https://github.com/daemontoolz/workstation
- Owner: DaemonToolz
- License: gpl-3.0
- Created: 2017-07-24T09:33:24.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2018-02-02T13:23:50.000Z (over 8 years ago)
- Last Synced: 2025-01-28T14:17:04.188Z (over 1 year ago)
- Topics: asp, csharp, database, golang, net-mvc, signalr
- Language: JavaScript
- Homepage:
- Size: 15.6 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# WorkStation
Workstation is a simplified and open collaboritve tools.
## What is it?
By itself, it is a bundle divided into 2 projects, a client-side and a server-side.
The client project regroups all targets:
- Browser, using ASP.NET MVC, framework 4.6.2, and SignalR : Probable evolution towards an ASP.NET Core 2.0 MVC + Angular 5 & SignalR
- Application, using WPF and framework 4.6.2
- Mobile, hopefully on Android, iOS and Windows.
- One part will be both on Client and Serverside and mostly written in Go for large data transfert and treatment across the network.
The server project:
- Authentication Services, token-based for the most. This one intends to be used on a wider range of projects not, necessarily, combining a username / password + token auth. Using ASP.NET Core 1.
- Global Management Services, for a direct control of the database. It is based on a Windows Authentication system, restricting the utilization. Using ASP.NET MVC and framework 4.6.2.
- Database Management Services, local Windows Services to clean and review the databases.
- Workstation Services, the "mainframe" WCF service interacting with the previous clients. This one is based both on a Username / Password verification and a Token generation. It could have been simpler, yet this project is mainly an "experimentation".
Both projects are / will be checked with SonarQube.
## How does it work?
## Note
Right now, the entire structure is based on a Monolithic architecture - everything's managed by 1 service - yet if the amount of actions increases, then Microservices will be considered.