Skip to main content

Need a simple e-ticket commerce solution with paypal integration

This is not so much a review or recommendation as it is a rant about how difficult it STILL is to implement a simple and yet modern e-commerce site.


The naive days of the early web are gone yet most users are either sophisticated or uninformed and both need to be properly serviced. I need to build a simple e-commerce solution for what amounts to a e-ticket or event system.


The problem with most commercial versions of this type of software is that it is typically a SAAS (software as a service). And many charge a fee based on the percentage of the cost plus some fixed amount. This can be problematic because there is also a monthly fee and between the two costs it's too expensive to operate.


  • annual registration
    • once a year we ask our members to pay a family fee and register or name the members
  • event registration
    • About once a month we have an event. There is a fee for the dad and the first child. 
    • Each additional child may or may not have a fee associated with it
    • Each member needs to be identified
    • Sometimes we need to know shirt size or some other question
    • dad's need to be reminded to acknowledge terms and conditions, etc
    • dad's need to be reminded that annual registration is required
  • I need reporting for headcount etc so I can verify the dependency requirements.


There are many challenges. Firstly not all features in most eCommerce sites lend themselves to eTickets and vice versa. I've tried a number of compromises and very few are complete or they expect the user to jump too high.


I understand and respect that all these vendors need to make a living. If I had to build this site from scratch it would cost way more than I would like. I know this is open ended but maybe there is something someone else has done that might work? I'm not averse to hosting my own project or code but I'm very conscious of PCI so no personal information should leak; therefore some professionalism is required.


I looked at paypal but I cannot confirm the reporting.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…