re-opening this subject... I was planing to start with the base TKL 12 image and install OpenERP on it.
Good idea ? Any advice / suggestion ?
The docs seem pretty complete for installation. Hopefully all goes smoothly, if you have troubles just remember that TKL v12.x is based on Debian 6 now.
The only thing I'd add, is perhaps it'd be better to start with the TKL PostgreSQL appliance instead? Assuming that you'll want to backup with TKLBAM...
Although I actually don't use any appliances with PostgreSQL so I'm not 100% sure... IIRC it was released just before v12.
[Update] As of 25/01/2013 TKLBAM does not currently support the PostgreSQL appliance (or any other appliances that use databases other than MySQL) OOTB. However, using the TKLBAM pre and post backup/restore hooks to dump/insert the DB and the --force-profile switch (to avoid the warning) it can be configured to work.
Good point about starting with the TKL PostgreSQL - indeed TKLBAM is one of the key reason to use Turnkey :) ....
I'm not sure whether that would work without a few extra steps. So here's how I'd do it on TKL:
echo "deb http://nightly.openerp.com/7.0/nightly/deb/ ./" >> /etc/apt/sources.list.d/openerp.list
apt-get update && apt-get upgrade && apt-get install openerp
Open http://<appliance-ip-or-FQDN>/ from a web browser to complete install...
The change to the first line are only personal preference (I like to have an additional spearate sources.list and keep the default one as-is). The second line basically just incorporates 4 & 5 and uses apt-get instead of aptitude (and skips the cache cleaning).
I think there is something wrong with the deb... I tried installing to LAPP, Postgresql and Core and it didn't work on any of them... The appliance is not even listening on the port that it's meant to and I can't find any openerp files anywhere... whereis openerp only returns etc/openerp (and no binary...)
As per suggestions above I installed openERP on a TKL PostgreSQL appliance. Things are working fine so far.
Having my server to my liking I tried this:
root@postgresql ~# tklbam-backup
TurnKey Hub Error: Backup profile archive not found: turnkey-postgresql-12.0-squeeze-x86
This probably means that TKLBAM doesn't yet fully support your system.
If you're feeling adventurous you can force another profile with the
--force-profile option. Sorry about that.
Whoops... the whole point was to be able to use TKBackup...
Any advice ?
Sorry, it looks like I have misinformed you! I was sure that the TKL guys had fixed that up sometime ago. I just went back over the most recent blog posts and must admit that I couldn't find mention of a fix being released that included it so I must sincerely apologise.
I have contacted the devs to see if they can give some clarity on the situation (I know that some time ago Liraz was planning to make it's inclusion in TKLBAM a priority - and perhaps that's whay I thought it had been updated).
I recall that therre was some sort of (unsupported) workaround to include PostgreSQL backups in TKLBAM using the pre and post hooks facility, but it was never totally clearly documented anywhere (just hints on the pieces required to do it yourself).
My advice would be to read the advanced TKLBAM documentation and research creating a hook to dump the PostgreSQL DB on backup (and restore the dump on restore) and then use the --force-profile option to create the backup. Obviously you'll need to put the DB dump file somewhere where it will be included in the backup.
Ok looking into making my custom settings - obviously I would have prefered an "official" support...
That being said I would think that PostgreSQL is "mainstream" enough to warrant some attention.
I have spoken with the devs and they have confirmed that there is currently no official support for PostgreSQL ... yet.
They assure me that they are working on it but haved changed tack. They are looking to create a generic TKLBAM database handling functionality which will allow support for multiple different DBs (rather than just adding specific PostgreSQL support). The upside is that this will allow greater flexability into the future and allow TKLBAM to support other existing DB appliances (eg CouchDB) much easier. The downside is that it is taking much longer than originally hoped.
So the way to go is as I mentioned above. Obviously test this thoroughly before you need to rely on it, but I can see no reason why it won't work.
Thanks for the follow up - will report with what I managed to patch together :)
But you will also need to '--force-profile'. Unfortunately I'm not sure of the specific profile names/format but judging by the error message I would assume something like 'turnkey-mysql-12.0-squeeze-x86' or even 'turnkey-core-12.0-squeeze-x86' would work. Note though if you use the profile of an appliance that includes MySQL (eg the MySQL appliance) then you will need to '--skip databases' to avoid issues (if you use an appliance profile that doesn't include a MySQL DB then you won't need to worry).
When you are testing I would make sure that you try restoring to a fresh instance of PostgreSQL appliance as well (as you would have to if you had a hardware failure).
I'd love to hear how you go and it would be great if you could document your findings thus helping others in a similar position (just post back here to this thread if you want). Also if you have any issues ask here too. I can't guarantee that I will have the answers but more than happy to try to help! :)
See the error message posted above. And yes you could use Core instead, but I think LAPP is ok, just need to --force-profile to avoid the error.
Personally I love GitHub and have been using it for all patches that i have worked on for a while now. Launchpad is probably fine too, but I am now familiar with git (and AFAIK Launchpad uses bazaar which I have no experience with).
Here is why I would suggest GitHub:
At the end of the day, though it probably doesn't matter that much. As long as you are using some sort of version control so you can tweak/adjust your code with facility to backtrack if you muck something up.
So with TKL starting out as Ubuntu based it probably seemed like the thing to do (makes linking bugs in TKL that actually relate to upstream software very easy). Now TKL is Debian based, that rationale is less relevant. However we need to have a bug tracker and it works quite well, so no point moving it elsewhere IMO (until something radically better comes along).
AFAIK though LaunchPad has never been used to host TKL code. I think Alon and Liraz use git exclusively (and now have some it hosted on GitHub) and LaunchPad uses Bazaar...
What about using :
or better replace wget with axel .
The package is complete package, including addons .. etc etc.
ref : http://www.theopensourcerer.com/2012/12/how-to-install-openerp-7-0-on-ub...
I have installed openerp 6.1 on windows xp. It is workin well and good on port 8069.Whenever i type from another computer 192.168.1.5:8069 its not accessible . Kindly help me with this.
I have made necessary changes in config file.
I have no idea how you ended up here but this is a forum dedicted to Trunkey Linux - you won't get much help regarding Win XP over here ! I suggest you post your question in the openERP forum in the install section: http://forum.openerp.com/forum/forum5.html
My suggestion would be to either start a fresh thread and edit the top post (rather than making new posts) and any new info keep adding/editing the top post. That way the info is all at the top instead of users having to crawl through a whole thread...
I have sucessfully installed OpenERP 7.0 on TKL 12 (LAMP + Postgres 9.x) several times since december 2012, using a TKLPatch script that I have developed.
I tryed to read all this long thread but did not undestand its porpouse. Are you just trying to intall OpenERP and use it or are you trying to develop a TKLPatch script that will be published to help people to create a TKL OpenERP appliance?
I could help on both options. Just let me know what do you want.
Arnold, as I mentioned before, I have successfully installed OpenERP 7.0 on TKL 13 (LAMP + Postgres 9.x) several times since November 2013 using a TKLPatch script that I have developed.
In fact I have been thinking on sharing those scripts via my new project OeHealth (https://github.com/OeHealth), an OpenERP health solution.
Usually I don’t build an ISO file but just pick an Tunkey Appliance (mostly LAMP), install it an aply some TKLPatch scripts. I think it would be ease to merge those scripts in one that could generate the ISO installation.
We can start a team work on GitHub and I would be very glad on participate on it. Please contact me directly using email "email@example.com" or skype "carlos.eduardo.vercelino".
We can start a team work on GitHub and I would be very glad on participate on it. Please contact me directly using email "firstname.lastname@example.org" or skype "carlos.eduardo.vercelino".
It'd be great to see a OpenERP appliance. If you use TKLDev to build it and host your (TKLDev) build (instructions) on GitHub then we could see it integrated into the TKL library! :)
I have been making some tests on GitHtb regarding the OpenERP installation over the AWS (Amazon Web Services). Please see this link on GitHub:
I did not forked any TK appliance for now, I am just testing some TKLPath scripts.
I woud sugest you to use the LAPP Turnkey Appliance as a reference insted of the pure PostgreSQL Appliance. OpenERP has its own webserver but for http protocol only. In an web eviroment I think that it is recomended to use a https connection instead.
Right now I am testing only over the AWS as I said, but I will go forward to an ISO version of it as soon as possible. I am in a hury here implementing two diferent forks for this project:
Jeremy, I am considering your sugestion on TKLDev to implemet this, but I do not have the skill do to it right now.
The LAPP appliance has the same PostgreSQL admin features as the pure PostgreSQL. Additionally it has the APP stack that is used to implement the HTTPS features.
On AWS usually I disable all ports except 443 (SSH) and 12325 (OpenERP over https) as described on the README of my GitHub branch. To access the PostgreSQL server You canb stablish an SSH tunnel and use a tool like PGAdmin III. Also I configure the apliance do accept sessions for root only via SSH an Private keys.
More information about formatting options