Software system for the management of technical support tickets, which will serve the users, and optimize the existing mechanisms. In addition, the system offers high-level overview dashboards, which manual systems do not.
- Variables shall be named in lower case, words separated by underscores. Example:
my_variable
. - Functions shall be named in lowerCamelCase. Example:
void myFunction()
. - Structs shall be named in UpperCamelCase. Example:
struct MyStruct {}
. - Non-business-logic modules shall be implemented via Pimpl, and the related functions shall be prefixed with the module name. Example:
myModule_myFunction()
. - Maintain consistent indentation. Use 4 spaces.
- Use Allman style braces (each
{
and}
on its own line) - Where relevant, prefer
wchar_t
overchar
. More about unicode (wide chars): The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)
-
Your code should be commited to a branch which is not
master
. -
When you're done, you shall open a pull request.
-
Pull request may be merged in to master after 3 aprooving reviews by your peers.
-
This repository uses git submodule. Run the following before working:
git submodule init git submodule update
Please compile and run your code before opening a pull request. Never merge to master code that doesn't compile, doesn't work, or crashes.
- This project uses OpenSSL. Windows binaries compiled by Shining Light Productions.
In order to run builds, cetrain DLLs need to be present.
Copy
libcrypto-1_1-x64.dll
fromOpenSSL/dist
toSource Code/x64/Debug
! - Example database is located under
Example Database
. Instructions are inExplaination.txt
. You'll need an initialUsers.txt
database in order to log in to the system.