Constructing A Web Site
Contents
1 - Domain Name & Hosting
Domain Names
For .com/.co.uk domains I prefer godaddy.com but if it will be hosted in tsohost.com it can be purchased from them.
Turkey Hostings
www.natro.com.tr is the best alternative for Turkey hostings. It can provide multi platform ASP.NET hostings with MSSQL & MySQL databases.
Name Servers
- ns1.natrohost.com - 85.159.64.2
- ns2.natrohost.com - 85.159.67.2
UK Hostings
tsohost.com is the best alternative for UK hostings. It can provide multi platform ASP.NET hostings with MSSQL & MySQL databases.
Name Servers
- ns1.tsohost.co.uk
- ns2.tsohost.co.uk
- ns3.tsohost.co.uk
Creating FTP Account
In this stage we create an FTP Account and set a password. If possible we'll use same password for everything.
Creating Under Construction Page
For all images use logicbase.co.uk/img folder
2 - Email
Creating an email for the project is important. For healthy results and SEO stuff I prefer a gmail account in logicmade.project.[ProjectName]@gmail.com
3 - Code Base
According to project's open source or private situation GitHub (For free open source or paid private projects) or Bitbucket (For free private projects) can be selected.
Use project email to create an account. Create a branch (with project name ) from LogicBO master and create a pull request
4 - Build and deploy server
OnCheckIn.com is the only free alternative that builds and deploys .NET codes from codebase. So create a login here with project email and project password.
5 - Exception handling
Create an Exceptionless account with project email again to handle errors and create statistics
6 - Site Health Check & Alerts
Create a New Relic account with project email to set alerts on site down
7 - Project Management
Create a Trello account with project email or you can use logicmade account and create a project underneath.
Get email address for the project from Trello in order to post tickets directly to this board.
8 - Bug Reporting
Create a project under http://s3k.me/bug (it's optional. Trello can be used for both bugs and project)
9 - Code
Common codes should always be in Master and only project spesific codes should be in branch. if master changes other projects using master should be merged and pushed.
See Also
