Fork me on GitHub

Lookin for PN Developer!  Bottom

  • Hi,

    we are a 100% noncommercial community website and we do lookin for some development help to get the following working:

    an existing Download Module has to be modified with these additional features:

    Uploaded files shall be stored into the database and not on the filesystem anymore.
    Download fetches the file from database and sends it to the client directly.
    An Import Function which imports all existing Downloads from Filesystem to the database. Also it has to to remove those downloads where files do not exist anymore in the filesystem.
    categories and subcategories are stored in the database too, of course.

    We are lookin for experienced PostNuke Developers and ask for fair offers. We will place the modificated Download-Module unter GPL and offer it for free to the community.

    The Download Module MUST work with Postnuke .726
    .760 is no option yet since it has too many breakdowns to the prior versions. migration of 726 to 760 is not that easy.

    Best Regards

    Simon
  • no impressum, no real contact information, must-register, only a bunch of "developers" mostly consultants, no prices, ...
    i prefer serious information... you are a developer? you have time? then make an offer. ;)

    regards

    Simon
  • just a tip, storing the actual files in the database is retarded. Maybe im completely off, but i dont think i am. BTW, there are only a "bunch" of developers, and if i remember right, none of those listed are "consultants". I personally would never make a bid on a project on a forum, especially just the little amount of information you posted.
  • simonlange

    no impressum, no real contact information, must-register, only a bunch of "developers" mostly consultants, no prices, ...
    i prefer serious information... you are a developer? you have time? then make an offer. ;)

    regards

    Simon

    Erm... you register, post a job, then devs who are up to the challenge post their offers...

    --
    Get PhotoGallery, PayPalCart, Dynamenu, Enhanced Blocks & other mods

    Cape Cod Travel Info...
  • I wouldn't recommend storing files in the database. If you do, you'll be hitting your database a lot more for file downloads, which is just not a good use of your database. You'll also have to stream your downloads through PHP, which means lots and lots of open scripts for long periods, slowing your server.

    It's really not a good idea.

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide
  • well there are a lot of pros and contras storing files into database. for us there are more pros than contras.
    just "some" pros:
    - scalable
    we can add additional "space" within a second, no boundaries (hardisk, machine dependency), no risky nfs constallations.
    - security
    we have realtime backups with mysqls replication and clustering functions. no need for rsyncing anymore.
    - deeplinking
    deeplinking has no chance anymore
    - speed
    since we can spread the website and its complete content to a cluster of webservers and databaseservers, REAL loadbalancing will speed things up.

    we know that all points can be achieved by different packages too (rsync, referercheck, several antihotlinking systems, advanced loadbalancers, nfs)
    but the overhead for all these applications is a lot larger as just putting all into database. sure, the DB will increase, but there is no difference for us since the downloads needs room in all these scenarios. but filesystems are never as scalable as a databaseserver. ;)

    @nate: i tried, but i wasnt allowed to post a job. just tons of errormessages on the site. ;) all messages had a security issue saying that my authentication key is not valid - whatever that means. ;)

    @mac retarded isnt the correct word. its awesome! :) or you tell me how to achieve nearly-realtime putting fresh uploaded files onto several servers... yep no chance. the only chance would be nfs, but then you only POINT to ONE physicly existing file by the other servers. and what do you do when the server goes down (e.g. headcrash). ok, u can use rsync. (every 5minutes? or every 30minutes?) and lose files in the meantime? and i have to live with the cron-launched heavy load of rsync and its traffic-peaks? no, i prefer continously stream of traffic caused by clustering/replication, as we use it for every content! the ONLY content which is not in the database are the files of the download section...

    last but not least. SURE, i just made a "short" post what we need. what did u expect? details come later. but a experienced developer should know with our initial post, if he can doit or not. i would do it mysqlf but i dont have the time to try&fail learn the postnuke API. so its not as expensive to us to deligate it to someone who has PN experience.

    also keep in mind that the best place to get PN developers is here in this forum since at other places its a lot harder to find ppl even knowing postnuke. many developer prefering their own CMS system or usin complete other CMS as e.g. zope. ;) so, yes, i think i have more chances to get experienced developers for postnuke around here and not out there in the wild. ;)

    best regards

    Simon
    ps: i dont think many of you have the experience to compare database/filesystems in a large environment. sure, for small sites and those sites who never shall grow filesystem is good enough, but when clustering comes into place you gonna hate it if you are bounded to a filesystem while the other content is already in the database... and sure, large databases and lots of connections do stress the databaseservers. ever heard of clustering, loadbalancing? if the stress if too high, i just add some more databaseservers... currently our PN-database is 1gb large and has 50gb of downloads (BTW: once we had a lot more downloads, but most files were lost due headcrash, we use currently rsync but rsync uses too many ressources on the machines)
  • what came in mind after sending the reply. ;)
    if u fear too many concurrent connections when downloading directly from database.
    what about fetching the file into local filesystem (cache) and answer from there. and after a defined period of time when nobody did fetch that cached file anymore, the cached file is removed. ;) this would not decrease the pros i wrote in my post before. :)

    best regards
    Simon

This list is based on users active over the last 60 minutes.