the_angry_angel

I’ve been working with Odoo for about a year implementing it for a small-medium business in the UK (lots of customisations, general specing out etc, working with their partners, etc. So not all dev). Disclaimer I’ve not yet touched v13.

The good; The OCA (community association), the people (both community and Odoo), the basic framework gets you up and running fast. You can tell it’s grown over time, and it’s got sharp edges, but you can get what you need done. Not necessarily in the prettiest way. The backwards compatibility and desire to not break the core APIs is generally good from what I’ve seen so far. Individual modules depends how much Odoo themselves lean on it afaict. GitHub access for partners and direct source access to both enterprise and community editions has been extremely helpful.

The bad; imho testing is a pain. The ORM uses Polish notation to build filters, which if you’re used to SQL is frankly irritating to work with. The ORM itself is quite clever, but it’s also not like any ORM I’ve worked with. The dev docs aren’t great, beyond the basics. The quality of modules in the “App Store” is extremely hit or miss. Odoo official “support” as a partner is questionable. I feel like they’re under pressure to get you to pay up to be a partner and then some period of time you might get help later. Anecdotally I’m led to believe our partner account manager has been pushing us hard to host a local event at our own cost (I’m not that involved with that side). The last few versions have seen more accounting features drop out of community edition. Some of the official apps are basic.

Is it better than SAP, Dynamics, etc.? Probably not. Is it good enough given the price point and flexibility, for smaller businesses? Probably, especially if the business has been tying together lots of apps adhoc.

Yeah I’d completely missed this part. Makes it even worse

I was until even a few years ago still in the camp of progressive enhancement. I'm now accepting that you really do need Javascript and you cannot get around it. It does bother me that we've swung so far towards SPAs.

Beyond deeply dynamic webapps, such as ERPs/line of business apps, and the very few that really do need offline mode, I think server rendering in conjunction with javascript is the right path.

What that looks like in today's world I have mixed feelings about.

Phoenix's (Elixir) LiveView (which is now being duplicated in as Livewire in PHP) is an interesting take and certainly fills a gap, but I'm getting that feeling of jQuery era where markup is peppered with magic attributes. And equally it doesn't address all use cases (which is fine).

We're certainly in an age of experimentation.

