Version Control System for Web Development, effective ba?

[gabs]

ako task man gud kay pahimoon ko basic tuturial on using Trac/subversion.

nakasabot na ko gamay cge search og basa sa book sa svn


ako problem lang is

unsaon man ni pag combine sa live server apache og repository?
mas effective ba ni compared to traditional edit locally then FTP upload2x thing?


among website is already up and in production na. pero cge pa ni under develop.

akong current set up kay

gipa himo ko sa ako boss og replica sa among production server sa gawas like exact versions of OS, apache, php, java, etc

nya create virtual host for each web developer.

so each developer naay kaugalingon nga domain then if ma final na nila ila kada trabaho nila, ila dayon i update ang main virtual host. then if final na jud, upload dayon sa among testing nga real web hosting, not the production site.


please advice me kay gamay pa jud ako learning aning web development nga environment.
ako may nahug net admin gud kay ako ga setup from zero og nag handle sa development server, og sa network.

[fixyourself]

unsaon man ni pag combine sa live server apache og repository?
mas effective ba ni compared to traditional edit locally then FTP upload2x thing?

Imo gi ingon bai doesn't make sense, or wa lang ko kasabot sa imo pasabot. I'm not familiar with apache but unsai e combine ang live server apache sa svn repository?

RCS is used by the development team to manage source codes (but not limited to). Ang source repository is ang central storage sa codes commited by the developers, it doesnt mean nga ang repository e combine sa imong production server. lol. Pero pwde ang latest source nga naa sa imong repository e deploy sa imong production server.

An existing thread somehow related to RCS.

https://www.istorya.net/forums/progra...-and-more.html

[gabs]

sorry di pa jud kaayo ko familiar ani gud.

sa ako nabantayan man gud kanang magtrabaho na sila ang web developer, gamit sila FTP client then i refresh dayon nila ang website or url then makita dayon ang changes.

galibog man gud ko if pwede ba na himoong "repository" ang location gani ana ilang "index.php". kanang uploadan nila sa website ba.

local raman tanan ang development. basta naa gani major update, diha pa nila i update sa testing site (hosting). then basta major major update na, adto na sa pinaka final server (production domain)

problema man gud nila kanang "kinsa nag edit sa file bay?" og "nag edit ka sa file bay?" ana gani nga problem. mao gi pa set up ko asa ako boss og local development server para i virtual host.

karon kay gusto man sa ako boss kanang gitawag og "trac" wala paman sila kasuway pud ana gud

[fixyourself]

sorry di pa jud kaayo ko familiar ani gud.

sa ako nabantayan man gud kanang magtrabaho na sila ang web developer, gamit sila FTP client then i refresh dayon nila ang website or url then makita dayon ang changes.

galibog man gud ko if pwede ba na himoong "repository" ang location gani ana ilang "index.php". kanang uploadan nila sa website ba.

dili, if subversion.. I dont know how it is stored in the server, but gi try na nakog browse mura syag encrypted.

[maddox22]

dili, if subversion.. I dont know how it is stored in the server, but gi try na nakog browse mura syag encrypted.

Pwede uy. I think iya pasabot ani bro kay ang ila production server, didto pud nila i-install ila SVN repository then i-point nila ila Apache Web Server sa ila repository.

In other words same ra ang directory sa ila repository and sa ila production files. Pwede ni siya however ngano ingani-un man?

Does your boss have any particular reason for doing this? First understand that the purpose of having a repository is for development not for production deployment - unless your boss has a good reason for making your development environment the production itself.

The normal process is the SVN repostiory and you production server should be different or separate. Development first then if ok na then production.

Ang ako sad question to @TS, ngano gi-tagsa-an man ang mga developers ug domain? Curious ko ngano? Is this part of development?

And another thing, ang style nga FTP gamitun then refresh-refresh, as to whether this is a good practice or not, depends on your development team. Because sometimes kapos gyud sa oras and deploying can take time sometime.

However, it might be annoying sa inyo users nga mukalit lang kausab ang itsura or naa mawala nga text... or ang pa-it ug mukalit na hinu-on ug error.

But anyway, kanya-kanyang diskarte...

[maddox22]

Ang disadvantage sad diay kung imo i-point nimo inyo production sa inyo repository kay what if mag branch mo?

[fixyourself]

Pwede uy. I think iya pasabot ani bro kay ang ila production server, didto pud nila i-install ila SVN repository then i-point nila ila Apache Web Server sa ila repository.

In other words same ra ang directory sa ila repository and sa ila production files. Pwede ni siya however ngano ingani-un man?

Does your boss have any particular reason for doing this? First understand that the purpose of having a repository is for development not for production deployment - unless your boss has a good reason for making your development environment the production itself.

The normal process is the SVN repostiory and you production server should be different or separate. Development first then if ok na then production.

Ang ako sad question to @TS, ngano gi-tagsa-an man ang mga developers ug domain? Curious ko ngano? Is this part of development?

And another thing, ang style nga FTP gamitun then refresh-refresh, as to whether this is a good practice or not, depends on your development team. Because sometimes kapos gyud sa oras and deploying can take time sometime.

However, it might be annoying sa inyo users nga mukalit lang kausab ang itsura or naa mawala nga text... or ang pa-it ug mukalit na hinu-on ug error.

But anyway, kanya-kanyang diskarte...

mao ba? pwde ba?

Dili sad ko sure, ako ng gi try og browse gyud ang repository folder sa among SVN server, wala gyuy physical source code didto. Ang ako makita is mga encrypted files lang. Ai ambot lang sad.

Reason for Edit : provided link, how source files are stored in an svn repository

Where do the Files getting stored in repository

so, I guess dli pwde guro imong gusto buhaton.

[bash2death]

pag basa na lang bai about Hudson Server..magamit cguro na sa imu task karn unsaun pag integrate sa SVN changes ug sa Apache...^_^

[gabs]

thanks sa info guys.

ako gibuhat now kay na ahat nuon ko tuon practice SVN.

ako pa ni suwayan og point ang repository og ang main public_html location in one.


regarding sa creating domain for each web developer, para daw naa sila individual version, then copy lang sila sa main then develop.

sa ako tan aw, murag ok man ila paagi pero murag dili tingale ma trace ang process sa development

[personalmgt]

Ang disadvantage sad diay kung imo i-point nimo inyo production sa inyo repository kay what if mag branch mo?

Ahahaha pataya. Sakitas akong tiyan ug katawa.

I myself has been thinking this kind of mechanism so that I won't have to deploy development stuff in production. Actually, buhaton ni nako padulong because my workplace asks me to. What I'm thinking is to initialize the production folder with your favorite RCS. Sure that's possible pero like me who's using Git, I am worried about the Git files that get added in that folder. They can be easily accessed from the outside. Well maybe setting permissions to that folder but I think it's still not a good idea.

One more thing, if you're playing with databases, it sure is hellish. Multiple DBs, changing login/database strings, that could be counter-productive to easier deployment of code. But everything is workable here.