LF experienced people to review my archiving system 4 school
Posted: 2016/03/24 13:03:33
Hello,
I see this is a bit of an off topic thread, so I hope this is the good place to ask my questions.
I am 2nd year student at University in Ghent (Belgium) and for our project we need to set up an archiving system to archive student work, java projects, .net projects, tests, exams and so on.
The purpose of this is that our school can put all these files on a server to store it for a long time and access it quickly. Students can access this platform to see their work and put files on it, teachers can access all
the files and execute java projects and .net via this platform.
You can access the platform with school credentials.
So I am going to work with CentOS servers and a Windows server for the .net applications (although I've seen you can use mono I don't think it's that stable). For version control and updates I would use scripts via crontab,
to automatize it all I would also use scripts for the CentOS servers with puppet. All files are send via ssh between the servers.
We need to make a physical system, no cloud.
this is my plan:
from a host pc you log in, an sql server is connected and will check your CRUD rights. Once logged in you will see your things or as a teacher all the static files (ordered of course) with the option to execute projects. To store files you can do
it 2 ways, first is via sftp put it on the central file server, or via a git server (this server will clone the project to the file server). The file server will send the static files to the lamp server (the lamp server is the same as the page where you log in). projects (.net java) will be stored on the file server and will stay there. If a teacher wants to execute a .net application, the lamp server sends a trigger to the build server, this build server builds the application from the file server to the .net server or java server and shows it.
So now, is this a good concept of the problem? I need advice on this, thank you for reading!
I see this is a bit of an off topic thread, so I hope this is the good place to ask my questions.
I am 2nd year student at University in Ghent (Belgium) and for our project we need to set up an archiving system to archive student work, java projects, .net projects, tests, exams and so on.
The purpose of this is that our school can put all these files on a server to store it for a long time and access it quickly. Students can access this platform to see their work and put files on it, teachers can access all
the files and execute java projects and .net via this platform.
You can access the platform with school credentials.
So I am going to work with CentOS servers and a Windows server for the .net applications (although I've seen you can use mono I don't think it's that stable). For version control and updates I would use scripts via crontab,
to automatize it all I would also use scripts for the CentOS servers with puppet. All files are send via ssh between the servers.
We need to make a physical system, no cloud.
this is my plan:
from a host pc you log in, an sql server is connected and will check your CRUD rights. Once logged in you will see your things or as a teacher all the static files (ordered of course) with the option to execute projects. To store files you can do
it 2 ways, first is via sftp put it on the central file server, or via a git server (this server will clone the project to the file server). The file server will send the static files to the lamp server (the lamp server is the same as the page where you log in). projects (.net java) will be stored on the file server and will stay there. If a teacher wants to execute a .net application, the lamp server sends a trigger to the build server, this build server builds the application from the file server to the .net server or java server and shows it.
So now, is this a good concept of the problem? I need advice on this, thank you for reading!