The simplified timeline (as I understand it, willing to be corrected if I'm wrong);

1. PIR, or someone very close, seems to have lobbied to have price restriction of .org removed. My understanding is that PIR made the argument that they're a non-profit, they have no reason to raise pricing extortionately

2. This was passed, despite a large number of comments against the idea, Ethos was incorporated the following day

3. PIR sold itself to Ethos, a for profit company

The people involved seem to be moving between ICANN, PIR and private firms.

Given all these things I don't think it's unreasonable that people are deeply sceptical. Especially with the ambiguity of "no more than 10% per year" being throw around.

Integration with SPF and would be unfun and probably even impractical (max 10 lookups iirc?). I’d also worry about the inevitable abuse which would appear to originate from your range(s). If you can mitigate those though, it sounds interesting

In that case you are very fortunate.

I was running my own mail server for nearly 10 years on Hetzner. Prior to that on other hosts and in the distant past at home. Running mail servers is something I have done professionally and successfully.

The last time I moved boxes as I had many times before. I was on clean IP range but I had no IP reputation at all. In the past this wasn’t such a problem, especially with SPF, DKIM, rDNS, DMARC, server-to-server SSL etc. Around the same time I started having to deal with organisations (legal, etc for a death in the family and later rent) rather my my own circle of friends. It became extremely apparent that my mails weren’t hitting the inbox. But they were being accepted. This was extremely problematic.

I was in the group stating that running your own mail server isn’t hard. I still say that. The hard problem is convincing the big players to let your low volume domains and IPs hit the inbox. I begrudgingly gave up my MX servers last year.

How well does the auto wipe behave on Tesla’s? I’ve owned multiple cars with the feature over the last 10 years - the only one which has ever got it close was a Lexus (quite some time ago). The rest I’ve had and still need to constantly police.

Early versions of Bitlocker on Windows suffered from this.

I'll let you figure out how I know this :|

Off the top of my head;

* No Active Directory/SAML/other SSO. * Gaudy/gamer orientated look-and-feel, messages and notifications is hard to sell to business. * No/Poor implementations of "Enterprise Features" (read: eDiscovery, DLP, etc.)

Of those the first and second are arguably the most important as it is often a requirement for businesses of any size. The third is a bit more larger/enterprise-y business.

Hadn't come across the case. I'll give it a go if my DIY attempts dont work (or are crap) :D

This was exactly my intended use case - as a gift for relatives - the problem I've had is that I need it enclosed to prevent tiny little fingers from getting hurt/destroying the thing. Tried soak testing it one night and experienced the same thing :/

Currently I'm hoping that I can modify the case this weekend to fulfill my needs.

As something intended to be used by kids to learn about computing I do wonder how many are going to get hurt fingers from the heat output by accidentally maxing the cpu and/or touching the USB ports, etc.

Thanks, I’ll hace to look it up and give it a read. I’ll be honest I’ve not read the actual RFC in this instance and pieced together what I know from articles, reported behaviour, etc.

I know it’s lazy and I should’ve done more work. But, burn out

This is my beef with (my understanding maybe incomplete, in which case I apologise) the implementation.

Internal DNS, split brain DNS aren’t catered for without disabling support? I don’t want my internal names leaking to the internet, nor necessarily are they the same for external resolvers. Now yes the latter is a hack, but it’s one widely used still today.

The idea is laudable. But it feels hostile. I can disable support, but for how long?

IPSec is pretty much the standard interop still - pretty much everything talks it Cisco, Juniper, pfSense, Fortinet, etc. You name it I’d be surprised if it didn’t have support.

I’d love to see wireguard implemented in the networking world, but I think it may take some time to get there :/

You can absolutely configure IPSec tunnels on Fortinet.

Can I ask, do you perform updates and maintenance on these boxes? How do they perform in terms of throughput with openvpn?

FWIW in MSSQL there’s always the `option (maxrecursion 0)` trick

On one hand I kind of agree. It's a special syntax, which is one of the reasons why I personally dislike Vue and Angular, etc.

However, pragmatically, it's minimal and all the guts will be in Elixir - where the people probably most interested in LiveView will be spending most of their time anyway. So it's a net win imho.

Definitely not just a gimmick. It's aimed at smaller contractors imho.

I bought my first house in the UK less than a year ago. I ripped absolutely everything out. For weeks at a time I had only 1 working sink, with 1 working electrical output. During this time I had local contracters in to deal with stuff I either didnt have the time, expertise or legal certifications to manage myself. Barring a carpenter, every single one brought a makita radio/wifi unit, and every single one needed to leave the house to get hot drinks because the single socket could not safely take more devices plugged into it (chargers on an extension), etc.

> renamed the web folder a couple of times and so on

Just to add a bit of information to this, they were all in RC or pre-releases. I was bitten by this myself, but if you choose to run RC code then you need to own that a little bit.

Any tips on prying people away from Excel, and into something like metabase/Tableau/whatever?

That seems to be one of the biggest hurdles I think I'm going to have to figure out, rather than the technical side.

Story time;

I've recently started working with a SME (<100 users) who took this approach after abandoning the vendor's reporting recommendations for their Line of Business application (apparently it was just crap).

Other areas of the business cannot be without these reports under any circumstances. Negotiation is not an option.

Since about 2012 they've had various employees generating reports, alerts and data warehouses as objects in the database. Naturally some of these have been superseded. Very often the old objects were left behind "just incase". Almost all of the original authors have left and documentation has been lost or just didn't exist in the first place.

Many of these objects are dense and difficult (because SQL was the wrong tool for the job, or because they go many layers deep like matryoshka dolls).

Demands for changes to reports are frequent (weekly), and some reports functionally overlap, but produce wildly different results for different areas of the business based on various "rules".

Honestly, the database is a fucking mess (approximately 1900 objects relating to reports, alerts and data warehouses - some of which are dolls going many many levels deep., There's a huge sense of shame and fear over trying to regain control.

I totaly understand that this was entirely a human problem. With more restraint this wouldn't have happened. Both inside and out side of the IT team. However, a tool like PopSQL, metabase, etc. I believe would've helped with;

1. Ad-hoc queries that didn't really need to be full objects

2. Discoverability through prettier annotations, etc. - reduction of reports being duplicated

3. Auditing - last access/run times, etc. would be much easier to find to reduce the cruft

4. If the tool is more appropriate it could off load some of the things that SQL is not good at

There are undeniably good reasons for storing reports, alerts and data warehouses (developer maintained objects) in version control. If the report creation/alteration requests don't come often, then I'd argue it's ideal.

However living in the real world, I personally feel it needs to be balanced in conjunction with tools like PopSQL, metabase, etc. Right tool for the right job.

Yeah thats the one.

SFTP is SSH (i.e. it's not FTPS), so you don't have to stand up a FTP server :)

I believe Duplicati is the current tool du jour

> I know, shocking but not everyone is Amazon.

Amazon Vendor Central only has support for EDI (at least in the UK) - as in EDIFACT files sent over FTP.

If you want to do business with them you either need to talk that or be comfortable farming out to a 3rd party (I'm 1 day into a project where I'm finding all this out, and the hell of EDI file formats).

> Contexts ... not so much imo

I'll prefix my comment by saying I'm someone who is more on the sysadmin side of the scale of things. My code isn't pretty, but it generally works well enough to get the job done. I'm learning (probably the most important thing, I guess).

Contexts are one of things that I felt the same about. Until I tried really using them, rather than stressing over whether or not I was using them properly.

I made the mistake of trying to think of them as microservices, which bogged me down and for my purposes was complete overkill. I've now reached a kind of happy medium, which I've realised that I really should have already been using. I've kinda realised I suck at api design. And for that I'm very thankful to the phoenix team, because it feels like I'm learning.

I feel dumb not even having looked whether or not anyone actually produced cloned 10G cards.

Have you had any success with them yourself? Is there any data or resource on how trust worthy these clones are? Tempted to order a couple for testing at home with, at some point...

I'd assume the guarantee of the box being up, unlike ec2.

> why don't you use, e.g. protobuf

protobuf sounds attractive, but (unless I've missed something in protobuf's implementation), but out of the box you have 2 issues:

1. Protobuf doesn't/can't deal with fragmentation - so you'd have to ensure your protobufs are small enough to fit inside a UDP packet

2. Without a wrapper you couldn't put multiple small protobufs into a single UDP packet?

Both things are fixable by wrapping protobuf, but I suppose if you're trying to get something as small as possible, can you actually just do better by avoiding protobuf in the first place (I guess the answer is yes?)

I believe the point is that you have CoreOS hidden behind a firewall you can control, therefore you only have ssh open to sources you permit, you use a bastion host, etc.

Alerting is in the pipeline according to https://github.com/grafana/grafana/issues/2209