New Appliance: Odoo

[l-arnold]

So far so good with Odoo. (not seeing how to label "new-appliance")

ISO Available (long build process)
Arranged the http/https routing so that General usage defaults to HTTPS and no ports needed to be called.
Overrode tendency for TKLDEV to use the main structure from LAPP.
Need to define a new TKLBAM Profile.
Would like to bring in more Addons by Default
Fantastic and easy Migration from other Odoo (manual built).
Seemed that LAPP updated just one file which I was removed anyway to build Apache/Odoo CONF structure properly..

Issues:

• Would like the Main feed to TKLDEV to be a Package Pull for Odoo rather than Git Clone.
• get some scraps in the console when I start it up, but when I choose "Advanced" then "Back" they go away.
• ISO Size 1085 so larger than desired 1024 cylinders
• Need to update to Adminer it seems from the threads.
• SSL for Console 12325 dropped w/ hosted domain name
• some lag at startup

https://github.com/l-arnold/tkl-nomadic-odoo.git

[JedMeister]

Great work! 😄

I've just had a very quick look through your code and it looks like it will want a bit of pruning, consolidation and tidying; but as a first full appliance build it is a very solid effort! 👍 Odoo doesn't appear to be a very easy appliance to build/configure so well done! 👏

My 2c re your points:

• Would like the Main feed to TKLDEV to be a Package Pull for Odoo rather than Git Clone.

From my reading, using a git clone to install Odoo is actually better as it allows end users to update easier (if they so desire). Although perhaps might be useful to just clone the latest commit --depth=1 to reduce the size of the git tree downloaded. OTOH using the pre-build deb might be easier in some respects...

• get some scraps in the console when I start it up, but when I choose "Advanced" then "Back" they go away.

This would be related to #356 and/or #338

• ISO Size 1085 so larger than desired 1024 cylinders

Do you mean 1085MB? As in 1GB!? If so that's huge and I suspect pulling the whole git tree in is at least part of the problem...

• Need to update to Adminer it seems from the threads.

Not very familiar with PgSQL so not too sure about this one...

• SSL for Console 12325 dropped w/ hosted domain name

No idea about this (question below)

• some lag at startup
  Not sure on this either...

Some questions at this stage are:

• Why add Samba?
  • is that going to be relevant and useful for everyone?
  • or is it just handy and 'nice to have'? (if so I argue we should remove it)
• Why still have Odoo available via port 8069? My understanding is that to configure it to proxy properly through Apache (so it's available on ports 80/443) that makes serving it on port 8069 both redundant and a potential security risk... (It's easily disabled by setting the Odoo config to listen only on localhost/127.0.0.1)
• What is the 'console' you refer to? I assume that it is something directly relevant to Odoo? What does it do and what is it's value?

[l-arnold]

Agreed on most counts: (aside - some markdown buttons would be helpful here)

• (Git Clone depth= 1) Good point: might be useful to just clone the latest commit --depth=1 " I could kill the Git after cloning it and would likely also shrink it down but I like --depth=1 path
• Port 12325 Console is simply a repositioning and tweak of index.php that is in LAPP. I find it quite helpful for checking that all the interfaces are in fact up and running. Somewhat akin to having SSH and Webmin in the Servers console on TKL/Amazon hub. (not good to have it be the landing page for the whole IP though, thus the move. I do think something of the sort would be helpful for most apps.
• Small Lag on startup I expect is related to the process of starting Odoo which is starting via scripts that I am not watching (I used to so I know it takes a little time) (not a big deal). I will say that increasing my RAM allocation to 512 then 1024 and giving a second processor jumped the speed considerably.
• Samba. Working on a full answer. I don't know yet but it is there now, removal is easy and by default needs a login etc. Security and Overhead are the subjects to consider. Likely can be synched with the Odoo User Base and could provide then both a shared and personal storage space (though is more needed to synch or is it all in Samba? Extplorer is not loaded and though I considered did not want to wade into the LightTPD web that is serving it on the TKL FileServer app).
  In general I can see a advantage to it in terms of keeping PDF docs generated by Odoo attached to the server rather than every users personal datastore. Making that "default" will not be easy. My friend uses it with http://sourcetreeapp.com/ to have a graphical presentation of local Odoo (and other Git) projects. I need to learn about this.
  As a base Odoo install I am not sure Samba is needed. Certainly not critical). I will run some tests and research other practical applications more.
• Odoo Port 8069 I have already updated the services.txt to say http://localhost:8069). Next I need to update the conf file to restrict in fact. Should be pretty easy.
• Again, my "Web Console" is a reworked version of index.php in LAPP that adds an Odoo Link and could add others (for instance links to documentation etc). It couild run alternatively on 8080 instead of 12325 but seemed worth keeping in the TKL grid.

