Earlier quoted context omitted.
I don't understand how people get by without a password manager and a seperate password for every site these days.
Good memory works for me.
Ah, i'm jealous of you. I can't keep more than a few in my head at a time.
The quick website launch checklist
41–48 of 48 posts
Re: The quick website launch checklist
#42Earlier quoted context omitted.
I have a log that will mail me first time an error occurs. If it happens again, it will still be logged, but I don't get an email. Once I mark the error as resolved - if it happens again, I get an email.
Would you mind sharing how you set this up? That would actually make a great blog post.
I'm afraid I'm too busy to blog at the moment, but the code is here: https://github.com/troelskn/fejlvarp
Re: The quick website launch checklist
#43Earlier quoted context omitted.
Regarding 2: If you haven't done proper index/join stress tests with hundreds of thousands to millions of rows of data pre-launch, then I really don't know what else to say besides you're doing it wrong. Finding out two days after launch that your schema is complete garbage or improperly indexed is an amateur move. Placing javascript (that's not a shiv or script loader) in your to try and disguise this isn't a good s…
Hmm, sorry, thought I was being funny. Didn't work out that way I guess.
Given that the reply seemingly has nothing to do with your post, I think this is a case of someone replying to a comment that is higher up on the page rather than starting their own thread.
Re: The quick website launch checklist
#44Earlier quoted context omitted.
Good memory works for me.
Ah, i'm jealous of you. I can't keep more than a few in my head at a time.
Same here, although I don't use a password manager, I generate them based on a fixed seed and the website's domain, using a simple algorithm. One less backup to depend on ;)
Re: The quick website launch checklist
#45I feel like this is a checklist that makes you feel like you're accomplishing something (checking off items on the list) while never actually launching your website. In a way, it gives you a bunch of excuses to put off your public launch - "I just need to fix some CSS bugs in Firefox 2" or "I just need to test the backup restore process one more time to make sure it works". Most of us aren't building bank software he…
I agree with you on this but for a beginner I think it's a great list to start with. I think a lot of people miss a lot of things on this website and don't have a good launch because of it.
Re: The quick website launch checklist
#46Similar but more detailed & technical version:
http://programmers.stackexchange.com/questions/46716/what-sh...
My abridged version of it: https://docs.google.com/document/d/1jJGUFN6CxQUXQX49mRsJYv1H...
Re: The quick website launch checklist
#47Good list, but what about security? SQLInjections etc? You need to have that covered more than the rest in my opinion.
You can use the OWASP Top 10 as your checklist for security in many cases.
OWASP is an awesome project. If you really want to be secure use that as a guideline! Thanks for reminding me of that. I couldn't figure the name. All I could think of was WebScarab...
Re: The quick website launch checklist
#48Earlier quoted context omitted.
Hmm, sorry, thought I was being funny. Didn't work out that way I guess.
Given that the reply seemingly has nothing to do with your post, I think this is a case of someone replying to a comment that is higher up on the page rather than starting their own thread.
Nope. Trotsky edited his post, one of which's points I was refuting. I don't have the original, but it was edited long after I replied.