From: Stephen J. <st...@ph...> - 2009-11-09 19:14:57
|
It's not as nice as having a file attached to just click and download, but why not just include the script(s) on the page as long as they're just 1 or 2 files? See http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=Distribute_Full_Backups for an example. Cheers, Stephen -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -Robert A. Heinlein On Mon, 9 Nov 2009, Michael Stowe wrote: >> Michael Stowe wrote at about 11:21:39 -0600 on Monday, November 9, 2009: >> >> Not sure if I am missing something obvious here, but the BackupPC >> >> Mediawiki page seems to only allow the upload of *media* files with >> >> extensions like .jpegg, .png, etc. >> >> >> >> Even 'faking' the extension doesn't seem to work for me. >> >> Note Craig has given me editing access so that is not the problem >> >> unless there are different levels of access that would deny certain >> >> types of uploads. >> > >> > It's not a permissions issue; by default, MediaWiki a) only accepts >> > certain extensions, and b) rejects certain mime types. So, short of >> > reconfiguring MediaWiki, you'll have to link to somewhere else that the >> > files are hosted. (MediaWiki wasn't designed to host files, per se, >> but >> > it was designed so that files could be linked to.) >> >> OK... but shouldn't we be using a wiki service that allows posting of >> more general files since we are dealing here with support or >> extensions to BackupPC that typically is written in perl or bash (or >> in my case also a one-liner cmd script)? >> >> I guess we could link to someplace else but that has two problems: >> 1. There is no "natural" place to host such files and I don't even >> know where I would put them. >> >> 2. It makes it hard to back-up the wiki, ensure consistency, do >> version control, etc. if important scripts are stored in (random) 3rd >> party links. >> >> I don't know anything about Wikis but I would have thought that such >> functionality would be available for open source projects which often >> by their nature have multiple code contributors and extensions that >> are not part of the core tree. > > I believe what SourceForge expects (in the sense of "going with the > grain," and generally accepted practices) is to actually set up a small > SourceForge project, which then provides version control, download > capabilities, and so forth. > > (Personally, this seems like a lot of overhead to me, so I just host my > scripts on my own servers.) > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |