6 {{ upvoteCount | shortNum }}
6 {{ upvoteCount | shortNum }}

my first time on warrior

by alfieandbertie
5 replies
First I would like to thank everyone who made a effort to reply to my question posted on 22nd .I am brand new to all this and to be honest I need some guiding in the right direction I was lucky enough to be given a book by Christine Clayfield called newbie to millionaire which is now my reference when I get stuck. it is a book I can highly recommend to any newbie like myself .now comes the question how do I trust and make sure an outsource will not mess about with any site I want them to work on , I mean they can do what ever they like with access to your dash broard can't they ?
#expeinece #outsorcing #warrior
  • Profile picture of the author Jason Freeman
    Why don't you just use an FTP client like Filezilla? You create an FTP session for them and they can upload the files for your website.
    Signature


    {{ DiscussionBoard.errors[9299862].message }}
  • Profile picture of the author Raygun
    First off your can create temporary or limited passwords for almost everything now, also I suggest using 3rd party tools to make sure you see what they are doing while working for you.

    Tools such as TeamViewer are great, or if you are going to a place like elance they have ways to keep things pretty tight so you are both protected.
    Signature
    $25,000 Prizes===>>>
    http://clicknbank.com/jv-invite.php
    {{ DiscussionBoard.errors[9299873].message }}
    • Profile picture of the author kilgore
      This may seem like overkill, but I recommend always having (at least) two versions of your site, a development version and a production version. The development version is NOT public. It is where you have your developers, designers or anyone else (including you!) make changes and do testing. The production site is the public site where you deploy your changes once they've been properly tested (and only once they've been properly tested).

      It doesn't take someone purposely trying to mess things up to screw things up completely, and it is far better to have your development site broken than your production site. You can limit the access you give to just your development site and then move the changes over only once you're satisfied with them. A development can also serve as a useful backup in a pinch.

      For complex sites I also recommend a staging site, but this is likely more than you need.

      The trick with this model is setting up a good workflow for development, testing and then pushing changes to your live site. If this seems too complex for you to set up on your own, you can probably find a freelancer to do this for you. It's not rocket science -- but it's how the pros make sure that there systems are secure and bug-free (well, as much as possible anyway).
      Signature
      {{ DiscussionBoard.errors[9299892].message }}
  • Profile picture of the author alfieandbertie
    thanks fellas
    {{ DiscussionBoard.errors[9299882].message }}
  • Profile picture of the author ohman1988
    Hey man! It's all about the mindset, the mindset and the drive! You need to get your ideas down and organized, then just attack them! You sound like you really want this to work, so do just that, work a little. Once you finally see that first money come in, you'll be in love with your work! Keep your head up, you got this
    Signature

    These Three Brain Hacks Saved My Business! Get Them For Free Today.

    {{ DiscussionBoard.errors[9300758].message }}

Trending Topics