Development setup

[kilburn]

For now I've been using a virtualized test server, wich has it's own (installed) copy of ispcp and my main machine as development one.

The annoyance with this is that any time I want to modify something I've to:
1. Modify it in my svn working copy
2. Upload the file through sftp to the test server
3. "test"
4. Oh! I forgot one ";" (place any stupid non-syntax error here)
5. Goto 1

But it gets harder to manually track changes when there are several modified files, etc.

What about you? Any better solutions? I'd love some way of integrating the installed copy with the svn working copy, so I wouldn't even have to update the installed one everytime there's a commit from someone

[RatS]

try diff and patch

[kilburn]

- Install a clean virtualized etch system
- Install samba on it, adding a global share guest root access (this is a virtualized dev machine so....)

Code:

# Sample smb.conf
[global]
workgroup = WORKGROUP
security = SHARE
[all]
path = /
read only = No
guest ok = Yes
writeable = Yes
force user = root
force group = root
comment = Complete disk access

- Download ispcp from svn into "/usr/local/src/ispcp" using your svn client of choice
- Install ispcp from this folder
- "Fix" permissions (security warning! this is a dev machine....)

Code:

cp -R /usr/local/src/ispcp/gui/.svn /var/www/ispcp/gui/
chown -R vu2000:www-data /var/www/ispcp/gui/.svn
chmod -R u+w /var/www/ispcp/gui
cp -R /usr/local/src/ispcp/engine/.svn /var/www/ispcp/engine/
cp -R /usr/local/src/ispcp/engine/traffic/.svn /var/www/ispcp/engine/traffic/
cp -R /usr/local/src/ispcp/engine/tools/.svn /var/www/ispcp/engine/tools/
cp -R /usr/local/src/ispcp/engine/messager/.svn /var/www/ispcp/engine/messager/
cp -R /usr/local/src/ispcp/engine/setup/.svn /var/www/ispcp/engine/setup/
cp -R /usr/local/src/ispcp/engine/backup/.svn /var/www/ispcp/engine/backup/
cp -R /usr/local/src/ispcp/engine/quota/.svn /var/www/ispcp/engine/quota/

- Replace smb.conf with something like this

Code:

# Sample smb.conf
[global]
workgroup = BASIS
security = SHARE

[gui]
path = /var/www/ispcp/gui
read only = No
guest ok = Yes
writeable = Yes
force user = vu2000
force group = www-data
comment = IspCP gui access
hide dot files = No
inherit permissions = Yes

[engine]
path = /var/www/ispcp/engine
read only = No
guest ok = Yes
writeable = Yes
force user = root
force group = root
comment = IspCP engine access
hide dot files = No
inherit permissions = Yes

Done! Now we have two shares that let us access/modify the gui and engine parts of ispcp directly from our development machine AND svn update/commit from them with our svn client of choice (mine is TortoiseSVN)

Any comments, missing points, etc. ?