RRWH

Been sorting out a few Nginx Issues as well - especially around forcing everything to use https If you need a hand generating your CSR and a self-signed cert for testing I think I have a guide somewhere as well.
 
My stack where blesta is installed is a centminmod install, and then I just added a vhost where I installed Blesta in the root.
 
My complete sanitized vhost config file is included for reference.
 
server {   server_name namegoeshere.com;   access_log /path/to/access.log combined buffer=32k;   error_log /path/to/error.log;   root /path/to/docroot; listen  80; listen 443 default ssl; ssl     on; ssl_certificate         /path to/certificate.crt; ssl_certificate_key     /path/to/ssl.key; ssl_session_cache shared:SSL:10m; ssl_session_timeout  10m; ssl_protocols  TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!AESGCM; ssl_prefer_server_ciphers on;   # Force All pages to use SSL     if ($ssl_protocol = "") {        rewrite ^   https://$server_name$request_uri? permanent;     }   location ~ (\.pdt) { return 403; } location / {   error_page     404 = @blesta;   log_not_found  off; if ($request_uri ~ "^(.*)/install.php$"){     rewrite install.php /%1/install/ redirect;   } } location @blesta {    rewrite ^(.*)$ /index.php last; }   include /path/to/php.conf; }  
Specific Issue that I had using the centminmod stack was I had to remove the included config file for staticfiles - it sets cache headers for several static files and was causing issues with the navigation in the admin panel (css).  For fine-tuning, I will probably make a copy of this file and remove just the css stuff to keep it all as fast as possible.

After reading the excellent Site integration tutorial - I quickly came to realize that we can modify almost all aspects of the Site.
 
WARNING WARNING WARNING  - ALWAYS MAKE A BACKUP BEFORE MODIFYING ANY FILES
 
There are a LOT of *pdt files within a blesta install, and the one you want to modify is usually pretty easy to find.
 
From the doc root of your Blesta install, simply do the following
 
# find . -name "*pdt"  
This will give you a list of ALL the PDT files used for the presentation of the site.
 
Now, say you have a little specific mod you want to do (and yes) I did.
 
The Mod I wanted to make was really quite simple - it is on the Support page.  (Portal -> Support)
 
We are setting up several Support departments - we only have a single Support department listed where you can raise a request without being logged in, all other departments you need to be logged in.  As it is not obvious, we wanted to add a little bit of extra text to the page.
 
First, look at the URL of the Page you are going to:
 
https://yoursite/client/plugin/support_manager/client_tickets/departments/  
next list ALL the pdt files so we can identify what we want to modify, we went looking thru the list for a file that was a close match to the page path.
 
./plugins/support_manager/views/default/client_tickets_departments.pdt  
looked to be a likely candidate for what we were trying to achieve.
  First thing, we make a backup of the original file, just in case we mess it up and can easily revert to the original
 
# cp client_tickets_departments.pdt client_tickets_departments.pdt_orig  
Then with your favorite editor, modify the file.
 
We wanted to add a very simple message to the page 
 
<div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>  
Well, we took a moment, looked over the code and found what appeared to be the place where we wanted to add the text to the page.
 
                        <div class="heading first">                                 <h5><?php $this->_("ClientTickets.departments.heading_details");?></h5>                         </div> <div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>                         <div id="departments" class="pad">   Now, when you go to Portal -> Support you will see what we added (see the attached Image) - In this case, it was pretty east to see where within the pdt file we needed to make the addition.   Pretty Simple!   The Final Step - remember, if you do an update or install a newer version that your mods may be removed.  You should also be keeping a document somewhere of what files you modify and exactly what you changed, so in the event that an upgrade replaces the file you modified, you can easily put your changes back in place - and of course, making a copy of the files you modified as well is probably a good idea as well.   Looking forward to seeing some of the other customization's that everyone does.

Yeah,  Got a few RPi's 1 gets use as a media Server - XBMC connected to the NAS  Does a great job.
 
Still playing with one to use as a remote (solar powered) internet gateway for Ham Radio.    Until the Pi it was simply not feasible to do this due to the power requirements to have something running all the time.  Now at about 4W power it is very feasible.  Have not used the GPIO pins for any control, but have thought about it - that is what Ardruino's are for - much lower power and quite simple code.

After reading the excellent Site integration tutorial - I quickly came to realize that we can modify almost all aspects of the Site.
 
WARNING WARNING WARNING  - ALWAYS MAKE A BACKUP BEFORE MODIFYING ANY FILES
 
There are a LOT of *pdt files within a blesta install, and the one you want to modify is usually pretty easy to find.
 
From the doc root of your Blesta install, simply do the following
 
# find . -name "*pdt"  
This will give you a list of ALL the PDT files used for the presentation of the site.
 
Now, say you have a little specific mod you want to do (and yes) I did.
 
The Mod I wanted to make was really quite simple - it is on the Support page.  (Portal -> Support)
 
We are setting up several Support departments - we only have a single Support department listed where you can raise a request without being logged in, all other departments you need to be logged in.  As it is not obvious, we wanted to add a little bit of extra text to the page.
 
First, look at the URL of the Page you are going to:
 
https://yoursite/client/plugin/support_manager/client_tickets/departments/  
next list ALL the pdt files so we can identify what we want to modify, we went looking thru the list for a file that was a close match to the page path.
 
./plugins/support_manager/views/default/client_tickets_departments.pdt  
looked to be a likely candidate for what we were trying to achieve.
  First thing, we make a backup of the original file, just in case we mess it up and can easily revert to the original
 
# cp client_tickets_departments.pdt client_tickets_departments.pdt_orig  
Then with your favorite editor, modify the file.
 
We wanted to add a very simple message to the page 
 
<div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>  
Well, we took a moment, looked over the code and found what appeared to be the place where we wanted to add the text to the page.
 
                        <div class="heading first">                                 <h5><?php $this->_("ClientTickets.departments.heading_details");?></h5>                         </div> <div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>                         <div id="departments" class="pad">   Now, when you go to Portal -> Support you will see what we added (see the attached Image) - In this case, it was pretty east to see where within the pdt file we needed to make the addition.   Pretty Simple!   The Final Step - remember, if you do an update or install a newer version that your mods may be removed.  You should also be keeping a document somewhere of what files you modify and exactly what you changed, so in the event that an upgrade replaces the file you modified, you can easily put your changes back in place - and of course, making a copy of the files you modified as well is probably a good idea as well.   Looking forward to seeing some of the other customization's that everyone does.

Time for our own show-off!
 
Been busy with our new site just a few things left to go (but when is a website ever finished....), Finally got our integration about 95% there - just need to sort out a few small things that will come in time.
 
site - http://rrwh.com
 
Blesta - https://support.rrwh.com/
 
Login as a client - demo@example.com / demodemo
 
The bit you cannot see is that we put the "logged in as staff" on the same line as the "client Login / logged in navigation "
 
A huge thanks to Mike for his tutorial - it was invaluable in getting this far.

After reading the excellent Site integration tutorial - I quickly came to realize that we can modify almost all aspects of the Site.
 
WARNING WARNING WARNING  - ALWAYS MAKE A BACKUP BEFORE MODIFYING ANY FILES
 
There are a LOT of *pdt files within a blesta install, and the one you want to modify is usually pretty easy to find.
 
From the doc root of your Blesta install, simply do the following
 
# find . -name "*pdt"  
This will give you a list of ALL the PDT files used for the presentation of the site.
 
Now, say you have a little specific mod you want to do (and yes) I did.
 
The Mod I wanted to make was really quite simple - it is on the Support page.  (Portal -> Support)
 
We are setting up several Support departments - we only have a single Support department listed where you can raise a request without being logged in, all other departments you need to be logged in.  As it is not obvious, we wanted to add a little bit of extra text to the page.
 
First, look at the URL of the Page you are going to:
 
https://yoursite/client/plugin/support_manager/client_tickets/departments/  
next list ALL the pdt files so we can identify what we want to modify, we went looking thru the list for a file that was a close match to the page path.
 
./plugins/support_manager/views/default/client_tickets_departments.pdt  
looked to be a likely candidate for what we were trying to achieve.
  First thing, we make a backup of the original file, just in case we mess it up and can easily revert to the original
 
# cp client_tickets_departments.pdt client_tickets_departments.pdt_orig  
Then with your favorite editor, modify the file.
 
We wanted to add a very simple message to the page 
 
<div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>  
Well, we took a moment, looked over the code and found what appeared to be the place where we wanted to add the text to the page.
 
                        <div class="heading first">                                 <h5><?php $this->_("ClientTickets.departments.heading_details");?></h5>                         </div> <div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>                         <div id="departments" class="pad">   Now, when you go to Portal -> Support you will see what we added (see the attached Image) - In this case, it was pretty east to see where within the pdt file we needed to make the addition.   Pretty Simple!   The Final Step - remember, if you do an update or install a newer version that your mods may be removed.  You should also be keeping a document somewhere of what files you modify and exactly what you changed, so in the event that an upgrade replaces the file you modified, you can easily put your changes back in place - and of course, making a copy of the files you modified as well is probably a good idea as well.   Looking forward to seeing some of the other customization's that everyone does.

After reading the excellent Site integration tutorial - I quickly came to realize that we can modify almost all aspects of the Site.
 
WARNING WARNING WARNING  - ALWAYS MAKE A BACKUP BEFORE MODIFYING ANY FILES
 
There are a LOT of *pdt files within a blesta install, and the one you want to modify is usually pretty easy to find.
 
From the doc root of your Blesta install, simply do the following
 
# find . -name "*pdt"  
This will give you a list of ALL the PDT files used for the presentation of the site.
 
Now, say you have a little specific mod you want to do (and yes) I did.
 
The Mod I wanted to make was really quite simple - it is on the Support page.  (Portal -> Support)
 
We are setting up several Support departments - we only have a single Support department listed where you can raise a request without being logged in, all other departments you need to be logged in.  As it is not obvious, we wanted to add a little bit of extra text to the page.
 
First, look at the URL of the Page you are going to:
 
https://yoursite/client/plugin/support_manager/client_tickets/departments/  
next list ALL the pdt files so we can identify what we want to modify, we went looking thru the list for a file that was a close match to the page path.
 
./plugins/support_manager/views/default/client_tickets_departments.pdt  
looked to be a likely candidate for what we were trying to achieve.
  First thing, we make a backup of the original file, just in case we mess it up and can easily revert to the original
 
# cp client_tickets_departments.pdt client_tickets_departments.pdt_orig  
Then with your favorite editor, modify the file.
 
We wanted to add a very simple message to the page 
 
<div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>  
Well, we took a moment, looked over the code and found what appeared to be the place where we wanted to add the text to the page.
 
                        <div class="heading first">                                 <h5><?php $this->_("ClientTickets.departments.heading_details");?></h5>                         </div> <div style="margin: 0 0 0 4em"><p><br />Existing Clients, Please login to see all Support departments</p></div>                         <div id="departments" class="pad">   Now, when you go to Portal -> Support you will see what we added (see the attached Image) - In this case, it was pretty east to see where within the pdt file we needed to make the addition.   Pretty Simple!   The Final Step - remember, if you do an update or install a newer version that your mods may be removed.  You should also be keeping a document somewhere of what files you modify and exactly what you changed, so in the event that an upgrade replaces the file you modified, you can easily put your changes back in place - and of course, making a copy of the files you modified as well is probably a good idea as well.   Looking forward to seeing some of the other customization's that everyone does.

better and will stop someone else having problems...

Got it.....  Found that php.ini had been configured to disable exec !
 
Might be worth adding to the install checks and noting that exec is required for the backups.

We added several modules during the beta, as well as additional features and improvements to existing features.
 
Still, adding new features to a beta isn't ideal because those features that are released towards the end of a beta don't go through as much testing before final release. With 3.0 out now, and known bugs being few, we're able to start transitioning to development for 3.1 and beyond. We are still less than 2 weeks after a major, full-rewrite, all new release and while there is a lot we want to do, and will be doing, stability is more important.

Went smooth!
 
At what point are we going to be able to do the updates from within Blesta itself.  At the moment, it is a bit of a pain as you have to be logged in, download the patch/package, upload it to the server, unzip, then run install.
 
Can't wait until I can do this all from within Blesta itself and thus save a lot of time.

Went smooth!
 
At what point are we going to be able to do the updates from within Blesta itself.  At the moment, it is a bit of a pain as you have to be logged in, download the patch/package, upload it to the server, unzip, then run install.
 
Can't wait until I can do this all from within Blesta itself and thus save a lot of time.

Makes me glad I never went with that particular software....