Blog Documentation Book a Demo
Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

Easier way to update Vanilla

PoloPolo
edited December 2006 in Vanilla 1.0 Help
Updating/upgrading forums have always been a big mess, errors, etc etc. But what if Vanilla made it in a different approach. Let me give you my idea. Instead of uploading all the stuff into the FTP, why not just make an autoupdate upgrader, that automatically uploaded the file onto the FTP, replaced them, and updated the board. This can easily be done with right FTP permissions. Also the admin should be able to turn autoupdate, on or off, if it is on then it would update the board directly when a new update is available. If it is off then you can either manually click the update button and it updates the forum or do it the old messy way, by uploading and replacing file. So what do you think of the idea? This could help a lot of people, especially newbies! Would be nice!

Comments

  • MinisweeperMinisweeper New
    The only problem with this is that it's a massive security hole. It has been discussed before with no real outcome and a lot of mixed feelings. It would be nice, ofcourse, until something went wrong and a load of forums got overwritten by bad files and wiped them out.
  • PoloPolo
    I don't think it is a massive security hole if it is done right.
  • chuyskywalkerchuyskywalker
    edited December 2006
    Three little letters, my friend...

    S.V.N.
    svn up ./
    And be done.

    If you are not familiar with it, I'd be happy to explain more -- but it is, by far, the fastest, safest way to upgrade yourself. Automated upgrades for a forum would be BAD BAD BAD. What about my extensions? Themes? What if I was naughty and had core files modified? An svn upgrade will stop at bugs like this and not screw you over. Additionally, and svn upgrade can be reverted in one command just about as easy as above.
  • StashStash ✭
    And that command would be what exactly Chewy? ;)
  • chuyskywalkerchuyskywalker
    svn up -r N ./ will revert to any given revision.
  • StashStash ✭
    Lovely job :) *bookmarked*
  • chuyskywalkerchuyskywalker
    I think I'll do a write up on how to use SVN with Vanilla -- should be in the wiki.
  • MinisweeperMinisweeper New
    The only problem with using the SVN at present, is that the SVN isnt a stable release, and the new releases arent exact copies of the SVN...
  • chuyskywalkerchuyskywalker
    The trunk of of SVN project is almost never stable. You should be checking out from tags. (And mark should be creating tags at each stable/bug release ;) )
  • MarkMark Vanilla Staff
    http://lussumo.com/svn/vanilla/tags/

    1.0.2 and 1.0.3 were wacky patches that weren't ever applied to the core since there were a bunch of unstable / untested changes in it. So they couldn't be tagged.
  • chuyskywalkerchuyskywalker
    "wacky patches"? :) lol

    I've seen other projects do tags like "1.x" which was simply the most up to date version of 1.(well)x
  • MarkMark Vanilla Staff
    Well, when the register_globals security hole came up, the svn trunk wasn't at a point where I was comfortable doing a release - but I knew that the patch was very important, so I downloaded a copy of Vanilla 1.0.1 and patched that - then released it as 1.0.2 (followed shortly by 1.0.3).

    SVN wasn't involved in the patching process at all - so yeah, wacky.
  • chuyskywalkerchuyskywalker
    Ah, well you could have done a checkout of the 1.0.1 tag updated it, and then retagged it as 1.0.2, then 3 in the same manner. ;)

    Probably should too -- at least, get a 1.0.3 in there.
This discussion has been closed.