SitePoint Sponsor

User Tag List

Results 1 to 4 of 4
  1. #1
    SitePoint Zealot
    Join Date
    Aug 2006
    Posts
    164
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Is there a tool to lock website?

    Hello,

    is there a tool to lock all the files of the website (no changes allowed) and when you want to make any change, then you have to give additional password to unlock the files first?
    http://www.yourshoutbox.com <- FREE chat for your website - limited offer
    http://www.smartchatbox.com <- let your visitors talk

  2. #2
    Life is not a malfunction gold trophysilver trophybronze trophy
    TechnoBear's Avatar
    Join Date
    Jun 2011
    Location
    Argyll, Scotland
    Posts
    5,376
    Mentioned
    214 Post(s)
    Tagged
    5 Thread(s)
    I don't know about a tool like that, but I set all my file permissions to read-only, which has much the same effect.
    Don't be arrogant. Be kind to a koala that thinks it's a bear.

  3. #3
    Certified Ethical Hacker silver trophybronze trophy dklynn's Avatar
    Join Date
    Feb 2002
    Location
    Auckland
    Posts
    14,605
    Mentioned
    19 Post(s)
    Tagged
    2 Thread(s)
    Bingo! That's all you can do (except for the owner but leave that turned off, too, until you need to update.

    Regards,

    DK
    David K. Lynn - Data Koncepts is a long-time WebHostingBuzz (US/UK)
    Client and (unpaid) WHB Ambassador
    mod_rewrite Tutorial Article (setup, config, test & write
    mod_rewrite regex w/sample code) and Code Generator

  4. #4
    Hosting Team Leader silver trophybronze trophy
    cpradio's Avatar
    Join Date
    Jun 2002
    Location
    Ohio
    Posts
    4,823
    Mentioned
    142 Post(s)
    Tagged
    0 Thread(s)
    This isn't 100% failsafe, but the first thing I do is disable FTP and only grant limited SSH users.

    I typically then setup an SVN repo (you can use GIT, Mercurial, etc) with a dev, test, and prod branch structure (prod is created, test is dervived from prod, and dev is derived from test. Developers have access to dev and test and select individuals have access to prod. Then I have a weekly/monthly/it can be scheduled to run when necessary job that will take the code in the prod branch and overwrite the website with it.

    Therefore the primary way the website is changed is via your SVN repo and by pushing changes from dev to test, and then from test to prod (provided it has been tested and verified).

    Granted those with SSH accounts "could" change the website directly, but the next push of prod to the website will overwrite their changes.
    Be sure to congratulate xMog on earning April's Member of the Month
    Go ahead and blame me, I still won't lose any sleep over it
    My Blog | My Technical Notes


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •