Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss project structure #1

Open
SantiagoTorres opened this issue Mar 5, 2013 · 1 comment
Open

Discuss project structure #1

SantiagoTorres opened this issue Mar 5, 2013 · 1 comment

Comments

@SantiagoTorres
Copy link
Member

Check the wiki-entry: https://github.com/GIDAIbero/GIDAFileUpdater/wiki/ProjectStructure

Option 2 should be up on... 3 or 4 days more... let's start discussing option 1

@aparedes
Copy link
Member

aparedes commented Mar 6, 2013

For option 1, I understand that the use of PHP and MySQL are the standard of working in the University (also that there are not much ports open for apps and HTTP port is open), but when writing a new file I would imagine at least a script/program (C, C++, Java, Python, Perl, Haskell, Erlang, Bash... any option is good) that reads the new files; creates the bundle information and posts it on MySQL. I don't like the idea of having a literal file loader through PHP a lot of security issues can arise. And as the developers we should have access to the server that hosts the files.

Actually there could be a cron that pulls the git repo and we can add a hook that runs the program after every pull.

In an ideal world were we could manage the ports; we could create a GitHub Hook http://developer.github.com/v3/repos/hooks/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants