Search the Community

I've spent the last year building a web application on my local machines using the typical LAMP stack. I've been a developer for 10+ years and am fairly good when it comes to scripting but the server/hosting/system admin thing scares me. I've taken tons of sites live but they always exist on shared hosting and require minimal maintenence...simply ftp changes...no big deal. With my latest personal projects I've used revision control (git or mercurial) simply as a way to let me work from different machines. It's awesome. I push code from home, work, and my laptop and everything is in sync with one another. It really has changed the game for me. ( I use bitbucket) My latest project will involve paying customers and has a huge code base. FTPing files is not going to cut it. I've heard of having a "staging" environment so that you can push code to the staging environment, test it, and then push to production. That sound perfect! Every time I google git/staging I get pages and pages of command line stuff. I'm used to using version control GUI's like tower and sourcetree. Are there server environments that would allow me to use a GUI to manage version control? Or are linux server environments command line only? Are there any hosting companies you know of that would be a good fit for these needs? I'm looking to keep the hosting <= $20/month Thanks

I have a situation with my job where we have software versioning in place. We are having releases ever 2 weeks to a month. for example we are currently working on 2.2.1.0 and 2.3.0.0 we have requirements for 2.3 and 2.2.1 any changes we make to 2.2.1 need to be replicated in 2.3 also what is going on is they are going back to previous versions and making other corrections to 2.2.0.0 and now 2.1.4.1 and 2.1.5.0 and adding a new version 2.1.5.1 this is getting to be a little too much to keep up with and we have a team in china working with us also, and I am working and managing the project files. we have github as a repository system and have versions for 2.3, 2.2, and 2.1 the idea is that each repository will have the latest of its sub kind well, we recently released 2.2.0.0 and then started on 2.2.1.0 and then they made a bunch of changes to 2.2.0.0 and then released the package then the chineese made changes to the files that we broke off (out of repositories) after the package was released and then stuff didn't work because the chineese wanted to replace files from 2.2.1.0 into 2.2.0.0 which may also compromise the integrity of everything. I got reprimanded for not properly communicating with the chineese to stop making changes... now, they want to have a separate repository for each an every release what is the best strategy to keep up with this. It seems like it is set up to fail and have crossover that is going to break. I have done the best I can do to keep versions of every system. am I just in over my head or what?

Hi, I have one big project written in PHP. We currently use Git to do the source code versioning. Now I would like to know how can I separate this big project into smaller projects, each in its subfolder? Today I have: BigProject |-- SubProject1 |-- SubProject2 |-- SubProject3 I wanted to be able to control the version of each SubProject. I'm thinking Git submodules but I read about it and it seems confusing and awkward to work with. Cheers, Bruno