develop on webhost or localhost
Permalink
Hello interested reader
Another beginner question, sorry
webhost or localhost?
I have read over the Editor's Guide, Developer Documentation and the API
and done various testing on localhost.
So feeling more familiarized with concrete5, time to begin development.
I have a LIVE site already which I wish to change to a concrete5 site.
My question is what is the best way for me to approach this first project?
Develop on localhost and upload all when done or set up on webhost and develop there?
Please advise how you would approach this
low tech
Another beginner question, sorry
webhost or localhost?
I have read over the Editor's Guide, Developer Documentation and the API
and done various testing on localhost.
So feeling more familiarized with concrete5, time to begin development.
I have a LIVE site already which I wish to change to a concrete5 site.
My question is what is the best way for me to approach this first project?
Develop on localhost and upload all when done or set up on webhost and develop there?
Please advise how you would approach this
low tech
JohntheFish
yeh i'm on windows dev system so i'll definitely change mysql to use camelcase. First i've heard about that anyway. I guess i've been lucky so far playing on localhost as things have just worked without obvious error.
Great link. I'll have to read it a few more times because there is a lot of info in there but I get the idea.
So should I install concrete5 in a sub directory (which I think is a good idea) and develop the content online as opposed to developing on localhost and then trying to upload everything?
First time working with a (big) framework so have no idea of best way to work with one.
Thanks
low tech
yeh i'm on windows dev system so i'll definitely change mysql to use camelcase. First i've heard about that anyway. I guess i've been lucky so far playing on localhost as things have just worked without obvious error.
Great link. I'll have to read it a few more times because there is a lot of info in there but I get the idea.
So should I install concrete5 in a sub directory (which I think is a good idea) and develop the content online as opposed to developing on localhost and then trying to upload everything?
First time working with a (big) framework so have no idea of best way to work with one.
Thanks
low tech
My personal development process is
- develop code offline
- develop initial content offline
- clone to online staging site
- develop further content on staging site
- continue to develop code offline, upload to staging site for final test/integration
- at some point it is ready, so either make the staging site the live site, or clone it to the live site
- there is usually further content developed on the live site
- there are usually minor code tweaks that continue to follow the dev/staging/live process
- at some point the live site has diverged sufficiently from dev and staging, so I clone it back to create new dev and staging sites based on the live site.
- once stable, I may skip the staging site for minor changes.
- for big changes, take new clones and go through the dev/staging/live process again
- but beware sites with high volumes of user generated data, such as forums, forms and eCommerce.
- develop code offline
- develop initial content offline
- clone to online staging site
- develop further content on staging site
- continue to develop code offline, upload to staging site for final test/integration
- at some point it is ready, so either make the staging site the live site, or clone it to the live site
- there is usually further content developed on the live site
- there are usually minor code tweaks that continue to follow the dev/staging/live process
- at some point the live site has diverged sufficiently from dev and staging, so I clone it back to create new dev and staging sites based on the live site.
- once stable, I may skip the staging site for minor changes.
- for big changes, take new clones and go through the dev/staging/live process again
- but beware sites with high volumes of user generated data, such as forums, forms and eCommerce.
Hi JtF
Thanks for sharing your workflow. It helps me with my understanding.
Previously with my work I would synchronize my files, work locally and then upload any files that changed. I would export mysql if needed.
I have one more question and then i'm done:-)
When you say 'clone' do you mean clone ALL the files plus database or do you mean certain files such as the theme folder and application folder?
ie files/dir that (maybe) change
I'm not sure which reply to mark as 'best answer' because both are good, so i'll just mark this one
Thanks again, appreciated
low tech
Thanks for sharing your workflow. It helps me with my understanding.
Previously with my work I would synchronize my files, work locally and then upload any files that changed. I would export mysql if needed.
I have one more question and then i'm done:-)
When you say 'clone' do you mean clone ALL the files plus database or do you mean certain files such as the theme folder and application folder?
ie files/dir that (maybe) change
I'm not sure which reply to mark as 'best answer' because both are good, so i'll just mark this one
Thanks again, appreciated
low tech
Whatever is needed to ensure an exact replica. That can vary depending on what I am working on.
I do a lot of specialised development for others, so often an everything clone is the best way to ensure it really is a clone and nothing has been missed due to their making changes to content, upgrades and their own parts of the project.
I do a lot of specialised development for others, so often an everything clone is the best way to ensure it really is a clone and nothing has been missed due to their making changes to content, upgrades and their own parts of the project.
JtF
Understood, magic
Thanks for your time and effort
All is clearer and I can move forward
low tech
Understood, magic
Thanks for your time and effort
All is clearer and I can move forward
low tech
JtF
small update
following your advice, I am now setting up my file structure as per your link
and will perform the redirect to the sub-domain via .htaccess rewrite file
as per advice from my hosting provider
Just like to say thanks again for your help.
low tech
small update
following your advice, I am now setting up my file structure as per your link
and will perform the redirect to the sub-domain via .htaccess rewrite file
as per advice from my hosting provider
Just like to say thanks again for your help.
low tech
JtF
Also had to redo my dev environment because my tables were as you thankfully pointed out 'lowercase'
saved me a possible big future headache
good man
low tech
Also had to redo my dev environment because my tables were as you thankfully pointed out 'lowercase'
saved me a possible big future headache
good man
low tech
This howto also has some tips on a staging/live site process
https://www.concrete5.org/documentation/how-tos/developers/organise-...