Redesigning pfSense interface

vasiqmz

Currently I'm working on a Firewall project and for that I've been using pfSense. I'll be redesigning the WebGUI of pfSense completely i know that all the php related files are stored in www folder but in ISO image file when I mount that I can't see those folder I guess they are compressed using some utility. I'm assuming all those files are stored in usr.uzip file but I can't open or uncompress that file.

My question is How do i compile a modified pfSense [ modifying only the WebGUI ] ?

phil.davis

You should be able to see files in /usr/local/www and because they are HTML/PHP/Javascript it is all interpreted and so there would be no need to compile anything to modify the WebGUI.
However, pfSense is a registered trade mark of http://www.electricsheepfencing.com/ so you cannot just modify bits of pfSense and still call it pfSense. You would have to abide by the rebranding etc. rules that ESF sets. So contact them.

vasiqmz

Thanks for your reply.

Ya those files are visible when you download the whole repo from GitHub but when I download the ISO files from the site then I don't see those www folders anywhere although I see a usr.uzip folder. I know I don't need to recompile the code because of Php but I also can't edit the code while running it Live on a Virtual Box [ it's too difficult to work in there ].

Regarding the registered trademark of pfSense I'll email ESF. Plus I won't be calling this software pfSense.

I just want to know how can I compile or modify the Php files without running it Live on a Virtual Box ?

doktornotor

You modify it by using the tools from the unavailable pfsense-tools repo to build your custom ISO. ::) ::) ::)

vasiqmz

So they removed the tool ? I read on many posts that they had removed that tools from the repo. So if they did then how can I now compile the pfSense ?

ayvis

You can find few clones on github and/or contact ESF

doktornotor

@ayvis:

You can find few clones on github

Which are plain useless for 2.2 development….

@ayvis:

and/or contact ESF

… and receive no reply whatsoever.

jcyr

@doktornotor:

@ayvis:

You can find few clones on github

Which are plain useless for 2.2 development….

@ayvis:

and/or contact ESF

… and receive no reply whatsoever.

Yep, ESF has definitely gone to the dark side.

bryan.paradis

@doktornotor:

@ayvis:

You can find few clones on github

Which are plain useless for 2.2 development….

@ayvis:

and/or contact ESF

… and receive no reply whatsoever.

Have an example of this?

doktornotor

@bryan.paradis:

Have an example of this?

AFAICT, noone ever got access to the -tools repo. "Not yet. Soon (really)." - 3 weeks ago. ::) >:(

jcyr

@doktornotor:

@bryan.paradis:

Have an example of this?

AFAICT, noone ever got access to the -tools repo. "Not yet. Soon (really)." - 3 weeks ago. ::) >:(

Historically the ESF has held a rather uncommon meaning of the word 'soon', perhaps this time it will mean 'never'?

Guest

@jcyr:

@doktornotor:

@bryan.paradis:

Have an example of this?

AFAICT, noone ever got access to the -tools repo. "Not yet. Soon (really)." - 3 weeks ago. ::) >:(

Historically the ESF has held a rather uncommon meaning of the word 'soon', perhaps this time it will mean 'never'?

More like 'now'.

Your impatience is noted.

And I have sworn off ever responding to anything from 'doktornotor'.

cmb

Those who provided us keys had access last week. We haven't "gone to the dark side." ::)