Back to it today. Import went really well from my Postgresql App build. Did a Backup of the Database. Then Restore to the New Server. Would like to test TKLBAM but not sure it will work as I modified LAPP pretty extensively.

When manually importing, backing up, issues with Web. Once 2 Databases are populated any Web Visitor is asked to choose the Database which totally breaks the idea of web hosting with Odoo. Should be easy, but will need an InitHook declaring that Database name. Also an opportunity for breakage.

Thinking about hooking into Webmin to get some easy Control over the Odoo Config files as well as Odoo Start Stop and Git and Addon functionality. Ideally wouild access ODOO Server from the Servers Dropdown in Webmin ideally. For now though this can be addressed from FileManager (Java) or SFTP. Probably not time just now, but perhaps this is easier than I think it will be.

[l-arnold]

On Test system edited Odoo Config files (ie openerp-server.conf) with the following and it blocked 8069 in http mode. Will add to the app and test on next go round.

(had no values before)

xmlrpc_interface = 127.0.0.1
netrpc_interface = 127.0.0.1

[l-arnold]

Excellent,
Git Clone ... --depth=1 cut the size in half (and I didn't apply to a few small gits included). Seems to have sped the build time considerably as well.

In /opt/openerp/odoo/openerp-server.conf
I have disabled port 8069 to the outside (did not work if also done in "openerp-server-man.conf in same folder, but as noted below may have been something overall system related instead)

I anticipate this will cause problems for people trying to install their SSL Certs so need to give simple guidance for opening (it is rather easy)

A small script would be ideal.
Webshell (12320) did not work on first load and now that I have rebooted, perhaps the "openerp-server-man.conf" statement above was caused by something systematic instead.

[l-arnold]

Confirm (the openerp-server-man.conf) above did not cause the system not to operate.

The changes in openerp-server.conf (and openerp-server-man.conf which may not be required) do block 8069 from being accessible from other machines including on the same network. SSL is working through Proxy, so as designed.

Basically taking 2 Reboots for a complete system to come up.

Once before InitHooks
Once after InitHooks
Seemingly a Third Reboot then all systems are working.
This is after a new MAKE today. I do not recall this problem earlier, though it could explain one or two seeming SSL Issues. Today had a variety of issues.
Webmin in Chrome came up after system showing at install reboots.
Webshell and Oddo Came up after 2 boots (ie. one more than design)
IE Explorer 8 Webmin and others only came up after 2 boots. (also one more than design)

Should probably script this if it is ongoing. May be an issue with Openerp/Odoo Server needing to restart which also could be scripted.

[l-arnold]

(FIXED in Comment Below) Found in http://www.askapache.com/htaccess/mod_rewrite-variables-cheatsheet.html#SERVER_ADDR

quest was

My reworked index.php (aka web console) is causing problems.
Standard build is to use HTTP_HOST but this is problematic when the Host Starts with a Port Number.

For Instance the standard index.php in LAPP:
$_SERVER{'HTTP_HOST'}; ?>:12321"><img
will give me (when hosted on port 12325) www.website.com:12325:12321

SERVER_ADDR works if there is no Firewall or IP Alteration involved which there is if hosted behind a firewall generally even though ports are less problematic.

$ipaddr Likewise gives the same problem as SERVER_ADDR

What is Needed is a Variable for HTTP_HOST_NOPORT
then my alterations would work.

SERVER_ADDR does work for testing inside a private network but not when public.
Likely could be buried for now.

I have tried HOSTNAME but it gets tangled between TKL Hostname and Odoo Hostname. Needs to be the TKL Hostname which would be specified in an inithook. It resolves however, to Odoo's hostname somehow, even going through Apache and not landing on the Odoo Website (at index.php)

[l-arnold]

use SERVER_NAME to fix all issues in index.php.

I recommend this being standard Naming for all Index.php Consoles. Updating next.

[l-arnold]

Will move issues to the Root App from here out unless comments come in here. Will post a SourceForge Iso shortly as well.

[l-arnold]

Working ISO is here and it looks like not posted since my last comment.
https://sourceforge.net/projects/tklnomadicodoo/

[l-arnold]

Working through the wkhtmltopdf issue again. Made it work in my original build and Jeremy referenced the same in forums, but it seems my Config File wants it to be somewhere it aint.

[JedMeister]

Perhaps a new enough version of wkhtmltopdf may be in Jessie?

[l-arnold]

Got it working. Fonts are not as clean as in Wheezy... Working on that but might just be my eyes. Bottom line is it works and we are going away from paper. The "Portal Option" is really nice. Had a customer today login and confirm an order. Yesterday sent a nice clean "mass mailing" that also worked very well. Its a big system and lots to setup for sure but that should be done by the user generally. The wkhtmltopdf and base line addons do need to work and are as far as I can see. That was the only error I had so far.